Hi Joel,
We see some channels stuck on the StopMonitor application which could be
the cause, though there are only about 20 of them.
An Asterisk restart is the immediate cure for sure - we were hoping to
identify some cause in order to prevent a repeat.
Thanks very much for your advice.
On
I would check if you don't have any channels in a hung/zombie state...
Have a look if "core show calls" matches "core show channels".
Either way, it seems wonky, so you might end up having to give that
asterisk a restart... :S
On Wed, Jul 27, 2022 at 6:21 PM David Cunningham
wrote:
> Hello,
>
Hello,
We have an Asterisk 13.38.2 server which today started giving "we couldn't
allocate a port for RTP" errors. The output of "netstat -anp" showed that
Asterisk was using all 10,000 ports allocated for RTP, even though it only
had a maximum of around 200 concurrent calls at any point in the
This is what I get when I run "dundi set debug on". I've changed the IPs to
DUNDi Server 1 and 2. DUNDi peers always show UNREACHABLE
Tx-Frame -- OSeqno: 000 ISeqno: 000 Type: NULL (Command)
Flags: 00 STrans: 26713 DTrans: 0 [DUNDi Server 1:4520] (Final)
Tx-Frame -- OSeqno: 000
On Wed, Jul 27, 2022 at 11:02 AM Dan Cropp wrote:
> Looking at the Asterisk wiki
>
>
> https://wiki.asterisk.org/wiki/display/AST/Asterisk+Geolocation+Implementation
>
Just FYI, I'm in the process of clarifying and adding more info. Should be
done Friday.
>
>
> I see the dial plan support the
Looking at the Asterisk wiki
https://wiki.asterisk.org/wiki/display/AST/Asterisk+Geolocation+Implementation
I see the dial plan support the GeolocProfileCreate and there is support for
GEOLOC_PROFILE settings to be set on the dial plan.
We currently use AMI Originate support. We may have
I realize that the heyday of DUNDi was about 2008, and that there's less and
less information online about it and lots of people don't use it anymore and
use static IAX trunks instead. But we have 53 asterisk phone systems connecting
our locations, and so creating static IAX trunks (even with a
