[asterisk-bugs] [Asterisk 0015052]: registration fails if multiple peers are specified in sip.conf
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Jun 25 03:35:28 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=15052
======================================================================
Reported By: fsantulli
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 15052
Category: Channels/chan_sip/Registration
Reproducibility: always
Severity: block
Priority: normal
Status: acknowledged
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:
======================================================================
Date Submitted: 2009-05-07 11:07 CDT
Last Modified: 2009-06-25 03:35 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
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
has duplicate 0015139 SIP stops working with multiple REGISTE...
======================================================================
----------------------------------------------------------------------
(0106964) fsantulli (reporter) - 2009-06-25 03:35
https://issues.asterisk.org/view.php?id=15052#c106964
----------------------------------------------------------------------
I agree with PTorres, the bug appears even with only one register. I
suppose it's only related to DNS operations, as i discovered that, when
peer is in "Request Sent" state, even when registration fails appears on
cli, an outgoing call to that peer will stop every message and the peer
magically goes into "Registered" state.
Also, i think that >1.4.18 and >1.6.1.0 are different bugs and should be
splitted.
Issue History
Date Modified Username Field Change
======================================================================
2009-06-25 03:35 fsantulli Note Added: 0106964
======================================================================
More information about the asterisk-bugs
mailing list