[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 16:19:51 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 16:19 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...
======================================================================
----------------------------------------------------------------------
(0133557) jrose (manager) - 2011-04-08 16:19
https://issues.asterisk.org/view.php?id=17396#c133557
----------------------------------------------------------------------
Well, it isn't really a bug though. It's strictly a matter of terminology.
And inside of Asterisk proper, the exit status is LEAVEUNAVAIL when
someone gets ejected from a queue due to mass pausing, so that's what you'd
normally expect right?
You can pretty easily perform a workaround simply by checking for that
exist status and editing the log yourself using a shell command cat with
append for the log file in question if it encounters ${QUEUESTATUS} ==
LEAVEUNAVAIL.
If you want to pursue this further, please create a new issue with... I'd
guess text as the severity.
Issue History
Date Modified Username Field Change
======================================================================
2011-04-08 16:19 jrose Note Added: 0133557
======================================================================
More information about the asterisk-bugs
mailing list