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

[Asterisk Bug Tracker]

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-10 09:56 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0097425) blitzrage (administrator) - 2009-01-10 09:56
 http://bugs.digium.com/view.php?id=12312#c97425 
---------------------------------------------------------------------- 
Is it possible callcentric fixed something on their end? I cannot get this
to fail at all. I see registrations going to separate IPs each time a
re-registration happens:

For example:

[Jan 10 06:45:51] NOTICE[25009]: chan_sip.c:7588 sip_reregister:    --
Re-registration for  1777289XXXX at callcentric.com
[Jan 10 06:45:51] DEBUG[25009]: chan_sip.c:7817 transmit_register:    >>>
Re-using Auth data for 1777289XXXX at callcentric.com
REGISTER 13 headers, 0 lines
Reliably Transmitting (no NAT) to 204.11.192.23:5080:


Then next time...

[Jan 10 06:46:35] NOTICE[25009]: chan_sip.c:7588 sip_reregister:    --
Re-registration for  1777289XXXX at callcentric.com
[Jan 10 06:46:35] DEBUG[25009]: chan_sip.c:7817 transmit_register:    >>>
Re-using Auth data for 1777289XXXX at callcentric.com
REGISTER 13 headers, 0 lines
Reliably Transmitting (no NAT) to 204.11.192.37:5080:



So I'm seeing it change the IP address, but I never get a failure.

Sorry, so I'm not sure how to reproduce this in order to determine if the
patch helps or hurts :)

I can apply the patch if requested and try it to see if it has any
negative effects I suppose. Just let me know! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-10 09:56 blitzrage      Note Added: 0097425                          
======================================================================