[asterisk-bugs] [Asterisk 0011080]: SIP channel stops processing calls, but no apparent deadlock

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11080 
====================================================================== 
Reported By:                callguy
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   11080
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.13  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-24-2007 15:58 CDT
Last Modified:              01-04-2008 13:06 CST
====================================================================== 
Summary:                    SIP channel stops processing calls, but no apparent
deadlock
Description: 
Approximately once per week we are seeing asterisk stop processing SIP
calls. The behavior is the same as a deadlock, but core show locks does not
show any evidence that there is a deadlock. 

The only way to resolve is to restart asterisk. 

output of:
core show locks
info thread
thread apply all bt

from the running process is attached.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0011165 Deadlock in channel.c
====================================================================== 

---------------------------------------------------------------------- 
 russell - 01-04-08 13:06  
---------------------------------------------------------------------- 
callguy:  Your locks output is very similar to that from the person that
just reported that their problem appears to be solved.  Given that, it
would be worth updating to the latest code in svn when you feel that it is
a good time to do so. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-04-08 13:06  russell        Note Added: 0076299                          
======================================================================