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

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
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:                     resolved
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:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             10-17-2007 02:35 CDT
Last Modified:              11-06-2007 14:50 CST
====================================================================== 
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.
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 11-06-07 14:50  
---------------------------------------------------------------------- 
Since the state of queue members is gotten from their (channel-level)
device state, attempting to modify the member's status from solely within
app_queue (especially in a thread-safe way) would be at the least
difficult, and at worst cause a bunch of new issues to surface. In either
case, the changes are too invasive to be introduced into 1.4 anyway.

Since I still have not been able to make the circular call distribution
work as described in 1.2, I can't see any sort of action taken with regards
to this as a bug fix.

I am going to go ahead and close this, especially since you have found a
workaround. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-06-07 14:50  putnopvut      Status                   assigned => resolved
11-06-07 14:50  putnopvut      Resolution               open => fixed       
11-06-07 14:50  putnopvut      Note Added: 0073231                          
======================================================================