[asterisk-bugs] [Asterisk 0017396]: When caller exits due to EXITEMPTY in app_queue EXITUNAVAIL is written to queue_log.
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Apr 8 09:16:23 CDT 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17396
======================================================================
Reported By: aragon
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17396
Category: Applications/app_queue
Reproducibility: always
Severity: major
Priority: normal
Status: acknowledged
Asterisk Version: SVN
JIRA: SWP-1527
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): 1.4
SVN Revision (number only!): 265570
Request Review:
======================================================================
Date Submitted: 2010-05-25 10:28 CDT
Last Modified: 2011-04-08 09:16 CDT
======================================================================
Summary: When caller exits due to EXITEMPTY in app_queue
EXITUNAVAIL is written to queue_log.
Description:
I have tested multiple versions of 1.4 and I have never seen EXITEMPTY
written to queue_log.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0017334 [patch] [regression] CDRs being written...
======================================================================
----------------------------------------------------------------------
(0133538) aragon (reporter) - 2011-04-08 09:16
https://issues.asterisk.org/view.php?id=17396#c133538
----------------------------------------------------------------------
I have no issue with the way the caller is treated by Asterisk.
As far as I am concerned the caller should not enter the queue if all
agents are paused. I consider this queue to be unavailable in this
scenario and I expect and Asterisk does write EXITUNAVAIL to the queue_log
file.
If no agents are logged to this queue the queue is also unavailable to the
caller except when the caller is forced out of the queue I would expect
EXITEMPTY to be written to the queue_log file. EXITEMPTY is never written
to the queue_log file. The result is that agent statistical reports are
never able to differentiate caller overflow between all agents paused Vs.
no agents logged since EXITUNAVAIL is written to queue_log in both
scenarios. Obviously the two scenarios are different. Queue empty is not
the same as all members paused. I just want Asterisk to write EXITEMPTY to
the queue_log file when a caller is forced to exit due to no agents
logged.
I also tested leavwhenempty=strict
The result:
All members paused writes EXITEMPTY to queue_log file
No members logged writes EXITEMPTY to queue_log file
In this case I would expect all members paused to write EXITUNAVAIL to
queue_log file.
I also tested leavewhenempty=strict in combination with joinempty=yes
This writes EXITEMPTY in both scenarios.
I also tested leavewhenempty=strict in combination with joinempty=strict.
This writes EXITUNAVAIL in both scenarios
So Asterisk cannot seem to differentiate between all members paused Vs. no
members logged to write correct value to queue_log.
Issue History
Date Modified Username Field Change
======================================================================
2011-04-08 09:16 aragon Note Added: 0133538
======================================================================
More information about the asterisk-bugs
mailing list