asterisk users - Apr 2023 - couldn't allocate a port for RTP instance

On Fri, Apr 14, 2023 at 5:44 AM Fourhundred Thecat <400thecat at gmx.ch>
wrote:
> Hello,
>
> my logs are flooded with:
>
> WARNING: The 'stasis/m:cdr:aggregator-00000005' task processor
queue
> reached 5000 scheduled tasks again.
>
This means there's a ton of channel events being created.

>
> and then, when call came, I got this:
>
> ERROR: Oh dear... we couldn't allocate a port for RTP instance
> '0x6e1e680fd670'
>
This means that there are a ton of channels or sessions up that are using
all the RTP resources.

>
> WARNING: Unable to cancel schedule ID 0.  This is probably a bug
> (res_rtp_asterisk.c: dtls_srtp_stop_timeout_timer, line 2873).
>
> any idea what is happening, or how to troubleshoot his ?
>
There is insufficient information. You'd need to state what version of
Asterisk, as well as which channel driver to begin with. Showing a console
log may also provide information.

-- 
Joshua C. Colp
Asterisk Project Lead
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20230414/d0e1cedb/attachment.html>

> On 2023-04-14 11:06, Joshua C. Colp wrote:
> On Fri, Apr 14, 2023 at 5:44 AM Fourhundred Thecat <400thecat at gmx.ch
> <mailto:400thecat at gmx.ch>> wrote:
>
>     Hello,
>
>     my logs are flooded with:
>
>     WARNING: The 'stasis/m:cdr:aggregator-00000005' task processor
queue
>     reached 5000 scheduled tasks again.
>
>
> This means there's a ton of channel events being created.
>
>
>     and then, when call came, I got this:
>
>     ERROR: Oh dear... we couldn't allocate a port for RTP instance
>     '0x6e1e680fd670'
>
>
> This means that there are a ton of channels or sessions up that are
> using all the RTP resources.
>
>
>     WARNING: Unable to cancel schedule ID 0.  This is probably a bug
>     (res_rtp_asterisk.c: dtls_srtp_stop_timeout_timer, line 2873).
>
>     any idea what is happening, or how to troubleshoot his ?
>
>
> There is insufficient information. You'd need to state what version of
> Asterisk, as well as which channel driver to begin with. Showing a
> console log may also provide information.
thank you, I found the problem:

I had this in extensions.conf:

   same => n,GotoIf($[ "${DIALSTATUS}" = "BUSY" ]?6:7)

and then I added one line above that, and forgot to adjust the numbers.
So basically, the rule was going in an cycle.

Is there a better way than to use hardcoded numbers for GotoIf ?