[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. 
====================================================================== 
http://bugs.digium.com/view.php?id=14536 
====================================================================== 
Reported By:                aragon
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14536
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
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-02-26 09:59 CST
====================================================================== 
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
====================================================================== 

---------------------------------------------------------------------- 
 (0100795) aragon (reporter) - 2009-02-26 09:59
 http://bugs.digium.com/view.php?id=14536#c100795 
---------------------------------------------------------------------- 
The problem isn't service affecting so I opened it as minor but its bunging
up all my Call Center statistics.  I hope a developer can take a look at
this issue soon.  I cannot upgrade Asterisk on any other sites until this
issue is resolved... and I wouldn't want to see this problem turn up in
1.4.24 when it is released to the masses.

I'm getting a little desperate 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-26 09:59 aragon         Note Added: 0100795                          
======================================================================