[asterisk-bugs] [Asterisk 0016240]: [patch] QUEUE_MEMBER(..., free) counts wrapping-up agents as available

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16240 
====================================================================== 
Reported By:                kkm
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16240
Category:                   Applications/app_queue
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.2.0-rc5 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-11-13 01:34 CST
Last Modified:              2009-11-16 10:05 CST
====================================================================== 
Summary:                    [patch] QUEUE_MEMBER(...,free) counts wrapping-up
agents as available
Description: 
the QUEUE_MEMBER dialplan function can return total members, logged-in
members and "free" members count. A member is counted as "free" immediately
after his call ends, even though its wrap-up time, if specified in
queues.conf, has not yet expired, and the queue will not actually route a
call to it.
====================================================================== 

---------------------------------------------------------------------- 
 (0113854) lmadsen (administrator) - 2009-11-16 10:05
 https://issues.asterisk.org/view.php?id=16240#c113854 
---------------------------------------------------------------------- 
I just tried to apply it to trunk, and it doesn't apply unfortunately. I
may be able to find the time to try and update it, but there is one chunk
of code that failed to apply, and I'm not sure if it was just because of an
offset it couldn't find, or if there is a code here that needs to be
updated -- I'm not a coder, so I'll need to see which of the two it is :) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-16 10:05 lmadsen        Note Added: 0113854                          
======================================================================