|Summary:||ASTERISK-20043: Queues with linear ring strategy|
|Reporter:||Gerald Lim (teotech)||Labels:|
|Date Opened:||2012-06-25 09:48:34||Date Closed:||2012-08-29 08:57:21|
|Environment:||Asterisk 126.96.36.199 on a x86_64 running Linux CentOS||Attachments:||( 0) Queue_701.txt|
|Description:||I am running asterisk version 188.8.131.52 with Freebx 184.108.40.206. I have a constant issue with the Ring Strategy with the Queue.|
Actually i have static agent with Ext 1000, 1002, 1003 and 1004 with 0 priority for each in the queue. I have put the ring strategy as Linear which is supposed to ring agent at the order specified (i.e 1000, 1002, 1003 and 1004 ).
But whenever i ring this queue, Ext 1000 will ring and then Ext 1002 will ring only 1 time and then Ext 1003 will ring and then Ext 1004 will ring only 1 time and so on.
It is as if skipping the next agent by ringing its ext only 1 time and then go to the next agent ext.
Any advise please?
P.s: the ring all strategy works with no issue.
|Comments:||By: Rusty Newton (rnewton) 2012-06-27 18:50:32.664-0500|
To confirm your description of the unexpected behavior:
You are saying that with a linear strategy set, it appears that every other static agent is rung only once (ignoring your set timeout?)
Can you include the appropriate files showing configuration, or include the output of the "queues show" CLI command for that particular queue? Please attach all debug or output in a text file and not in the comments or description.
By: Gerald Lim (teotech) 2012-07-04 05:55:03.399-0500
Please find attached the output of the queue call.
Queue was configured to ring linearly from 1001,1002 and 1003. Test was done from ext 1004 ringing the queue number 701.
The phone rang in this sequence 1001,1002,1001(only once),1003(only once),1001,1002,...
By: Rusty Newton (rnewton) 2012-07-06 16:39:00.549-0500
Looking through the debug, I see some weirdness in 1001 ringing for 10000ms a few times, then other times for 15000ms, 1002 and 1003 seem to consistently give up after 15000ms. That wouldn't match with the described behavior exactly, but might lead us to the problem.
This could be a configuration issue, a problem with FreePBX or a bug in Asterisk. To find out whether this is a bug in Asterisk you will need to reproduce this problem without FreePBX dialplan in place. Please reproduce with straight Asterisk and a similar, but simple queue setup with linear ringing strategy, then provide a full debug log during the process https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information along with a SIP packet trace so we can verify the calls out to the extensions.
The idea here is to remove the additional complexities that FreePBX is throwing into the situation so that we can see clearly if this is a bug.
By: Matt Jordan (mjordan) 2012-08-29 08:57:16.792-0500
Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information can be found at http://www.asterisk.org/developers/bug-guidelines