|Summary:||ASTERISK-13493: Modifying wrapup from dialplan or manager - Let a queue member get out of wrapup early|
|Reporter:||Fredrik Liljegren (fiddur)||Labels:|
|Date Opened:||2009-02-01 01:11:50.000-0600||Date Closed:||2011-06-07 14:02:38|
|Description:||After a queue call, the queue member goes into wrapup. I want to enable the member to end his wrapup faster, if he feels he can take a new call faster. Reasonably, he'd do this by pushing a button that cancels the wrapup.|
There is also the possibility he would want to prolong the wrapup. That is not as much an issue as he could pause his queue membership, but modifying the wrapup would be a more correct way to do it.
****** ADDITIONAL INFORMATION ******
I see that the way wrapuptime is implemented, this would not be easy to implement. And, what I would like to do later is having a cdr for the wrapup, which requires some kind of event sent when the wrapup is over, to be able to measure "after call work time".
Both these features would suggest that wrapup is implemented using some kind of state instead of just checking the time in ring_entry.
This is not an unusual scenario, see e.g. a wrapup-state implemented in dialplan instead: http://www.voip-info.org/wiki/view/Agents+without+agent+channel+Asterisk+1.4+AEL
I just think it would be better implemented in app_queue than having everybody doing their own wrapup-applications.
I'm prepared to do the coding after discussing implementation design...
|Comments:||By: Fredrik Liljegren (fiddur) 2009-02-01 01:26:04.000-0600|
Hmm, am I reading the code right in ring_entry, or is this correct assuming this scenario:
queue test1 has 40 seconds wrapuptime.
If tmp is SIP/1234, hasn't recieved any queue call, but had a normal call 30 seconds ago, he will still be considered in wrapup when a call comes in on test1?
So then, wrapup is supposed to be considered not just the time you need after a call from a certain queue, but the time you need to be free of calls before taking a call from this queue?
By: Mark Michelson (mmichelson) 2009-02-12 09:42:54.000-0600
Nope, the lastcall portion of a member is only updated on calls from the queue. This is what is used to gauge if the wrapuptime is still in effect for a member.
According to the bug guidelines, I have to close this issue, at least for now, since it is a feature request with no code attached. If you want to discuss implementation details further, the appropriate medium is the asterisk-dev mailing list. Once details have been worked out and you have code written, you can either re-open this or open a new ticket.