[asterisk-bugs] [Asterisk 0015052]: registration fails if multiple peers are specified in sip.conf
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jun 24 13:01:13 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-24 13:01 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...
======================================================================
----------------------------------------------------------------------
(0106913) PTorres (reporter) - 2009-06-24 13:01
https://issues.asterisk.org/view.php?id=15052#c106913
----------------------------------------------------------------------
We have experienced something like this ( asterisk version 1.4.18 ) even
with only one register.
Somehow we think it has to do with DNS resolution problems, (but it may
expand to other cases). As a workaround we use IP addresses instead of
domain names when possible (most of the time luckily).
When this problem happens sip show registry shows 'request sent' , but
Chan_sip gets blocked, not a simple sip packet gets answered/sent to other
peers we tried to remove the problematic register line but 'sip reload'
does not work and after another attempt the console show something like
"Previous reload is pending"
The only 'solution' to unblock everything was to restart *
Issue History
Date Modified Username Field Change
======================================================================
2009-06-24 13:01 PTorres Note Added: 0106913
======================================================================
More information about the asterisk-bugs
mailing list