Summary:ASTERISK-14624: [patch] Improved penalty use with new ring strategy(penalty ringall), prioritized agents, and status updates.
Reporter:Rami (rami)Labels:
Date Opened:2009-08-10 06:59:37Date Closed:2011-06-07 14:00:59
Versions:Frequency of
Environment:Attachments:( 0) app_queue_changes.patch
( 1) app_queue_changes2.patch
Description:New ring strategy: penalty_ringall.
with this strategy the queue will first call all agents with lowest penalty, and move to next penalty when there is no answer or all busy, it will make use of the agent extension status to know if an agent is available or not (even if the agent is talking not from the queue), and will not even try call him when his extension is busy, it also supports autofill option to take the next call to the next penalty group.

Agents caller priority: agent-caller-priority=yes/no
when set to yes all incoming calls will try to talk with the agent they last spoken with, even if the agent called out to the number.

autopause option pauses the agent in all his queues and not only the one he missed the call(makes more sense...)

Comments:By: Ronald Chan (loloski) 2009-08-11 11:56:25

please provide the patch against SVN-Trunk in order for them to look at your patch, since 1.4 is already in a feature freeze state

By: Rami (rami) 2009-08-12 06:07:28

We need the patch for our call center application,
If 1.4 is at freeze state would using the patch for our own use breaks the GPL licence?

By: snuffy (snuffy) 2009-08-12 07:09:44

Rami: There is nothing wrong with putting a patch against 1.4 up on the tracker, to be accepted into the asterisk code base officially you must make the patch against trunk asterisk version.

By: Leif Madsen (lmadsen) 2009-08-20 16:22:43

Yes, please provide the patch against trunk as new features don't go into released branches. Thanks!

By: Leif Madsen (lmadsen) 2009-09-22 08:25:09

Closing this issue as there appears to be no interest from the reporter in moving this to trunk where new features live. Perhaps in the future they will revisit this issue and reopen it, and then supplying the updated patch.