Summary:	ASTERISK-27325: app_queue: Agent stays in use after call is parked using DTMF
Reporter:	Andres Miedzowicz (amiedzow)	Labels:
Date Opened:	2017-10-08 17:58:18	Date Closed:
Priority:	Major	Regression?
Status:	Open/New	Components:	Applications/app_parkandannounce Applications/app_queue
Versions:	13.17.0	Frequency of Occurrence	Constant
Related Issues:
Environment:	OS: CentOS 6.7 Kernel: 2.6.32-573.22.1.el6.x86_64 Asterisk version: 13.17.0 Hardware: Dell PE R200	Attachments:	( 0) CLI_Commands.txt ( 1) CLI_Commands.txt ( 2) CLI_Commands.txt ( 3) configuration.txt ( 4) configuration.txt ( 5) configuration.txt ( 6) log.txt ( 7) log.txt ( 8) log.txt
Description:	Call parking is configurated in Asterisk 13.17.0 (using PJSIP) using the default settings in res_parking.conf and features.conf. When a call enters a queue and the agent that picked up the call parks it, the status of that agent stays "In Use" until the call ends even though the agent is no longer involved in the call at all. For example, a call from Alice gets into a queue and gets answered by Bob. Bob parks the call and gets removed from the bridge. After that, Charlie picks up the parked call and talks to Alice normally. During this call, the status of Bob is "In Use" which doesn't allow him to get new calls. Only when the call between Alice and Charlie ends does Bob become available again. Example: Extension 681 calls the queue and it’s picked up by extension 687. The call is then parked by 687 and picked up by extension 689. My configuration is the following is in configuration.txt. The output of the CLI commands during each stage of the testing scenario is in cli commands.txt The log of the whole scenario can be found in log.txt
Comments:	By: Asterisk Team (asteriskteam) 2017-10-08 17:58:19.122-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: Richard Mudgett (rmudgett) 2017-10-09 14:53:42.211-0500 I think this is a duplicate of these issues: ASTERISK-26399 ASTERISK-26400 ASTERISK-26715 ASTERISK-26975 By: Andres Miedzowicz (amiedzow) 2017-10-09 23:35:35.852-0500 It is indeed the same issue reported in ASTERISK-26399 but I'm running version 13.17.0 and it's still happening whereas the issue specifies that it should be fixed in that version By: Rusty Newton (rnewton) 2017-10-11 16:26:49.370-0500 Thanks for the report! In order to maximize efficiently, there are project guidelines for how to report issues. Please read through the Asterisk Issue Guidelines [1]. After reading the guidelines, please clean up this issue so that bug marshals can more easily help you. In particular: 1. Don't post extensive debug or logs inside the Description or Comment fields. 2. Use the Description field for a description of the issue, referencing *attached* debug with links or notes. 3. Use the Comment fields for discussion regarding the issue. 4. If you need to put a few lines of debug or logs into any field, surround the text with "noformat" tags to help us read it easily. 5. Attach files with a '.txt' extension where possible so that they can be analyzed futher by bug marshals. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines By: Andres Miedzowicz (amiedzow) 2017-10-12 03:54:04.683-0500 Thanks for the comments. I've cleaned up the description and uploaded the files with the configuration and logs By: Richard Mudgett (rmudgett) 2017-10-12 09:55:16.285-0500 Your files are not showing up.  Logs and configuration files are not contributions.  Patches are contributions.  Files marked as contributions will not show up unless you have signed a contribution license. By: Andres Miedzowicz (amiedzow) 2017-10-12 17:44:55.425-0500 Logs and configuration files By: Andres Miedzowicz (amiedzow) 2017-10-12 17:45:22.955-0500 Ok. Now they are attached to the issue By: Rusty Newton (rnewton) 2017-10-12 17:46:38.009-0500 Thanks for cleaning that up Andres! By: Kevin Harwell (kharwell) 2017-10-24 16:23:56.847-0500 I was able to duplicate on the latest 13 branch. By: Andres Miedzowicz (amiedzow) 2018-03-07 19:38:42.602-0600 Hi all, do you know if there's an ETA for this issue to be assigned for investigation and fix? By: Joshua C. Colp (jcolp) 2018-03-08 04:25:07.238-0600 The issue has been accepted and is in queue. There is no timeframe on when it will get looked into.