[asterisk-bugs] [Asterisk 0010406]: Asterisk stops processing calls

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10406 
====================================================================== 
Reported By:                callguy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10406
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.9  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             08-08-2007 11:44 CDT
Last Modified:              09-25-2007 05:42 CDT
====================================================================== 
Summary:                    Asterisk stops processing calls
Description: 
Asterisk stops processing calls in the sip channel at random intervals.
This appears to be related to reloading chan_sip.so. When this happens the
console partially locks up (show channels becomes unresponsive) and shortly
after sip processing ceases to function. 

Running bt attached. 
====================================================================== 

---------------------------------------------------------------------- 
 Ted Brown - 09-25-07 05:42  
---------------------------------------------------------------------- 
Hi,

we've just had another SIP lockup, all phones couldn't registered to the
Asterisk machine. Asterisk was compiled with the following flags:
DEBUG_THREADS,
DONT_OPTIMIZE and LOADABLE_MODULES.

Please see attached the following results of CLI commands:

- core show channels
- core show threads
- core show locks
- sip show peers

RAM level compsumtion was also increasing at a nearly constant rate of 3%
more each hour, at the moment of the lockup there was around 180MB of free
RAM memory. The system was running for almost 24 hours before the lockup.

Please ask for more information in case it helps. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-25-07 05:42  Ted Brown      Note Added: 0071063                          
======================================================================