[asterisk-bugs] [Asterisk 0015609]: [patch] WARNING[23025]: channel.c:952 __ast_queue_frame: Exceptionally long voice queue length queuing to Local

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15609 
====================================================================== 
Reported By:                aragon
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15609
Category:                   Core/Channels
Reproducibility:            have not tried
Severity:                   crash
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 206273 
Request Review:              
====================================================================== 
Date Submitted:             2009-07-29 09:26 CDT
Last Modified:              2009-09-22 09:44 CDT
====================================================================== 
Summary:                    [patch] WARNING[23025]: channel.c:952
__ast_queue_frame: Exceptionally long voice queue length queuing to Local
Description: 
Since upgrading to 1.4 SVN 206273 I see LOTS these errors when paging or
when calls are processed by app_queue.  When I see the messages during a
page I don't hear any paging (my Polycom phones continue to ring but no
paging audio).

I have no idea where the message is coming from how to reproduce, or
collect debug information for this specific issue.  I need help to find
root cause.
I think it could be caused by locking in autoservice since I see this lock
every time I see the warning message

=== Currently Held Locks ==============================================
=======================================================================
===
=== <file> <line num> <function> <lock name> <lock addr> (times locked)
===
=== Thread ID: 3057154960 (autoservice_run      started at [  238]
autoservice.c ast_autoservice_start())
=== ---> Waiting for Lock https://issues.asterisk.org/view.php?id=0
(autoservice.c): MUTEX 89 autoservice_run
&(&aslist)->lock 0x81798c8 (1)
=== --- ---> Locked Here: autoservice.c line 89 (autoservice_run)
=== -------------------------------------------------------------------


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0015109 [patch] Abort by memory allocator, poss...
related to          0015817 crash in local_attended_transfer, likel...
related to          0015845 Crash during attended transfer occurs
====================================================================== 

---------------------------------------------------------------------- 
 (0111188) aragon (reporter) - 2009-09-22 09:44
 https://issues.asterisk.org/view.php?id=15609#c111188 
---------------------------------------------------------------------- 
Leif,

I'll be back in the office tomorrow and will update Asterisk with
Russell's IAX2 patch.
Since Friday I have 16 core dumps that I must analyze for relevance.
IAX2 config does exist for a small test trunk but there is only traffic on
a SIP trunk.
The WARNING messages are generating regardless of trunk type.
I have tested the following trunk types:
SIP
IAX2
PRI

The test scripts do the following:
1. Multiple Asterisk servers hammer my test server through a SIP trunk.
Some of those Asterisk servers act as SIP clients to emulate many SIP
phones with an ACD agent login script.
2. Multiple agents answer calls while logged into queue with dynamic agent
login and /n option using Polycom IP550 phones with 3.1.3revC firmware.
3. After agent answer caller is transferred to another SIP extension with
native Asterisk attended transfer code. Once a Asterisk SIP client receives
a transferred call we auto answer with "weasels" prompt.

When the exceptionally long warning message appears multiple SIP
extensions become unavailable with SIP qualify in Asterisk for each
extension.
Total number of extensions on test server is about 100 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-22 09:44 aragon         Note Added: 0111188                          
======================================================================