[asterisk-bugs] [JIRA] (ASTERISK-23998) channel.c: Exceptionally long voice queue length queuing to Local....

[Rusty Newton (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-23998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=220903#comment-220903 ] 

Rusty Newton commented on ASTERISK-23998:
-----------------------------------------

There is a lot going on. We need to be able to reproduce this to investigate. I'm unable to reproduce this without a lot of guesswork.

A few options to move forward:

1. Provide a complete freepbx backup that we can restore and then, with minimal effort reproduce the issue.

or

2. Provide step by step instructions on how to set up the scenario in a clean FreePBX install

3. Provide a set of Asterisk configuration files that we can drop in, set up a phone or two with and reproduce the issue. Include instructions of course..

>  channel.c: Exceptionally long voice queue length queuing to Local....
> ----------------------------------------------------------------------
>
>                 Key: ASTERISK-23998
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23998
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_local
>    Affects Versions: 11.10.0
>         Environment: CENTOS 5.10 both 32bit and 64bit
> uname -a : 2.6.18-371.9.1.el5
>            Reporter: Kampolis Ioannis
>            Assignee: Rusty Newton
>         Attachments: console, console_debug.tgz, core.show.locks, extensions_additional.conf, queues.conf, sip_additional.conf
>
>
> Two Queues:
> Queue 703 has one member 3304.
> Queue 702 has three members ()
> Once 3304 forwards (not using the asterisk feature code) all his calls to 702 a warning is issued channel.c: Exceptionally long voice queue length queuing to Local making the system unresponsive.
> This causes load more than 9 to a monster dual-cpu DELL R520 in a production environment with more than 20k calls per day. The issue is resolved once the call is terminated or with a restart of the pbx.



--
This message was sent by Atlassian JIRA
(v6.2#6252)