[asterisk-bugs] [JIRA] (ASTERISK-24478) IAX hits maxcallnumber limit of 2048 with only one concurrent channel

Y Ateya (JIRA) noreply at issues.asterisk.org
Thu Jan 1 14:59:34 CST 2015


    [ https://issues.asterisk.org/jira/browse/ASTERISK-24478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224265#comment-224265 ] 

Y Ateya edited comment on ASTERISK-24478 at 1/1/15 2:57 PM:
------------------------------------------------------------

I saw the same problem and I was able to reproduce it. My setup is as follows:

SIP1 <> IAX Trunk <> SIP2 <> GSM gateway

Hint: Calls always flow from SIP1 (always the caller) to SIP2 (always the callee).

The problem occurs when there is a failure in GSM gateway; which leads to rejecting many of SIP calls. Here is what should happen for increment, schedule decrement and actual decrement of the call number counter:
- call comes
- increment counter
- call rejected
- schedule counter decrement after 60 seconds

and this pattern will be repeated until GSM return to normal operation. So after 60 seconds of GSM-back-to-life; all calls will continue as usual. But this DON'T happen.

What happens is:
- increment, schedule decrement, after 60 seconds decrement event occurs.
- increment, schedule decrement, after 60 seconds decrement event occurs.
.
.
- increment, schedule decrement, after 60 seconds decrement event occurs.
=======And after a while (~15 minutes in my case), decrement event stops!
- increment, schedule decrement
- increment, schedule decrement
- increment, schedule decrement


Decrement don't happen even after I stopped SIP1 calls.
And the result is that IAX peers have no active calls and max call number is 2048. Raising max call number doesn't solve the problem; Neither decreasing MIN_REUSE_TIME.

The attached log is from Jan  1 18:12:13 to Jan  1 18:32:46. You will that the latest decrement "ip callno count decremented" was at Jan  1 18:23:32. For TEN minutes, scheduled decrements didn't happen.

Attachments:
maxcallnumber_count.log.bz2: Extracted counter-related messages from debug log.
maxcallnumber_full.log.bz2: The full log 

Environment:
- Running Asterisk 13.1.0 compiled from sources and using PJPROJECT. 
- Ubuntu 12.04 64bit





was (Author: yateya):
I saw the same problem and I was able to reproduce it. My setup is as follows:

SIP1 <-> IAX Trunk <-> SIP2 <-> GSM gateway

Hint: Calls always flow from SIP1 (always the caller) to SIP2 (always the callee).

The problem occurs when there is a failure in GSM gateway; which leads to rejecting many of SIP calls. Here is what should happen for increment, schedule decrement and actual decrement of the call number counter:
- call comes
- increment counter
- call rejected
- schedule counter decrement after 60 seconds

and this pattern will be repeated until GSM return to normal operation. So after 60 seconds of GSM-back-to-life; all calls will continue as usual. But this DON'T happen.

What happens is:
- increment, schedule decrement, after 60 seconds decrement event occurs.
- increment, schedule decrement, after 60 seconds decrement event occurs.
.
.
- increment, schedule decrement, after 60 seconds decrement event occurs.
=======And after a while (~15 minutes in my case), decrement event stops!
- increment, schedule decrement
- increment, schedule decrement
- increment, schedule decrement


Decrement don't happen even after I stopped SIP1 calls.
And the result is that IAX peers have no active calls and max call number is 2048. Raising max call number doesn't solve the problem; Neither decreasing MIN_REUSE_TIME.

The attached log is from Jan  1 18:12:13 to Jan  1 18:32:46. You will that the latest decrement "ip callno count decremented" was at Jan  1 18:23:32. For TEN minutes, scheduled decrements didn't happen.

Attachments:
maxcallnumber_count.log.bz2: Extracted counter-related messages from debug log.
maxcallnumber_full.log.bz2: The full log 

Environment:
- Running Asterisk 13.1.0 compiled from sources and using PJPROJECT. 
- Ubuntu 12.04 64bit




> IAX hits maxcallnumber limit of 2048 with only one concurrent channel
> ---------------------------------------------------------------------
>
>                 Key: ASTERISK-24478
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24478
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2
>    Affects Versions: 12.6.1
>         Environment: Linux autodial 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux
>            Reporter: POUILLY GUILLAUME
>            Severity: Critical
>         Attachments: maxcallnumber_count.log.bz2, maxcallnumber_full.log.bz2
>
>
> [Edit by Rusty - Even if we can't track down the issue here, we should  improve iax.conf to mention the 2048 default limit and describe the max values for maxcallnumbers and maxcallnumbers_nonvalidated]
> Hi, 
> With ARI, I create channels to make outbounds call via a IAX Trunk. After some time, i have on the asterisk cli :
> [Nov  1 16:14:46] ERROR[5236][C-00005077]: chan_iax2.c:2588 peercnt_add: maxcallnumber limit of 2048 for 10.100.5.1 has been reached!
> [Nov  1 16:14:46] WARNING[5236][C-00005077]: chan_iax2.c:12400 iax2_request: Unable to create call
> [Nov  1 16:14:46] WARNING[5236][C-00005077]: app_dial.c:2421 dial_exec_full: Unable to create channel of type 'IAX2' (cause 34 - Circuit/channel congestion)
> There is no maxcallnumber, on each side of the iax Trunk.
> core show channels:
> Channel              Location             State   Application(Data)
> IAX2/autodial_b-2918 (None)               Ringing AppDial((Outgoing Line))
> Local/0964158794 at REA (None)               Ring    Dial(IAX2/autodial_b/096415879
> 1 active channel
> 1 active call
> 20672 calls processed
> The active call does not exist in reality
>  module show like iax;
> Module                         Description                              Use Count  Status
> chan_iax2.so                   Inter Asterisk eXchange (Ver 2)          1          Running
> 1 modules loaded
> the asterisk cli stop working and i have to lauch it again.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list