Summary:	ASTERISK-16063: Registration process retries even though OK has been returned from the provider
Reporter:	John Covert (jcovert)	Labels:
Date Opened:	2010-05-06 13:05:30	Date Closed:	2011-07-26 15:16:02
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_sip/Registration
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) sip.conf ( 1) sipreg.txt
Description:	I am seeing the following behaviour with several providers. When asterisk first starts, registrations proceed well (usually).  As time goes on, the sip channel starts "missing" the "OK" responses to outgoing "REGISTER" messages.  In the example I've uploaded, the sixth retry succeeds, however, I've seen even the sixth fail, resulting in over 270 retries (all with responses which should have been accepted), and messages of the form "sip_reg_timeout:    -- Registration for 'user@provider' timed out, trying again (Attempt ASTERISK-41) I've uploaded a SIP DEBUG for your information; the first registration is OK; then it starts taking six "OK" responses before asterisk is happy.
Comments:	By: Paul Belanger (pabelanger) 2010-05-06 13:14:31 Please attach your sip.conf file. By: John Covert (jcovert) 2010-05-06 16:36:27 sanitized and attached. provider6 is the one that corresponds with the example sipreg.txt By: cappucinoking (cappucinoking) 2010-05-09 21:36:15 Does 1.6.2.8rc1 have this same issue? By: John Covert (jcovert) 2010-05-10 06:01:05 Yes, it does.  I just upgraded this morning, and the problem persists. By: John Covert (jcovert) 2010-07-05 14:04:35 Still seeing this on 1.6.2.9. By: Leif Madsen (lmadsen) 2011-07-26 15:15:56.798-0500 Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.4 and 1.6.x branches has ended. For continued maintenance support please move to the 1.8 branch which is a long term support (LTS) branch. For more information about branch support, please see https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions If this is still an issue, please open a new issue so it can be re-triaged appropriately. Thanks!