[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:                   block
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.1.0 
Regression:                 No 
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-13 16:17 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
====================================================================== 

---------------------------------------------------------------------- 
 (0104712) fsantulli (reporter) - 2009-05-13 16:17
 https://issues.asterisk.org/view.php?id=15052#c104712 
---------------------------------------------------------------------- 
i'm used to configure codecs, t38 fields and other settings into sip
[section_names] so, why should i change a configuration considered
functional into other asterisk releases ? Do this can depend on dns servers
configured in resolv.conf ? why this problem does not appear when using
asterisk 1.6.0.9 ? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-13 16:17 fsantulli      Note Added: 0104712                          
======================================================================