Summary:	ASTERISK-27973: app_queue: QUEUESTATUS = CONTINUE instead LEAVEEMPTY
Reporter:	Valentin Safonov (val32)	Labels:	pjsip
Date Opened:	2018-07-19 02:51:42	Date Closed:	2018-08-14 05:01:29
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Applications/app_queue
Versions:	13.21.0	Frequency of Occurrence	Constant
Related Issues:	is caused by ASTERISK-25665 Duplicate logging in queue log for EXITEMPTY events
Environment:	CentOS 7.0	Attachments:	( 0) asterisk_13.21_log
Description:	I have Asterisk certified/13.21-cert2, simple dialplan: {noformat} exten => _X.,1,Answer same => n,Queue(400,ckt,,,10) same => n,Noop(queuestatus === ${QUEUESTATUS}) same => n,Hangup {noformat} And queue settings: {noformat} joinempty=yes leavewhenempty=strict {noformat} Queue 400 without active agents: {noformat} test_vd*CLI> queue show 400 400 has 0 calls (max unlimited) in 'rrordered' strategy (0s holdtime, 0s talktime), W:0, C:0, A:1, SL:0.0% within 0s   Members:      PJSIP/101 (ringinuse disabled) (Unavailable) has taken no calls yet   No Callers {noformat} So when i'm calling into queue 400 i'm getting QUEUESTATUS = CONTINUE. But it must be LEAVEEMPTY I checked another version of Asterisk 13.8, with the same settings and dialplan, and there it works correct (QUEUESTATUS = LEAVEEMPTY) I compared files app_queue.c in 13.21 and 13.8. It has a lot of changes. And if i change function wait_our_turn() in 13.21 like 13.8, then QUEUESTATUS works correct in 13.21 So it looks like a bug, right? More complete description of the problem: Asterisk log files with  'pjsip set logger on' in attachment. 1. i'm just calling from softphone (extension 102) to queue 400 2. i'm expecting to get QUEUESTATUS = LEAVEEMPTY according to https://wiki.asterisk.org/wiki/display/AST/Asterisk+11+Application_Queue and https://wiki.asterisk.org/wiki/display/AST/Using+queues.conf 3. but i got QUEUESTATUS = CONTINUE
Comments:	By: Asterisk Team (asteriskteam) 2018-07-19 02:51:44.617-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Joshua C. Colp (jcolp) 2018-07-19 04:14:13.427-0500 Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected and the location of documentation that led you to that expectation. 3. The behavior you actually encountered. To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines [2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information Additionally if this is a bug it will not be resolved in certified unless you have a support agreement with Digium. If you do have a support agreement you need to go through Digium support to receive help. By: Valentin Safonov (val32) 2018-07-19 08:47:46.688-0500 asterisk debugging log in attachment and i added more info in my header message above By: Friendly Automation (friendly-automation) 2018-08-14 05:01:31.377-0500 Change 9854 merged by Joshua Colp: app_queue: set QUEUESTATUS to LEAVEEMPTY instead of CONTINUE [https://gerrit.asterisk.org/9854|https://gerrit.asterisk.org/9854] By: Friendly Automation (friendly-automation) 2018-08-14 05:01:54.862-0500 Change 9857 merged by Joshua Colp: app_queue: set QUEUESTATUS to LEAVEEMPTY instead of CONTINUE [https://gerrit.asterisk.org/9857|https://gerrit.asterisk.org/9857] By: Friendly Automation (friendly-automation) 2018-08-14 05:02:05.794-0500 Change 9855 merged by Joshua Colp: app_queue: set QUEUESTATUS to LEAVEEMPTY instead of CONTINUE [https://gerrit.asterisk.org/9855|https://gerrit.asterisk.org/9855] By: Friendly Automation (friendly-automation) 2018-08-14 05:02:15.441-0500 Change 9856 merged by Joshua Colp: app_queue: set QUEUESTATUS to LEAVEEMPTY instead of CONTINUE [https://gerrit.asterisk.org/9856|https://gerrit.asterisk.org/9856]