[asterisk-bugs] [Asterisk 0012312]: 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:              06-26-2008 10:30 CDT
====================================================================== 
Summary:                    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 - 06-26-08 10:30  
---------------------------------------------------------------------- 
oej, yes, I'll update to use doxygen formats.

That line of code decides a new SRV record should be used if
handle_response_register got any response code in the 400 range that wasn't
a 401 or 407 which could be a response to an initial register.

I made an assumption in this patch that connection issues would be handled
by this area of the code receiving a timeout, but I could be wrong.

I wasn't sure if it would be worth attempting a new SRV record when one
failed for something besides a connection problem, but if this section of
code does get a timeout for connection issues this would be easy. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-26-08 10:30  bbryant        Note Added: 0089284                          
======================================================================