[asterisk-bugs] [Asterisk 0011007]: Circular call distribution no longer works

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11007 
====================================================================== 
Reported By:                bcnit
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   11007
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.13  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-17-2007 02:35 CDT
Last Modified:              10-17-2007 10:17 CDT
====================================================================== 
Summary:                    Circular call distribution no longer works
Description: 
In Asterisk 1.2, if I wanted to specifically state the order extensions
were run, I would use priorities and the 'roundrobin' strategy, for
example:

-----------------------------------
[queue]
strategy=roundrobin
timeout=10
retry=1

member => SIP/100,1
member => SIP/102,2
member => SIP/101,3
-----------------------------------

This would have the effect of ringing 100 for 10 seconds, then 102, then
101.

In Asterisk 1.4(.13) and being driven from realtime, this no longer works.
Using 'roundrobin' is now deprectaed and if the queue defined above were
called, 100 would ring for 10 seconds, then would ring for another 10
seconds and so on.

I suspect that this behaviour will break a lot of implementations when
they are upgraded to 1.4 - it's certainly broken two of ours.
====================================================================== 

---------------------------------------------------------------------- 
 bcnit - 10-17-07 10:17  
---------------------------------------------------------------------- 
Hmmm. OK, I take your point, but.......

Surely no answer from a member indicates that that member is "unavailable
in some way"? ;-)

Both sites have queues driven from realtime (MySQL), so I don't know how
this would work for the patch, but I'll have a play.

If that doesn't work, then I've worked out how to implement it with Local
channels and then I'll have a go at hacking the code to see if I can treat
no answer the same as a Busy/Congestion which is a better solution for me.
Perhaps a new option for the Queue command which says 'treat no answer as
unavailable'.

I have spoken to the EU and they are absolutely adamant that it used to
work on a 1.2 version. I will investigate... 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-17-07 10:17  bcnit          Note Added: 0072169                          
======================================================================