[asterisk-bugs] [Asterisk 0012312]: [patch] DNS SRV lookups causing re-registration problems

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12312 
====================================================================== 
Reported By:                jrast
Assigned To:                bbryant
====================================================================== 
Project:                    Asterisk
Issue ID:                   12312
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             03-26-2008 17:38 CDT
Last Modified:              07-08-2008 17:31 CDT
====================================================================== 
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.
====================================================================== 

---------------------------------------------------------------------- 
 bbryant - 07-08-08 17:31  
---------------------------------------------------------------------- 
I've uploaded two new patches against 1.4 and trunk. jrast, please test and
see if they fix the issue you're having.

Some more improvements can be done to the way SRV records are fetched in
asterisk. The problem is now a srv record that has a high weight but causes
a connection problem still has the same chance to be used that it did the
first time (srv records are sorted by chance, according to a weight). 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-08-08 17:31  bbryant        Note Added: 0089915                          
======================================================================