I am getting this error Exceptionally long voice queue length queuing to - From what I read the only solution to fix this
Asterisk version Asterisk 1.4.26
I understand we are now using asterisk 1.8 but to upgrade right at the moment is not an option so I am wondering how to fix this issue without re-installing or upgrading the asterisk software
[Jul 15 15:08:27] WARNING[7590]: channel.c:951 __ast_queue_frame: Exceptionally long voice queue length queuing to Local/192*168*001*175*78600075@default-9db3,1
[Jul 15 15:08:28] WARNING[7590]: channel.c:951 __ast_queue_frame: Exceptionally long voice queue length queuing to Local/192*168*001*175*78600075@default-9db3,1
[Jul 15 15:08:28] WARNING[7590]: channel.c:951 __ast_queue_frame: Exceptionally long voice queue length queuing to Local/192*168*001*175*78600075@default-9db3,1
[Jul 15 15:08:28] WARNING[7590]: channel.c:951 __ast_queue_frame: Exceptionally long voice queue length queuing to Local/192*168*001*175*78600075@default-9db3,1
[Jul 15 15:08:28] WARNING[7590]: channel.c:951 __ast_queue_frame: Exceptionally long voice queue length queuing to Local/192*168*001*175*78600075@default-9db3,1
[Jul 15 15:08:28] WARNING[7590]: channel.c:951 __ast_queue_frame: Exceptionally long voice queue length queuing to Local/192*168*001*175*78600075@default-9db3,1
[Jul 15 15:08:28] WARNING[7590]: channel.c:951 __ast_queue_frame: Exceptionally long voice queue length queuing to Local/192*168*001*175*78600075@default-9db3,1
[Jul 15 15:08:28] WARNING[7590]: channel.c:951 __ast_queue_frame: Exceptionally long voice queue length queuing to Local/192*168*001*175*78600075@default-9db3,1
[Jul 15 15:08:28] WARNING[7590]: channel.c:951 __ast_queue_frame: Exceptionally long voice queue length queuing to Local/192*168*001*175*78600075@default-9db3,1
To work round this, you are going to have to work out what the underlying cause is.
Well what I do know is this was not an issue before we turned on inbound for this campaign. So far what I can tell is if I close the users sip client and re-open the sip client it solves the issue.
It happens about once a day around 3pm based on Friday, Monday (logs) - That is on both days when the issue accorded and to fix it we rebooted the server - which then would not let users login.
We then told agents to quit Twinkle (Ubuntu 8, Codec G711a) and reopen there Twinkle. This seems to then de-register the SIP user and allows them to re-register there SIP account again.
Also issue seem to show up after we added two new asterisk servers and tried to get them communicating to the DB - which I still have not got working with the latest version of GoAutoDial.
I would say being in a call centre and seeing this issue it is most likely due to the amount of calls we are processing to each user - but then again we never had an issue like this before Thursday last week - when I added the two trunks to talk to the other servers running 1.8 asterisk.
Is there an issue with 1.4 talking to 1.8?
But then if there is - why would the agents on 1.4 who are logining into only 1.4 asterisk server having the issue - we are not yet using the other server due to issues we are having with auto dialling not working - Manual dialing works fine.
Have you had a resolution to this?
We are experiencing that error in Asterisk 1.4.44.
all users get their calls disconnected simultaneously when that happens.
We have that approx. ever 1.5 days.
That is if hyperthreading is turned off.
If I leave it on in the bios then we get it maybe 5-6 times a day.
seems to occur under moderate load, under high load with more staff on the phones the likelyhood seems not to increase.
Using RHEL 6.3
With our other pbx asterisk 1.2 on RHEL 5.4 we don’t have that issue.