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
