[asterisk-bugs] [Asterisk 0011550]: Prodding channel... causes 100% utilization

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11550 
====================================================================== 
Reported By:                pj
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11550
Category:                   Channels/chan_sip/General
Reproducibility:            sometimes
Severity:                   block
Priority:                   normal
Status:                     new
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 92697 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-14-2007 08:37 CST
Last Modified:              12-26-2007 13:37 CST
====================================================================== 
Summary:                    Prodding channel... causes 100% utilization
Description: 
from time to time, asterisk is locked (100% cpu utilization, but not crash)
with "Prodding channel..." messages...
grep "SIP/777-082ae2f8" /var/log/asterisk/messages | wc -l
856979

in my case it happened in entering simple diaplan, calling MoH...
 555 => { Set(TIMEOUT(absolute)=60); MusicOnHold(); }
user is connected over wifi, so maybe some packet was lost in some
critical call stage, that causes sip channel starts looping?

unfortunately, I was not able to do some debugging, because asterisk pc
was completely locked, due to realtime priority of asterisk process...
====================================================================== 

---------------------------------------------------------------------- 
 russell - 12-26-07 13:37  
---------------------------------------------------------------------- 
There is a good chance this has already been fixed.  Please update and try
again.

Also, if it still happens, try to grab "core show locks" output while it
is freaking out.

$ sudo asterisk -rx "core show locks" > showlocks.txt 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-26-07 13:37  russell        Note Added: 0075967                          
======================================================================