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

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15052 
====================================================================== 
Reported By:                fsantulli
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   15052
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     resolved
Target Version:             1.6.1.2
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:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-05-07 11:07 CDT
Last Modified:              2009-07-13 18:26 CDT
====================================================================== 
Summary:                    [patch] 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
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0015139 SIP stops working with multiple REGISTE...
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-13 18:26 svnbot         Status                   assigned => resolved
2009-07-13 18:26 svnbot         Resolution               open => fixed       
======================================================================