Summary:	ASTERISK-25530: Asterisk 13.6 not presenting ami hangup event for queue calls
Reporter:	Ryan Rittgarn (rrittgarn)	Labels:
Date Opened:	2015-11-06 10:33:11.000-0600	Date Closed:	2020-01-14 11:14:00.000-0600
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:
Versions:	13.6.0	Frequency of Occurrence	Constant
Related Issues:
Environment:	Debian Wheezy VM 2GB Ram 4 Cores	Attachments:
Description:	Comparing 13.5 to 13.6. In 13.5 incoming call comes into the queue, and is then parked. AMI Event properly fires for the queue member's channel being hung up. In 13.6 this event does not fire.
Comments:	By: Asterisk Team (asteriskteam) 2015-11-06 10:33:13.549-0600 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: Rusty Newton (rnewton) 2015-11-07 16:17:25.264-0600 I was unable to reproduce the issue. 1. Inbound caller enters queue 2. Queue member answers 3. Queue member parks caller with features.conf DTMF code 4. Queue member hangs up Watching AMI events I see the BridgeLeave and Hangup for the queue member channel. These events occur in both 13.5 and 13.6 in my tests. You'll need to provide AMI logs accompanied by full debug logs for the scenario in 13.5 and 13.6 as well as extensions.conf, queues.conf and manager.conf configuration. If the issue is occurring there is probably a difference in our configuration or a step you forgot to mention. Thanks! By: Rusty Newton (rnewton) 2015-11-07 16:17:38.469-0600 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 By: Asterisk Team (asteriskteam) 2015-11-22 12:00:19.271-0600 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines