Summary:	ASTERISK-27791: Getting Exception "Exceptionally long voice queue length queuing to"
Reporter:	shaurya jain (shaurya)	Labels:	webrtc
Date Opened:	2018-04-06 01:30:08	Date Closed:
Priority:	Major	Regression?
Status:	Open/New	Components:	pjproject/pjsip
Versions:	15.3.0	Frequency of Occurrence	Constant
Related Issues:
Environment:	Ubuntu 16.04,Webrtc,ARI,Stasis	Attachments:	( 0) ari_log_error
Description:	When we console dial the 5000 extension which is not configured in the extensions.conf then it shows direct NOTICE like and then hangup the call:- No such extension/context 6000@50 while calling Local channel But in case,If we dial that wrong extension through stasis then it comes up with the below warnings until we hangup the call manually. [Apr  5 17:50:29] NOTICE[9350] core_local.c: No such extension/context 5000@50 while calling Local channel [Apr  5 17:50:30] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2 [Apr  5 17:50:32] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2 [Apr  5 17:50:33] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2 [Apr  5 17:50:34] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2 [Apr  5 17:50:36] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2 [Apr  5 17:50:37] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2 [Apr  5 17:50:38] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2 [Apr  5 17:50:39] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2 [Apr  5 17:50:41] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2 [Apr  5 17:50:42] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2 [Apr  5 17:50:43] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2 [Apr  5 17:50:45] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2 [Apr  5 17:50:46] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2 [Apr  5 17:50:47] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2 [Apr  5 17:50:48] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2 [Apr  5 17:50:50] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2 [Apr  5 17:50:51] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2 [Apr  5 17:50:52] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2 [Apr  5 17:50:53] WARNING[9357] channel.c: Exceptionally long voice queue length queuing to Local/5000@50-00000012;2
Comments:	By: Asterisk Team (asteriskteam) 2018-04-06 01:30:09.739-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: shaurya jain (shaurya) 2018-04-06 01:31:42.376-0500 Attached are the ARI Logs for the same.Let me know the proceedings so we can handle this too. By: shaurya jain (shaurya) 2018-04-09 06:45:45.172-0500 Hello Team, Any update regarding this. By: Joshua C. Colp (jcolp) 2018-04-09 06:53:58.047-0500 This issue has not yet been triaged. Any updates or requests for additional information will be posted on it. Even after it is triaged there is no time frame on when it will get looked into and resolved. By: Kevin Harwell (kharwell) 2018-04-12 13:51:04.051-0500 You are seeing the "Exceptionally long voice queue length..." message because you have added three Local channels to a bridge that are "down". Once the third channel is added the underlying bridge technology switches to softmix, which then mixes the audio and sends it to each channel. In this case silence frames are written to each channel's queue. But since the each channel has nothing servicing their respective frame queues it fills up, thus the message. To avoid this make sure your channels are "up" and connected to something that can service their queues before putting them in the bridge, or at the very least before the 3rd channel is added. Or do as you are doing and then connect them afterward. You'll still see the message, but it will stop once the channels are "up" and their queues are being serviced. By: Kevin Harwell (kharwell) 2018-04-12 13:55:27.278-0500 I think one could argue that this is a bug. Softmix should probably not be writing audio frames to "down" Local channels. By: Kevin Harwell (kharwell) 2018-04-12 14:02:50.519-0500 To duplicate using ARI: 1. Create a mixing bridge. 2. Create three Local channels (for instance endpoint: Local/5000). 3. Add each of those channels to the bridge. By: Abhay Gupta (agupta) 2018-04-12 20:26:51.104-0500 Same problem comes on IAX channel . So it seems it is only IAX and Local channels which has the problem in bridge [Apr 12 16:10:40] WARNING[30689][C-0000d814] channel.c: Exceptionally long queue length queuing to IAX2/6_ster-32537 [Apr 12 16:10:40] WARNING[30689][C-0000d814] channel.c: Exceptionally long queue length queuing to IAX2/6_ster-32537 [Apr 12 16:10:40] WARNING[30689][C-0000d814] channel.c: Exceptionally long queue length queuing to IAX2/6_ster-32537 [Apr 12 16:10:40] WARNING[30689][C-0000d814] channel.c: Exceptionally long queue length queuing to IAX2/6_ster-32537 By: Abhay Gupta (agupta) 2018-04-12 20:48:07.342-0500 If a channel is down why it is not removed from bridge . ARI in any case is exposing the bridge so the technology itself should remove any channels which are down and release them . By: Kevin Harwell (kharwell) 2018-04-13 09:37:01.476-0500 {quote}Same problem comes on IAX channel . So it seems it is only IAX and Local channels which has the problem in bridge{quote} Yes, and It should happen with any channel type as well. {quote}If a channel is down why it is not removed from bridge . {quote} This ability was added in order to do things like early media using ARI. By: shaurya jain (shaurya) 2018-04-13 12:20:28.752-0500 So what we can do to avoid this as it impact a lot while in production. By: Kevin Harwell (kharwell) 2018-04-13 13:53:45.820-0500 {quote}So what we can do to avoid this as it impact a lot while in production.{quote} See my first comment above, but it really depends on your application and it's use. If don't need to then don't add the channels to the bridge until they are "up".