[asterisk-bugs] [Asterisk 0014536]: After a caller is processed by app_queue the queue_log logs the hangup as TRANSFER

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14536 
====================================================================== 
Reported By:                aragon
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   14536
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Target Version:             1.4.27
Asterisk Version:           1.4.23 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!): 173594 
Request Review:              
====================================================================== 
Date Submitted:             2009-02-23 19:26 CST
Last Modified:              2009-07-10 15:17 CDT
====================================================================== 
Summary:                    After a caller is processed by app_queue the
queue_log logs the hangup as TRANSFER
Description: 
I'm using agent callback and not channel_agent

In this example ext 222 dials *850 to enter a test queue and ext 233
(agent 1) answers the call. Then 222 hangs up.
But my queue_log logs the hangup reason as TRANSFER instead of
COMPLETEAGENT or COMPLETECALLER

I think I am using revision 173594
====================================================================== 

---------------------------------------------------------------------- 
 (0107596) mnicholson (administrator) - 2009-07-10 15:17
 https://issues.asterisk.org/view.php?id=14536#c107596 
---------------------------------------------------------------------- 
I cannot reproduce this issue with svn branch 1.4 revision 205877.  I need
concise instructions on how to reproduce this.

I looked at the code around that context change check.  I suppose it is
possible for the context to change because of a masquerade caused by a
local channel.  I will need to look at it some more and reproduce it to
understand it enough to fix it though. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-10 15:17 mnicholson     Note Added: 0107596                          
======================================================================