[asterisk-bugs] [Asterisk 0013242]: SIP registration does never work, in case DNS not available during firstregistration

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13242 
====================================================================== 
Reported By:                reinerotto
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   13242
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.4.21.1 
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-08-05 16:22 CDT
Last Modified:              2008-12-09 15:23 CST
====================================================================== 
Summary:                    SIP registration does never work, in case DNS not
available during firstregistration
Description: 
Effekt:
When asterisk is started, and DNS does not completely work in that instant
of time, sip registration will never succeed, even when DNS is OK
later on.

On my SuSE-LINUX 10.3, there is both a caching name server (named), and
asterisk.
named is started before asterisk.
However, named does not complete its initialization, before asterisk tries
to register SIP.
This might be caused by a slow/broken connection establishment to internet
via pppoe (DSL).
Then the following message shows up:

WARNING[3523] chan_sip.c:7595 transmit_register: Probably a DNS error for
registration to .... trying register again

But even after named works a bit later on, SIP registration never
succeeds.
Only restart of asterisk helps then immediately.
So it looks like, that the second and any further registration attempts do
not completely start "from scratch".
====================================================================== 

---------------------------------------------------------------------- 
 (0096035) russell (administrator) - 2008-12-09 15:23
 http://bugs.digium.com/view.php?id=13242#c96035 
---------------------------------------------------------------------- 
There is nothing we can do in Asterisk code to fix this.  You can see in
the logs that Asterisk is attempt to do a DNS lookup each time it retries
the registration.  You see "No such host" messages.  That comes out after a
DNS lookup fails.

Since this is an issue that exists outside of the Asterisk code, I'm
closing this out. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-12-09 15:23 russell        Note Added: 0096035                          
======================================================================