![]() So the unistim rtp "ports left open" bug I pointed out was acknowledged, and it went into the 14 strain.īut with that, sadly, there's no more updates for the 11' strain, and only bug fixes for the 13 strain. Igor has the changes to push into his next update.Īnother: I pushed the rtp port exhaustion issue on the asterisk official bug forum finally, and Igor created a patch that adds a couple of ast functions that close down rtp ports properly after a call is finished. funnily.) Without more boring explanation, I went through the chan_unistim code and made it x86/ARM friendly in ring functionality. everything is unsigned char, and so some of the explicit unsigned char definitions are moot. (Because you can simply throw char around, and when you specifically need an unsigned char, you specify, relying on the default, so in ARM, it's the other way around. The original driver was written probably before there was any interest in asterisk on the pi, (ARM cpu family) so it was written with many 'char' assigns that produce wildly wrong numbers on ARM. He pointed out that the ARM environment 'char' values (in c) are unsigned. I have sorted the ring issue with Igor (chan_unistim maintainer) this morning. (and sip and unistim sets too of course!) a distro for the NanoPI-Neo for someone - works a treat in a commercial environment in the US, bridging two Nortel BCM systems with about 10 channel capability. I've been building relatively small (88mb download img file?) asterisk builds for pi, orange-pi-one, banana-pi, and. It's nice that folks do what they do, as I've not paid anyone. Wait and see? Igor never did get back to me. I have a few Nortel BCM50's wrangled to use these sets so I kinda backed off for a bit. (just endless loads of pointless features for the real world like localised weather novelties?) Perhaps people only ever 'fiddle around' with a few Nortel sets then go back to crappy grandstream stuff and don't bother getting into it as FreePbx or other dumb-down front ends probably don't address advanced settings like that. am hesitant to believe Igor (maintainer) and others would have overlooked such a nasty bug. I'm guessing that if I run this on an intel machine, stock install, it won't be there. Perhaps the above will make it into another iteration, but this port closure. It also doesn't have the above fix, as I still get Duree on timer. I just did an upgrade and the asterisk11 is now at 11.17.0 - I was at 11.15.0-1 when I initially reported this here, but I notice the UDP port issue still hanging around. I never went through the asterisk channel as the raspberry pi isn't part of the official intended distribution I'd guess, being you can't install any digium boards onto one. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |