|Summary:||ASTERISK-01846: app_queue does not behave as expected with empty queue.|
|Reporter:||Terry Wilson (twilson)||Labels:|
|Date Opened:||2004-06-17 08:06:56||Date Closed:||2011-06-07 14:09:59|
|Description:||According to the 'show application queue' command, app_queue is supposed to return 0 when the queue is empty. I would assume that this would exit the queue application and move to priority+1. It doesn't. It keeps the caller in the queue until the timeout value specified in the dial plan.|
****** ADDITIONAL INFORMATION ******
This could be by design, I suppose, but it seems like it would make sense to at least have the option for it to fall through to the next priority if all of the Agents are logged out. If you have a situation where you would normally want customers to be able to hold indefinitely, but all of you agents have gone home for the evening, you are going to have a really unhappy customer...
I know you can have them press a key to have them leave a message or use gotoiftime to set business hours, but the first they will still hold for an indeterminite amount of time for no reason and the second doesn't take into account if one of your agents decides to put in some overtime. Just my $0.02.
|Comments:||By: Brian West (bkw918) 2004-06-17 21:58:03|
Nope using queues doesn't behave like that at ALL. I suspect you have member => lines in your queues.conf file for the queue. If you do then people will be let into the queue when nobody is there to answer it. You have a few ways to get around this.
1. Use Option "n"
2. Use AddQueueMemeber and RemoveQueueMemeber like I do to put devices in and out of the queue on demand.
This is not a bug or a design flaw its working as it was written to work.... granted it needs to maybe be written better or something...
By: Brian West (bkw918) 2004-06-17 22:00:14
More of a config issue.. find me on IRC