[asterisk-bugs] [Asterisk 0011210]: SIP reload for large config halts SIP Processing

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11210 
====================================================================== 
Reported By:                dtyoo
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11210
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.13  
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             11-09-2007 16:06 CST
Last Modified:              11-12-2007 13:08 CST
====================================================================== 
Summary:                    SIP reload for large config halts SIP Processing
Description: 
It seems that asterisk stops processing sip for some amount of time during
reloads. This causes weird dialing behavior for our end users trying to
make / recieve calls during the reloads, and some of our sip endpoints
start re-registering to other, backup servers when the reloads occur. Do
you have any suggestions / thoughts on this? I was going to start looking
at realtime as a possible solution, but given the size and complexity of
our dialplan, and integration with our existing backend systems this is
probably not going to be a quick fix.
====================================================================== 

---------------------------------------------------------------------- 
 twilson - 11-12-07 13:08  
---------------------------------------------------------------------- 
We did NAT traversal handling with setting REGISTER timeouts very low so
you can then turn off the qualify handling.  As long as it is on at all it
will send them to everyone on reload. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-12-07 13:08  twilson        Note Added: 0073537                          
======================================================================