|Summary:||ASTERISK-04372: Queues stop calling members after a while|
|Reporter:||Roy Sigurd Karlsbakk (rkarlsba)||Labels:|
|Date Opened:||2005-06-08 06:58:55||Date Closed:||2011-06-07 14:10:32|
|Environment:||Attachments:||( 0) queues.conf|
|Description:||app_queue stops calling queue members after some time. this happened after adding another queue. we have some 20 members in total, many of them members of several queues. queue.conf is uploaded some anonymized.|
is there a way to debug this?
|Comments:||By: Clod Patry (junky) 2005-06-08 07:05:34|
when the problem starting to occurs, we'll need any tool to debug (CLI output and/or typescript, etc), with debug activated.
By: Roy Sigurd Karlsbakk (rkarlsba) 2005-06-08 08:00:03
Two members of one queue9 was only member of that queue, but did not receive calls from the queue. after adding them to another queue, they now receive calls from both queues...
By: Roy Sigurd Karlsbakk (rkarlsba) 2005-06-09 04:36:46
Now, with new config, suddenly members of certain queues stop receiving calls. just as before. no change done in weeks.
By: Roy Sigurd Karlsbakk (rkarlsba) 2005-06-09 08:40:39
problem seems to occur all the time. customers waiting in queue may sometimes get 'stuck' for a long time. then, suddenly, it might work again.
By: Roy Sigurd Karlsbakk (rkarlsba) 2005-06-09 09:53:22
it seems this error occurs when quite many are called at once.
it looks beter if using roundrobin
can someone please tell me what the penalty does? is this adjusted automatically?
By: Roy Sigurd Karlsbakk (rkarlsba) 2005-06-12 14:23:50
can someone please help me out here? i need information about how to debug this.
verbose=9 and debug=9 shows nothing special.
what is typescript?
By: Kevin P. Fleming (kpfleming) 2005-07-11 23:19:39
This is going to be hard to debug. You'll need to capture a snapshot of what the queue thinks the states of all the members/agents are at the _exact_ moment that you notice the problem.
By: Mark Spencer (markster) 2005-07-31 17:25:09
Closing due to lack of feedback from bug placer. Feel free to reopen if you can provide some diagnostic of the state of the agents.
By: Roy Sigurd Karlsbakk (rkarlsba) 2005-08-01 05:49:16
I need information on how to debug this.
Right now we have a queue where only one of the two members receive calls
By: Olle Johansson (oej) 2005-08-01 07:00:13
Maybe you can add hints for the agents and members and then list the status with "show hints" before and after.
By: Olle Johansson (oej) 2005-08-01 07:01:05
Can you check if this occurs in CVS head as well, so we can see if there's a difference?
By: Roy Sigurd Karlsbakk (rkarlsba) 2005-08-01 07:06:57
I only see this on a quite busy system running some 6-7 queues. I have no possibility to setup a HEAD system and move the traffic over, so it'll need to be debugged on the 1.0 installation. this happens every now and then, but I've not seen any pattern yet.
what are these hints? HEAD stuff?
By: Olle Johansson (oej) 2005-08-01 07:20:21
If you want to us to fix something in CVS head before it becomes a release, I would kindly ask you to fix some PC so you can help us test in CVS head.
Check the sample dialplan for hints, it's in there. I don't think "show hints" is in 1.0 though.
By: Olle Johansson (oej) 2005-08-01 07:21:19
Anyone else with ideas on how to debug this situation?
By: Roy Sigurd Karlsbakk (rkarlsba) 2005-08-01 07:23:58
Please explain how I can simulate the following:
- Three support centres with a total of about 25 agents
- some 7-8 active queues with patly overlapping members (some are members of several queues)
- between a few hundered to a few thousand calls per day
- call time, wait time etc varies
By: Olle Johansson (oej) 2005-08-01 10:23:25
It doesn't happen with only a few members and a few calls then? You can only reproduce this in a live environment?
By: Roy Sigurd Karlsbakk (rkarlsba) 2005-08-01 10:58:45
it usually takes weeks for this to show up and then it may show up for only some time. it took months before we became aware of the problem at all
By: Michael Jerris (mikej) 2005-08-27 01:14:58
No one has been able to duplicate this, and there is nothing that can be done without getting some sort of debug information. I am going to need to suspend this bug until you are able to produce some debug information. You may need to track down somone when this is happening to get them into your box to debug. Another possible route to test is to use the 1.2 beta, or wait for release 1.2 and see if you can reproduce the problem.