Summary:	ASTERISK-12708: Make asterisk push an event to the manager in the case of a transfer.
Reporter:	David Woolley (davidw)	Labels:
Date Opened:	2008-09-10 08:14:49	Date Closed:	2008-12-09 09:28:45.000-0600
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Applications/app_queue
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Make Asterisk issue an AgentComplete event when the call is resolved as a transfer, albeit with a reason of transfer as opposed to caller/agent. ****** ADDITIONAL INFORMATION ****** We believe that ASTERISK-9159219 should have been treated as a bug, not a feature, and applied to the 1.4 branch.  This is because AgentComplete only really makes sense to any CTI supported use of queues if it is generated on all exit paths after AgentConnect. As such, it should have been applied to the 1.4 branch. It looks to me as though the proposed patch might apply directly in 1.4.21.  The current SVN head for 1.4 (142317), which looks like it would have the same issue, has another case in which a TRANSFER queue event is logged, which I haven't analyzed. In our case, generating the transfer wasn't a normal sort of operation, but was possible and resulted in the CTI side thinking it still had a call, which was then difficult to get rid of, as it didn't really exist.
Comments:	By: Leif Madsen (lmadsen) 2008-10-14 12:02:53 I'm assigning this issue to russell in the hopes he can determine if your request is justified and should have action taken upon it. Mind you russell is extremely busy (more so than usual) so this may take a bit longer than normal for action to be taken. Thanks! By: Russell Bryant (russell) 2008-12-09 09:28:45.000-0600 I have decided not to apply this to the 1.4 branch.  While I appreciate the argument you have made for it, since the 1.4 code base is very established at this point, I don't want to change the behavior and risk breaking existing applications that have worked around the issue.