[asterisk-bugs] [Asterisk 0015052]: registration fails if multiple peers are specified in sip.conf

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15052 
====================================================================== 
Reported By:                fsantulli
Assigned To:                lmadsen
====================================================================== 
Project:                    Asterisk
Issue ID:                   15052
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.1.0 
Regression:                 Yes 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-05-07 11:07 CDT
Last Modified:              2009-05-15 08:15 CDT
====================================================================== 
Summary:                    registration fails if multiple peers are specified
in sip.conf
Description: 
if i use only one register line and only one peer is configured in
sip.conf, registration works okey. If i add a registration line for another
proxy and i add the relative section, asterisk wants to resolve
[section_name] as hostname and registration fails
====================================================================== 

---------------------------------------------------------------------- 
 (0104814) lmadsen (administrator) - 2009-05-15 08:15
 https://issues.asterisk.org/view.php?id=15052#c104814 
---------------------------------------------------------------------- 
After talking to file on IRC, he has asked I request a SIP debug of this
failing to try and determine if the packets are not actually getting sent.
Those messages may not actually be indicating the real issue.

He has mentioned that he was able to reproduce it by using a nameserver
that doesn't resolve invalid hosts. So my network configuration must be
causing this to not fail for me.

Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-15 08:15 lmadsen        Note Added: 0104814                          
======================================================================