[asterisk-bugs] [Asterisk 0012884]: Queue is treated as empty if it isn't, but no agents meet the QUEUE_MIN_PENALTY and QUEUE_MAX_PENALTY criteria
noreply at bugs.digium.com
noreply at bugs.digium.com
Thu Jun 19 15:11:38 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=12884
======================================================================
Reported By: bcnit
Assigned To: putnopvut
======================================================================
Project: Asterisk
Issue ID: 12884
Category: Applications/app_queue
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
Asterisk Version: 1.6.0-beta9
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 06-18-2008 12:19 CDT
Last Modified: 06-19-2008 15:11 CDT
======================================================================
Summary: Queue is treated as empty if it isn't, but no agents
meet the QUEUE_MIN_PENALTY and QUEUE_MAX_PENALTY criteria
Description:
In a situation where a call is placed into a queue as follows:
exten => s,n,Set(QUEUE_MAX_PENALTY=1)
exten => s,n,Set(QUEUE_MIN_PENALTY=1)
exten =>
s,n,Queue(${ORGCODE}_${ORGQUEUE},ih,,${ORGCODE}/announce-incoming)
)
The queue is deemed to be empty if there are no agents with a penalty of 1
as a member of the queue.
We use queuerules.conf to raise the QUEUE_MAX_PENALTY value to overflow
calls to other departments and in our case (and I can imagine, other
people's too), it is perfectly legitimate to have members with a penalty of
2 logged in and no members with penalty 1.
As a result of this, the function QUEUE_MEMBER() returns incorrect data
(i.e. QUEUE_MEMBER(free) may return the "number of logged-in members for
the specified queue available to take a call" as 10, but in reality and
because of the penalty issue, it is zero.
I have been able to work around this by checking QUEUE_MEMBER(count) after
I receive a JOINEMPTY bounce out, incrementing QUEUE_MAX_PRIORITY and
trying again, but this is far from ideal!
======================================================================
----------------------------------------------------------------------
putnopvut - 06-19-08 15:11
----------------------------------------------------------------------
Sorry about that. When issues are reported against 1.6.0, I tend to patch
trunk so that I can commit the change there and then merge that change into
1.6.0. I forgot to generate the patch for 1.6.0 so what's there is the
trunk patch. I have now added 12884v2-1.6.0.patch. This should apply
cleanly to an svn checkout of the 1.6.0 branch.
Issue History
Date Modified Username Field Change
======================================================================
06-19-08 15:11 putnopvut Note Added: 0088962
======================================================================
More information about the asterisk-bugs
mailing list