Page 1 of 1

[BUG] Exceptionally long voice queue length

PostPosted: Thu Oct 28, 2010 12:51 am
by gohar
Kernel Version 2.6.18-194.8.1.el5.goPAE (SMP)
Distro Name GoAutoDial CE 2.0

I've a test setup consisting of one GoAutoDial and one plain asterisk connected together on LAN via SIP trunk. When I Dial call from GoAutoDial to other asterisk Box it gives me following strange output on CLI before actually handing call onto other server.


[Oct 27 11:29:09] WARNING[30112] channel.c: Exceptionally long voice queue length queuing to Local/8600051@default-a294,1
[Oct 27 11:29:09] WARNING[30112] channel.c: Exceptionally long voice queue length queuing to Local/8600051@default-a294,1
[Oct 27 11:29:09] WARNING[30112] channel.c: Exceptionally long voice queue length queuing to Local/8600051@default-a294,1
[Oct 27 11:29:09] WARNING[30112] channel.c: Exceptionally long voice queue length queuing to Local/8600051@default-a294,1
[Oct 27 11:29:09] WARNING[30112] channel.c: Exceptionally long voice queue length queuing to Local/8600051@default-a294,1
[Oct 27 11:29:09] WARNING[30112] channel.c: Exceptionally long voice queue length queuing to Local/8600051@default-a294,1
[Oct 27 11:29:09] WARNING[30112] channel.c: Exceptionally long voice queue length queuing to Local/8600051@default-a294,1
[Oct 27 11:29:09] WARNING[30112] channel.c: Exceptionally long voice queue length queuing to Local/8600051@default-a294,1
[Oct 27 11:29:09] WARNING[30112] channel.c: Exceptionally long voice queue length queuing to Local/8600051@default-a294,1
[Oct 27 11:29:09] WARNING[30112] channel.c: Exceptionally long voice queue length queuing to Local/8600051@default-a294,1
[Oct 27 11:29:09] WARNING[30112] channel.c: Exceptionally long voice queue length queuing to Local/8600051@default-a294,1
[Oct 27 11:29:09] WARNING[30112] channel.c: Exceptionally long voice queue length queuing to Local/8600051@default-a294,1
[Oct 27 11:29:09] WARNING[30112] channel.c: Exceptionally long voice queue length queuing to Local/8600051@default-a294,1


Here is the dialplan entry in GoAutoDial Box where Call is routed.

exten => 200,1,Answer()
exten => 200,n,Dial(SIP/123.123.132.213/4777888)
exten => 200,n,Hangup()


This gives me a delay of around 15 sec on each call between the two servers till then this WARNING keeps on showing up.

PostPosted: Thu Oct 28, 2010 3:08 pm
by williamconley
You must always post your vicidial version with build when posting (after all this may be the goautodial section, but it's the vicidial.org forum, right? :) )

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system.

Similar to This:
Vicibox X.X from .iso | Vicidial X.X.X Build XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation
_________

But you DID post your installation method, which is helpful.

What we do not know, however, is enough to make it difficult to answer your question. Asterisk version on both sides of the call would be good. Dial plan on both sides of the call would be excellent. And does this happen on calls to other providers/protocols/codecs would cap it off quite nicely.

Also, is this a fresh install with no other issues or an old install that this call method worked on yesterday but does not now ... or ...? :)

here it is...

PostPosted: Mon Nov 01, 2010 12:54 am
by gohar
goautodial-ce-2.0-final.ISO | VICIDIAL VERSION: 2.2.1-237 BUILD: 100510-2015 | Asterisk 1.4.27.1-1 | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation

I hope this'll do good.

PostPosted: Mon Nov 01, 2010 9:30 pm
by williamconley
williamconley wrote:Dial plan on both sides of the call would be excellent. And does this happen on calls to other providers/protocols/codecs would cap it off quite nicely.

Also, is this a fresh install with no other issues or an old install that this call method worked on yesterday but does not now ... or ...? :)

PostPosted: Fri Nov 05, 2010 2:39 pm
by gardo
Load average when this happens? Hardware specs?