[asterisk-bugs] [Asterisk 0015599]: Have another queue ringing strategy to ring all members with penalties between min/max

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15599 
====================================================================== 
Reported By:                pscs
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15599
Category:                   Applications/app_queue
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.0.10 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-07-28 10:41 CDT
Last Modified:              2009-08-20 16:28 CDT
====================================================================== 
Summary:                    Have another queue ringing strategy to ring all
members with penalties between min/max
Description: 
At the moment you cannot easily have a queue where certain extensions ring
initially and then after a while, other extensions are included (with a
'ringall' strategy).

The queuerules.conf looks as if it could be used to help with this
limitation, but it doesn't work because ringall will only ring the
extensions with the lowest penalty which are available.

So, if you have three extensions, with penalties 1,2,3 and the '1' one is
available but isn't being answered, the 2 & 3 extensions will not be
called. If you increase the 'QUEUE_MIN_PENALTY' from queuerules.conf, then
it will ring the '2' extension, but the '1' extension will stop ringing.
There is no way to have both the '1' and '2' extensions ringing at the same
time.

So, I would propose that another strategy be introduced to allow all
extensions between the QUEUE_MIN_PENALTY and QUEUE_MAX_PENALTY to be rung.
This would allow much more complex combinations of ringing extensions,
especially now that the queuerules.conf facility is present.

Looking at the source it does not look like this would be complex, and I'd
be happy to do it if it was considered worthwhile. (Basically adding a new
strategy with similar behaviour to QUEUE_STRATEGY_RINGALL, and a change to
calc_metric to give all callattempts the same metric if they pass the
penalty test).

(Also the name of the strategy is open for discussion - 'ringallv2' is
already used elsewhere... 'ringpriorities'?)


====================================================================== 

---------------------------------------------------------------------- 
 (0109421) lmadsen (administrator) - 2009-08-20 16:28
 https://issues.asterisk.org/view.php?id=15599#c109421 
---------------------------------------------------------------------- 
As this looks to be a feature request without a patch attached, we must
close this issue. If you are able to provide a patch, then please do reopen
this issue. Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-20 16:28 lmadsen        Note Added: 0109421                          
2009-08-20 16:28 lmadsen        Status                   new => closed       
2009-08-20 16:28 lmadsen        Resolution               open => no change
required
======================================================================