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

Kampolis Ioannis (JIRA) noreply at issues.asterisk.org
Tue Jul 8 11:30:56 CDT 2014


     [ https://issues.asterisk.org/jira/browse/ASTERISK-23998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kampolis Ioannis updated ASTERISK-23998:
----------------------------------------

    Status: Waiting for Feedback  (was: Waiting for Feedback)

Hi, thanks for the prompt response, I updated with debug information. As mentioned before the dialplan was generated by a clean freepbx install. If this is not suitable please do tell me to try to narrow down the dialplan.
I also included a core show locks output and a part of the sip configuration (even though I think it is not sip related). This is a configuration from a VM- not the actual production pbx for obvious reasons.

Best regards,

Ioannis

>  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: Kampolis Ioannis
>         Attachments: console, 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)



More information about the asterisk-bugs mailing list