Summary:	ASTERISK-24640: Registration pending stays forever after sip reload
Reporter:	Max Man (maxman)	Labels:
Date Opened:	2014-12-24 03:27:33.000-0600	Date Closed:	2015-01-21 07:35:31.000-0600
Priority:	Critical	Regression?
Status:	Closed/Complete	Components:	Channels/chan_sip/Registration
Versions:	13.0.1	Frequency of Occurrence	Constant
Related Issues:	is caused by ASTERISK-24067 chan_sip: upgrade registry and mwi object to ao2 is related to ASTERISK-24673 outgoing sip registers cannot be removed or modified without doing restart (or doing module unload chan_sip.so)
Environment:	FREEPBX Distro 6.12.65-22. faxdetect=no context=from-sip-external callerid=Unknown notifyringing=yes notifyhold=yes tos_sip=cs3 tos_audio=ef tos_video=af41 alwaysauthreject=yes useragent=FPBX-12.0.13(13.0.1) disallow=all allow=ulaw allow=alaw allow=gsm allow=g726 allow=g722 progressinband=no callevents=no language=ru rtpend=20000 rtpstart=10000 bindport=5060 jbenable=no minexpiry=60 defaultexpiry=120 registerattempts=0 maxexpiry=3600 notifyhold=yes notifyringing=yes srvlookup=no allowguest=no g726nonstandard=no videosupport=no maxcallbitrate=384 canreinvite=no rtptimeout=30 rtpholdtimeout=300 rtpkeepalive=0 checkmwi=10 registertimeout=20 nat=yes	Attachments:
Description:	If asterisk is not registered to one of remote peers (TRUNKs) f.e. remote server is unreachable, in console I see: multiple "Retransmitting #1...7 (NAT)" going to remote peer (registerattempts=0). But if a execute "sip reload" during that, it shows: NOTICE[2424]: chan_sip.c:15289 transmit_register: Strange, trying to register .... when registration already pending And after that no attempts are made to register to that peer (trunk), even if the remote server is reachable again (tested manually with blocking and unblocking its ip on the router). After "core restart gracefully" registration goes on fine.
Comments:	By: Rusty Newton (rnewton) 2015-01-09 19:36:36.291-0600 I can't reproduce this in the latest branch of 13. You'll have to provide us with the following: * sip.conf register line and full peer configuration, with which we can reproduce the issue. (substituting our own unreachable host of course) * Asterisk log demonstrating the issue https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information Be sure the log contains the output of "sip set debug on" (a SIP trace) along with the VERBOSE and DEBUG logger channels. Thanks! By: Max Man (maxman) 2015-01-14 14:38:42.881-0600 [RT-COM] disallow=all defaultuser=20002274991215111 type=peer secret=m6XXPKXptXLl nat=force_rport,comedia insecure=invite host=17.37.18.21 fromdomain=tel.rt.com dtmfmode=rfc2833 directmedia=no context=from-trunk canreinvite=no allow=alaw allow=ulaw allow=g729 20002274991215111:m6XXPKXptXLl@tel.rt.com/20002274991215111 Inspite of having in cli: core set verbose 5 core set debug 5 sip set debug on After sip reload, I see no more messages containing peer name, or ip, or domain except these two: [2015-01-14 23:11:16] NOTICE[16185]: chan_sip.c:15177 sip_reregister:    -- Re-registration for  20002274991215111@tel.rt.com [2015-01-14 23:11:16] NOTICE[16185]: chan_sip.c:15289 transmit_register: Strange, trying to register 20002274991215111@tel.rt.com when registration already pending By: Matt Jordan (mjordan) 2015-01-14 18:27:01.736-0600 Please provide the information Rusty requested using the instructions that he linked. A snippet of messages from the console is not a debug log. By: Matt Jordan (mjordan) 2015-01-19 13:58:28.267-0600 A possible patch for this has been put up on ASTERISK-24673. By: Matt Jordan (mjordan) 2015-01-19 16:35:26.227-0600 A slightly cleaned up patch for this issue has been put up on review board. If you can test it out, that would be greatly appreciated. Thanks!