[asterisk-bugs] [Asterisk 0015139]: SIP stops working with multiple REGISTER statements in sip.conf

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15139 
====================================================================== 
Reported By:                philipp2
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15139
Category:                   Channels/chan_sip/Registration
Reproducibility:            have not tried
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.24 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-05-17 08:58 CDT
Last Modified:              2009-05-17 09:43 CDT
====================================================================== 
Summary:                    SIP stops working with multiple REGISTER statements
in sip.conf
Description: 
System 1 (1.4.18, 2.8 GHz) with "register =>" statements in sip.conf, one
of them with sipgate.de. The SIP part of the system becomes unresponsive
after a couple of days. Removing the second "register =>" for sipgate.de
made the system stable.

System 2 (1.6 GHz, formerly 1.4.21 and now 1.4.24.1): Three "register =>"
statements to the SAME registrar (also Asterisk, btw). After a SIP RELOAD
the entire SIP part of the system becomes unresponsive, meaning that also
local LAN phones cannot register anymore. SIP SHOW REGISTRY shows "Request
Sent" (and sometimes "Unregistered" for one of the three). Reducing from 3
to 2 "register =>" statemens sometimes make things work, reducing from 3 to
1 heals it completely. Moreover: After the SIP RELOAD is issued on the CLI
there is no further output of any other CLI command, however with EXIT and
again an "asterisk -r" CLI output can be re-gained.

====================================================================== 

---------------------------------------------------------------------- 
 (0104893) philipp2 (reporter) - 2009-05-17 09:43
 https://issues.asterisk.org/view.php?id=15139#c104893 
---------------------------------------------------------------------- 
Possibly related: https://issues.asterisk.org/view.php?id=15052

tcpdump shows that in fact we are receiving registration responses ("200
OK" and "401 Unauthorized") from the remote registrar, however "SIP SET
DEBUG IP xxx" only reveals never-ending outbound "Retransmitting #x (no
NAT)" messages but no inbound SIP messages at all. So it appears that
Asterisk has stopped listening.

Please note that this issue is not 100% reproducible, sometimes it is
necessary to add a 4th or 5th "register =>" statement or issue SIP RELOAD
twice.

Retransmitting https://issues.asterisk.org/view.php?id=2 (no NAT) to
a.b.c.d:5060:
REGISTER sip:a.b.c.d SIP/2.0
Via: SIP/2.0/UDP 192.168.1.20:5060;branch=z9hG4bK0c9d8347;rport
From: <sip:4321 at a.b.c.d>;tag=as1359ea00
To: <sip:4321 at a.b.c.d>
Call-ID: 36233f5a4545d8076b76af432e0437ca at 127.0.0.1
CSeq: 122 REGISTER
User-Agent: Asterisk PBX
Max-Forwards: 70
Expires: 120
Contact: <sip:123 at 192.168.1.20>
Event: registration
Content-Length: 0

BTW: Shouldn't we see our own IP address here, as set with externip? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-17 09:43 philipp2       Note Added: 0104893                          
======================================================================