Summary:	ASTERISK-09531: Wrong "Got 200 OK on REGISTER that isn't a register"
Reporter:	Arcadiy Ivanov (arcivanov)	Labels:
Date Opened:	2007-05-27 22:15:46	Date Closed:	2007-06-22 13:30:48
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_sip/Registration
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) siplog_with_debug.txt ( 1) siplog.txt
Description:	OPTION results in 404 REGISTER with no username/secret results in 100, then in 401 REGISTER with username/secret results in 100, then in 200 No duplicate packets are received. Asterisk first reports [May 27 22:33:23] NOTICE[17995]: chan_sip.c:12171 handle_response_register: Outbound Registration: Expiry for sip.telphin.com is 1800 sec (Scheduling reregistration in 1785 s) and then out of the blue [May 27 22:33:23] WARNING[17995]: chan_sip.c:12106 handle_response_register: Got 200 OK on REGISTER that isn't a register even though no invalid/unexpected packets were received. I still can receive incoming calls even though I'm not sure Asterisk is even aware that it successfully registered with the SIP proxy. ****** ADDITIONAL INFORMATION ****** The bug might be related to 0009314
Comments:	By: Arcadiy Ivanov (arcivanov) 2007-05-27 22:48:12 Correction: judging by "sip show registry" Asterisk is aware that it is registered with sip.telphin.com. Re-register period is also normal (expiry - 15 sec). By: Arcadiy Ivanov (arcivanov) 2007-05-29 23:45:56 I don't have any particular objection to relating the bug to 9314, however I'd like to stress that in this case there appear to be *NO* duplicate packets received (or at least none displayed in sip debug mode). By: Olle Johansson (oej) 2007-05-30 01:22:36 No, this is a different issue than ASTERISK-9043. Can you repeat this with debug logging on? Thanks. By: Arcadiy Ivanov (arcivanov) 2007-05-30 07:25:55 Revision: 1.4 HEAD (currently 66601). console => notice,warning,error,debug Actually, no new messages as I can see. By: Joshua C. Colp (jcolp) 2007-06-22 11:53:27 You have to do set debug 9 in order to have debug messages from the core show up. In this case I think those would be very helpful. By: Arcadiy Ivanov (arcivanov) 2007-06-22 13:26:45 Running revision 71004. Issue has disappeared completely. By: Joshua C. Colp (jcolp) 2007-06-22 13:30:48 Great! Closed since it seems to have been fixed.