[asterisk-bugs] [Asterisk 0016899]: srvlookup don't work with register

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16899 
====================================================================== 
Reported By:                jamicque
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16899
Category:                   Channels/chan_sip/Registration
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.1.16 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-02-24 12:33 CST
Last Modified:              2010-02-25 13:19 CST
====================================================================== 
Summary:                    srvlookup don't work with register
Description: 
srvlookup don't work with register. If one ip (host) is down asterisk won't
try to register to other host automatically as it does with invites and
will try to register to the same host (retransmission error in console). 
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0016492 SRV registration
related to          0016898 dnsmgr failes to match peer when SIP sr...
====================================================================== 

---------------------------------------------------------------------- 
 (0118567) lmadsen (administrator) - 2010-02-25 13:18
 https://issues.asterisk.org/view.php?id=16899#c118567 
---------------------------------------------------------------------- 
I'm going to acknowledge this for now, but I have a feeling this is
expected behaviour as I don't think Asterisk has been programmed to handle
this scenario. I will defer to another developer to answer that question
though. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-25 13:18 lmadsen        Note Added: 0118567                          
2010-02-25 13:18 lmadsen        Status                   new => acknowledged 
======================================================================