[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:                   block
Priority:                   normal
Status:                     new
Target Version:             1.4.27
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-06-25 08:07 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.

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0015052 [patch] registration fails if multiple ...
====================================================================== 

---------------------------------------------------------------------- 
 (0106972) fsantulli (reporter) - 2009-06-25 08:07
 https://issues.asterisk.org/view.php?id=15139#c106972 
---------------------------------------------------------------------- 
This bug is surely a DNS related problem, if you look over /main/dns.c
you'll find:
"Asterisk DNS is synchronus at this time. This means that if your DNS does
not work properly, Asterisk might not start properly or a channel may
lock."

Try to change nameservers in /etc/resolv.conf. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-25 08:07 fsantulli      Note Added: 0106972                          
======================================================================