[asterisk-bugs] [Asterisk 0012312]: [patch] DNS SRV lookups causing re-registration problems
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Jan 12 10:19:24 CST 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=12312
======================================================================
Reported By: jrast
Assigned To: putnopvut
======================================================================
Project: Asterisk
Issue ID: 12312
Category: Channels/chan_sip/Registration
Reproducibility: always
Severity: major
Priority: normal
Status: ready for review
Target Version: 1.6.2
Asterisk Version: 1.4.18
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-03-26 17:38 CDT
Last Modified: 2009-01-12 10:19 CST
======================================================================
Summary: [patch] DNS SRV lookups causing re-registration
problems
Description:
SIP peer uses DNS SRV records which list multiple entries for
_sip._udp.domain.
Asterisk is selecting one and successfully registering with it. When
attempting to re-register, Asterisk is not selecting the same host.
Instead it is ALWAYS selecting another host, sending seven SIP REGISTER
requests to it, then failing over to the next (correct) host, at which
point the re-register succeeds. However, this process exceeds the
registration expiry and the registration is timing out on every
re-registration cycle.
Peer in question is callcentric.com.
======================================================================
----------------------------------------------------------------------
(0097496) blitzrage (administrator) - 2009-01-12 10:19
http://bugs.digium.com/view.php?id=12312#c97496
----------------------------------------------------------------------
Seems to fail for me on 1.4:
*CLI> Really destroying SIP dialog
'6c82c48c3fa9c718646841dc1ce8a34a at 192.168.128.50' Method: REGISTER
[Jan 12 07:06:05] NOTICE[12445]: chan_sip.c:7597 sip_reregister: --
Re-registration for 1777289xxxx at callcentric.com
[Jan 12 07:06:05] DEBUG[12445]: chan_sip.c:7829 transmit_register: >>>
Re-using Auth data for 1777289xxxx at callcentric.com
REGISTER 13 headers, 0 lines
Reliably Transmitting (no NAT) to 0.0.0.0:5080:
REGISTER sip:callcentric.com:5080 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK265c1070;rport
From: <sip:1777289xxxx@>;tag=as4a8b9251
To: <sip:1777289xxxx@>
Call-ID: 6c82c48c3fa9c718646841dc1ce8a34a at 192.168.128.50
CSeq: 104 REGISTER
User-Agent: Asterisk PBX
Max-Forwards: 70
Authorization: Digest username="1777289xxxx", realm="callcentric.com",
algorithm=MD5, uri="sip:callcentric.com",
nonce="fccff47271971947b6663cc222d66786",
response="b2cabadb1aa107d7b2ffc46996b8dff2"
Expires: 60
Contact: <sip:1777289xxxx at 127.0.0.1>
Event: registration
Content-Length: 0
Issue History
Date Modified Username Field Change
======================================================================
2009-01-12 10:19 blitzrage Note Added: 0097496
======================================================================
More information about the asterisk-bugs
mailing list