[asterisk-bugs] [Asterisk 0017151]: Playback deadlock?

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17151 
====================================================================== 
Reported By:                RobinFood
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17151
Category:                   Applications/app_playback
Reproducibility:            sometimes
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.2.6 
JIRA:                       SWP-1304 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-04-08 12:24 CDT
Last Modified:              2010-04-15 12:44 CDT
====================================================================== 
Summary:                    Playback deadlock?
Description: 
My issue is very close to the issue id 0014412. 

I'm using the Local channel to make a dialout calls.
I'm using the Playback application to play a gsm-file.
Sometimes (approximately 1 from 10 Playback calls) Playback application
stops to play after 1-5 seconds of a voice. Next-priority extensions does
not start. MixMonitor records a silence from * and a voice from a called
party. 
====================================================================== 

---------------------------------------------------------------------- 
 (0120489) RobinFood (reporter) - 2010-04-15 12:44
 https://issues.asterisk.org/view.php?id=17151#c120489 
---------------------------------------------------------------------- 
How can I check is the channel go away or still remain in the memory?

I think it goes away, because on the called party hangup there is the log
messages about hanging up both parties: at 01:23:39 there is the next
messages in the last attached log:
[Apr 14 01:23:39] DEBUG[16523] channel.c: Hanging up channel
'Local/790 at inbound-98b8;2'
[Apr 14 01:23:39] DEBUG[16522] channel.c: Hanging up channel
'Local/790 at inbound-98b8;1'

Maybe I used incorrect word to describe this issue, and this is really not
a deadlock, but how should I call it to be correct? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-15 12:44 RobinFood      Note Added: 0120489                          
======================================================================