[asterisk-bugs] [Asterisk 0015148]: [patch] Refactor queue member properties and add functions to retrieve/modify them

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15148 
====================================================================== 
Reported By:                atis
Assigned To:                eliel
====================================================================== 
Project:                    Asterisk
Issue ID:                   15148
Category:                   Applications/app_queue
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-05-18 18:32 CDT
Last Modified:              2009-05-21 11:06 CDT
====================================================================== 
Summary:                    [patch] Refactor queue member properties and add
functions to retrieve/modify them
Description: 
I'm trying to add QUEUE_MEMBER function which would allow to read/write
fields of member like penalty/calls/paused/lastcall/wrapuptime

Also there's refactoring for all kinds of access (dialplan
functions/AMI/CLI) to use the same mechanisms and update logics, allowing
to set +/- values relative to current value.

This is work-in-progress, there are some TODO's left in patch, and some
more refactoring has to be done.

I'm sharing this with eliel, as he is currently adding
per-member-wrapuptime which is a really good candidate for using the same
structure.
====================================================================== 

---------------------------------------------------------------------- 
 (0105226) atis (reporter) - 2009-05-21 11:06
 https://issues.asterisk.org/view.php?id=15148#c105226 
---------------------------------------------------------------------- 
Some idea of new feature based on this and per-member-wrapuptime

(18:52:18) philippel: if you have A and B with penalty 1, and C with
penalty 2, the normal behavior is never try C if A or B are available, and
not answering the phone is considered available. This is proper for
standard call centers, agents shoudl always answer or be busy talking
(18:52:44) philippel: however, there are many situaitons where you may
want to change the behavior and say if A or B don't answer there phone,
then it shoudl go to C
(18:52:51) atis_work: you could tweak it with wrapuptime
(18:53:01) philippel: how
(18:53:36) philippel: from what I understand and have played with, it wil
never escllate up to C if A and B can be run unless both are busy
(18:53:41) atis_work: well, if wrapuptime is high enough, A missing call
will get lastcall set to current time, and then wrapuptime kicks in
(18:54:04) atis_work: also, there's feature in development, that will
allow to change wrapuptime temporarily for agent
(18:54:35) atis_work: so, when you get NOANSWER in dialplan, you just set
wrapuptime for next call to 1 minute, and let ring other agents
(18:54:48) atis_work: or 5 minutes - depending on count of agents
(18:54:48) (hesco ir pametis šo istabuquit: Read error: 104 (Connection
reset by peer)).
(18:55:27) philippel: atis_work interesting approach, doens't wrapupttime
only apply if they answered the call though?
(18:55:51) atis_work: well.. i'm confident to change that :D
(18:56:17) atis_work: actually - wrapuptime applys always based on
lastcall
(18:56:42) atis_work: so, i'm thinking of letting user to update lastcall
upon missed call (optionally)
(18:56:56) atis_work: so, wrapuptime gets added - and agent still can't be
called
(18:57:26) atis_work: but yeah, that's quite complex system.. not for easy
enable-and-works
(18:57:53) atis_work: or few custom settings could be created based on
this mechanism
(18:58:02) atis_work: putnopvut: are you reading? :)
(18:59:16) philippel: atis_work well there are various ways to get the
starts and moons to line up that may get thigns working, but it would be
really nice to find a way to get penalties to work as described, ideally on
a per queue basis but on an all or nothing basis woudl be quite acceptable
as well (e.g. in general, usepenaltyonnoanswer=yes, somethign like that) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-21 11:06 atis           Note Added: 0105226                          
======================================================================