[asterisk-bugs] [Asterisk 0012312]: [patch] DNS SRV lookups causing re-registration problems
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Jan 9 16:49:50 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-09 16:49 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.
======================================================================
----------------------------------------------------------------------
(0097392) putnopvut (administrator) - 2009-01-09 16:49
http://bugs.digium.com/view.php?id=12312#c97392
----------------------------------------------------------------------
Having a look at bbryant's 1.4 patch, he only appears to do DNS lookups at
three times:
1) The first time we register
2) If sendto() fails at some point
3) If we get no response to our REGISTER and thus time out.
I think this is exactly what is needed here and will fix the issue. As far
as I'm concerned this patch is a go. Of course, it would be just amazing if
there is anyone out there that could give us a positive test result on it.
I would hate to commit code that looks correct but ends up having some
small problem.
I'm fairly certain the trunk patch is actually a step backwards since it
removes the dnsmgr functionality and doesn't actually change the operations
performed.
Issue History
Date Modified Username Field Change
======================================================================
2009-01-09 16:49 putnopvut Note Added: 0097392
======================================================================
More information about the asterisk-bugs
mailing list