[asterisk-bugs] [Asterisk 0012201]: Registration with SIP-provider never succeeds

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=12201 
====================================================================== 
Reported By:                reinerotto
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   12201
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.17 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 won't fix
Fixed in Version:           
====================================================================== 
Date Submitted:             03-12-2008 17:27 CDT
Last Modified:              03-13-2008 11:21 CDT
====================================================================== 
Summary:                    Registration with SIP-provider never succeeds
Description: 
When asterisk is started immediately after boot, AND DNS not available at
that time, registration with SIP-service provider does not succeed.
Unfortunately, then an infinite loop is entered, trying to register again,
failing again etc., even in case network and DNS are well up. Only a
restart of asterisk solves the problem.
Because of a bug in /etc/init.d/asterisk from SuSE exactly this can
happen.
Pls, refere to my previous report 12200 for details.
Fixing 12200 will avoid this situation to occure, but there might be other
scenarios, when registration never succeeds because of temporary DNS
problem.

It looks like, SIP-registration somehow does not "refresh completely"
DNS-info, when retrying registration AND very first registration attempt
already failed. 
====================================================================== 

---------------------------------------------------------------------- 
 russell - 03-13-08 11:21  
---------------------------------------------------------------------- 
This is not something that we will fix for Asterisk 1.4.  It requires
adding dnsmgr support to chan_sip, which is an invasive enough thing that
it can't be done for that release.  I would suggest ensuring asterisk does
not start after your networking comes up ... 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-13-08 11:21  russell        Status                   new => resolved     
03-13-08 11:21  russell        Resolution               open => won't fix   
03-13-08 11:21  russell        Assigned To               => russell         
03-13-08 11:21  russell        Note Added: 0083898                          
======================================================================