[asterisk-bugs] [JIRA] (ASTERISK-17636) Re-registration of SIP gateway sometimes occurs after the scheduled delay which causes gateway to see asterisk as unregistered
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Tue Jan 2 08:41:55 CST 2018
[ https://issues.asterisk.org/jira/browse/ASTERISK-17636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asterisk Team updated ASTERISK-17636:
-------------------------------------
Assignee: Joshua Colp (was: Fred Peters)
Status: Open (was: Waiting for Feedback)
> Re-registration of SIP gateway sometimes occurs after the scheduled delay which causes gateway to see asterisk as unregistered
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: ASTERISK-17636
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-17636
> Project: Asterisk
> Issue Type: Bug
> Components: Channels/chan_sip/Registration
> Affects Versions: 1.6.2.15
> Reporter: Fred Peters
> Assignee: Joshua Colp
> Attachments: messages.txt
>
>
> Note: the version reported by asterisk is 1.6.2.5 (not found in the product version field of Mantis)
> We have this problem on several asterisk installations.
> We have some external SIP gateways we register to with a time-out of 120 seconds
> Asterisk schedules a re-register every 105 second which is fine.
> However, a few times a day, the re-registration occurs too late. This has the side effect of becoming invalid for the outside gateway point of view. On that outside gateway we have some specific rules in case asterisk is no more registered, so this problem causes missed calls if they occur within that "unregistered" period
> Asterisk does not seems to be busy when the late re-registration occurs.
> ****** ADDITIONAL INFORMATION ******
> Below an extract of log which shows that re-register always occurs regularly excepted once where a comment has been inserted:
> [Mar 31 08:01:22] NOTICE[1711] chan_sip.c: -- Re-registration for 085519360 at sip.3starsnet.com
> [Mar 31 08:03:08] NOTICE[1711] chan_sip.c: -- Re-registration for 085519360 at sip.3starsnet.com
> [Mar 31 08:04:53] NOTICE[1711] chan_sip.c: -- Re-registration for 085519360 at sip.3starsnet.com
> [Mar 31 08:06:38] NOTICE[1711] chan_sip.c: -- Re-registration for 085519360 at sip.3starsnet.com
> [Mar 31 08:08:24] NOTICE[1711] chan_sip.c: -- Re-registration for 085519360 at sip.3starsnet.com
> [Mar 31 08:10:09] NOTICE[1711] chan_sip.c: -- Re-registration for 085519360 at sip.3starsnet.com
> [Mar 31 08:11:54] NOTICE[1711] chan_sip.c: -- Re-registration for 085519360 at sip.3starsnet.com
> [Mar 31 08:13:40] NOTICE[1711] chan_sip.c: -- Re-registration for 085519360 at sip.3starsnet.com
> [Mar 31 08:15:25] NOTICE[1711] chan_sip.c: -- Re-registration for 085519360 at sip.3starsnet.com
> [Mar 31 08:17:10] NOTICE[1711] chan_sip.c: -- Re-registration for 085519360 at sip.3starsnet.com
> [Mar 31 08:18:56] NOTICE[1711] chan_sip.c: -- Re-registration for 085519360 at sip.3starsnet.com
> [Mar 31 08:20:41] NOTICE[1711] chan_sip.c: -- Re-registration for 085519360 at sip.3starsnet.com
> [Mar 31 08:22:26] NOTICE[1711] chan_sip.c: -- Re-registration for 085519360 at sip.3starsnet.com
> [Mar 31 08:24:12] NOTICE[1711] chan_sip.c: -- Re-registration for 085519360 at sip.3starsnet.com
> ==> here we should have a re-register at 8:25:57
> [Mar 31 08:26:38] NOTICE[1711] chan_sip.c: -- Re-registration for 085519360 at sip.3starsnet.com
> [Mar 31 08:28:23] NOTICE[1711] chan_sip.c: -- Re-registration for 085519360 at sip.3starsnet.com
> [Mar 31 08:30:08] NOTICE[1711] chan_sip.c: -- Re-registration for 085519360 at sip.3starsnet.com
> Here is another extract of log file:
> You an see at 00:23:49 that re-registration is scheduled in 105 sec -> should
> occur at 00:25:34, but it will only occurs at 00:26:41
> SIP messages have been simplied to make it easier to read, but they were containing normal and successfull responses.
> [Mar 31 00:23:49] VERBOSE[1711] chan_sip.c: --- (10 headers 0 lines) ---
> [Mar 31 00:23:49] VERBOSE[1711] chan_sip.c: Scheduling destruction of SIP dialog '0eb640890787bd0910dc09b4613491f8 at 192.168.1.100' in 32000 ms (Method: REGISTER)
> [Mar 31 00:23:49] NOTICE[1711] chan_sip.c: Outbound Registration: Expiry for sip.3starsnet.com is 120 sec (Scheduling reregistration in 105 s)
> [Mar 31 00:24:21] VERBOSE[1711] chan_sip.c: Really destroying SIP dialog '0eb640890787bd0910dc09b4613491f8 at 192.168.1.100' Method: REGISTER
> [Mar 31 00:24:42] VERBOSE[1711] chan_sip.c: Reliably Transmitting (no NAT) to 85.119.188.3:5060:
> OPTIONS sip:sip.3starsnet.com SIP/2.0^M
> Via: SIP/2.0/UDP 192.168.1.100:5060;branch=z9hG4bK5c214d56;rport
> ....
> [Mar 31 00:24:42] VERBOSE[1711] chan_sip.c:.
> <--- SIP read from UDP:85.119.188.3:5060 --->
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP 192.168.1.100:5060;branch=z9hG4bK5c214d56;rport=64508
> ....
> [Mar 31 00:24:42] VERBOSE[1711] chan_sip.c: --- (9 headers 0 lines) ---
> [Mar 31 00:24:42] VERBOSE[1711] chan_sip.c: Really destroying SIP dialog '362d4deb7e5f5ed744b6f2074c3cb115 at 192.168.1.100' Method: OPTIONS
> [Mar 31 00:25:42] VERBOSE[1711] chan_sip.c: Reliably Transmitting (no NAT) to 85.119.188.3:5060:
> OPTIONS sip:sip.3starsnet.com SIP/2.0^M
> Via: SIP/2.0/UDP 192.168.1.100:5060;branch=z9hG4bK4cf9581b;rport
> ....
> [Mar 31 00:25:42] VERBOSE[1711] chan_sip.c:.
> <--- SIP read from UDP:85.119.188.3:5060 --->
> SIP/2.0 200 OK^M
> Via: SIP/2.0/UDP 192.168.1.100:5060;branch=z9hG4bK4cf9581b;rport=64508
> ...
> [Mar 31 00:25:42] VERBOSE[1711] chan_sip.c: --- (9 headers 0 lines) ---
> [Mar 31 00:25:42] VERBOSE[1711] chan_sip.c: Really destroying SIP dialog '3378a1b9729be9593d552cad4045ed7b at 192.168.1.100' Method: OPTIONS
> [Mar 31 00:26:41] NOTICE[1711] chan_sip.c: -- Re-registration for 085519360 at sip.3starsnet.com
> [Mar 31 00:26:41] VERBOSE[1711] dnsmgr.c: > doing dnsmgr_lookup for 'sip.3starsnet.com'
> [Mar 31 00:26:41] VERBOSE[1711] chan_sip.c: REGISTER 12 headers, 0 lines
> [Mar 31 00:26:41] VERBOSE[1711] chan_sip.c: Reliably Transmitting (no NAT) to 85.119.188.3:5060:
> REGISTER sip:sip.3starsnet.com SIP/2.0
> Via: SIP/2.0/UDP 192.168.1.100:5060;branch=z9hG4bK64adec24;rport
> ...
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list