Summary:	ASTERISK-28744: No transfer events logged in queue_log
Reporter:	Igor Goncharovsky (igorg)	Labels:
Date Opened:	2020-02-17 06:03:53.000-0600	Date Closed:	2020-02-19 08:06:24.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Applications/app_queue
Versions:	16.8.0	Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) full-ASTERISK-28744 ( 1) queue_log-ASTERISK-28744
Description:	We found that there are no ATTENDEDTRANSFER and BLINDTRANSFER events logged in queue_log in current asterisk versions (tested on 13 and 16 version of asterisk). Test flow: 1. Call to queue with single agent 2. Accept call 3. Enter blind of attended transfer sequence from features.conf 4. After call disconnected from queue member - check queue_log
Comments:	By: Asterisk Team (asteriskteam) 2020-02-17 06:03:54.961-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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. By: Igor Goncharovsky (igorg) 2020-02-17 06:05:53.999-0600 Asterisk log and queue_log attached By: George Joseph (gjoseph) 2020-02-17 11:21:04.383-0600 Were you getting the events in earlier Asterisk releases?  If so, what were the latest releases that worked? By: Igor Goncharovsky (igorg) 2020-02-18 00:03:17.061-0600 I could not find out now exact version of asterisk this worked previously for us. I believe it was in asterisk 12. There is two function in app_queue, that should handle transfer event in app_queue: handle_blind_transfer and handle_attended_transfer. By: George Joseph (gjoseph) 2020-02-18 08:29:04.174-0600 "asterisk 12"??  Oh my.  Are you just now upgrading or have you been progressing through versions and just now reporting the issue? By: Igor Goncharovsky (igorg) 2020-02-18 08:39:15.596-0600 No, we have not used this events in any systems and just have required to have it now. Also as side effect we receive no AgentComplete event in AMI right after transfer completed. By: George Joseph (gjoseph) 2020-02-18 08:48:07.209-0600 Are you using Local channels?  If so, see this issue... ASTERISK-28038 By: Igor Goncharovsky (igorg) 2020-02-18 21:31:50.649-0600 Thanks for this comment, I have tested with PJSIP and Local without /n option - both working fine. Not a bug, but note about this behaviour should be somewhere in code or wiki. By: Igor Goncharovsky (igorg) 2020-02-18 22:01:06.218-0600 Additional I want to say that although in terms of current architecture this behavior is correct, its unexpected by user (including freepbx users). By: George Joseph (gjoseph) 2020-02-19 08:06:10.403-0600 OK.  I'm going to close this issue and take an action item to document the behavior.