[asterisk-bugs] [Asterisk 0013755]: Avoiding deadlock for channel problem

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13755 
====================================================================== 
Reported By:                chivilis
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13755
Category:                   Core/Channels
Reproducibility:            sometimes
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.22 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-21 13:50 CDT
Last Modified:              2008-10-22 15:07 CDT
====================================================================== 
Summary:                    Avoiding deadlock for channel problem
Description: 
Hello, 

I have HP Proliant server with 1 E1 and 8 BRI Sangoma cards installed. I
have noticed that in period of one day I have and error, when user calls,
hears 'ringing' alert, agent answers, but user still hears 'ringing' tone.

I set debug mode in logger.conf and I noticed that when calls enters the
queue, and starts ringing 'Avoinding deadlock for channel' errors appears
and repeats many times.

All debug information is attached.
====================================================================== 

---------------------------------------------------------------------- 
 (0094169) putnopvut (administrator) - 2008-10-22 15:07
 http://bugs.digium.com/view.php?id=13755#c94169 
---------------------------------------------------------------------- 
You certainly could do that, but the problem is that the output is really
only helpful when the problem is occurring. Of course, I suppose that if
you set up a cron job to get that output every minute, then you will likely
also get the output while the problem is occurring, too. You'll just likely
also have a lot of output that won't be very helpful, though. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-22 15:07 putnopvut      Note Added: 0094169                          
======================================================================