[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:                     new
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:              08-18-2007 14:04 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. 
====================================================================== 

---------------------------------------------------------------------- 
 callguy - 08-18-07 14:04  
---------------------------------------------------------------------- 
We have narrowed this somewhat. The peers that are causing this behavior
are polycom 601 phones which have multiple sidecars. We are seeing hung
notify messages, related to the call-limit and hints. 

We had originally thought the behavior was transferring a local channel to
a queue, then perhaps just using the local channel. 

We have modified our dialplan to use neither queues or local channels when
calling to these handsets, but have experienced the same behavior. The only
common thread is that these handsets have a significant amount of notify
traffic going to them for the hints, and from time to time the hints seem
to cause an issue getting a lock elsewhere, causing a race condition. 

Aside from the backtrace, is there additional data we can obtain the next
time it happens to help narrow down the exact problem? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-18-07 14:04  callguy        Note Added: 0069050                          
======================================================================