[asterisk-bugs] [JIRA] (ASTERISK-24667) IAX hits maxcallnumber limit of 2048 after many calls and don't recover after hangup
Y Ateya (JIRA)
noreply at issues.asterisk.org
Tue Jan 6 17:25:34 CST 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-24667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Y Ateya updated ASTERISK-24667:
-------------------------------
Description:
NOTE: This might be clone of ASTERISK-24478 .
I saw the same problem as ASTERISK-24478 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 (rejected from GSM Gateway). 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 always 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 only solution then is to restart asterisk; reload didn't affect call number count.
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
was:
NOTE: This might be clone of ASTERISK-24478 .
I saw the same problem as ASTERISK-24478 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 (rejected from GSM Gateway). 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 always happen.
What happens occasionally 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 only solution then is to restart asterisk; reload didn't affect call number count.
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
> IAX hits maxcallnumber limit of 2048 after many calls and don't recover after hangup
> ------------------------------------------------------------------------------------
>
> Key: ASTERISK-24667
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-24667
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_iax2
> Affects Versions: 13.1.0
> Environment: Running Asterisk 13.1.0 compiled from sources and using PJPROJECT.
> Ubuntu 12.04 x86_64
> Reporter: Y Ateya
> Attachments: extensions_1.conf, extensions_2.conf, iax_1.conf, iax_2.conf, maxcallnumber_count.log.bz2, maxcallnumber_full.log.bz2, pjsip_1.conf
>
>
> NOTE: This might be clone of ASTERISK-24478 .
> I saw the same problem as ASTERISK-24478 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 (rejected from GSM Gateway). 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 always 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 only solution then is to restart asterisk; reload didn't affect call number count.
> 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
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list