[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-03-11 10:40 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
====================================================================== 

---------------------------------------------------------------------- 
 (0101539) aragon (reporter) - 2009-03-11 10:40
 http://bugs.digium.com/view.php?id=14536#c101539 
---------------------------------------------------------------------- 
Re-tested this morning with fresh install of Asterisk 1.4.24rc1
This behavior is unacceptable
I still get the incorrect data written to /var/log/asterisk/queue_log when
/etc/asterisk/queues.conf includes some context for an IVR menu
The purpose of the IVR context is to allow the caller to exit the queue
with a keypress
The test procedure is simple
Include an IVR context in queues.conf
Caller dials queue using any technology
Agent answers caller
Agent or caller does hangup
Call is not transfer call and caller does not dial any DTMF
Data in queue_log is useless and incorrect in this scenario

1236785420|1236785411.7|default-sales|NONE|ENTERQUEUE||6010
1236785421|1236785411.7|default-sales|Local/6002 at default-agent/n|CONNECT|1|1236785420.8
1236785447|1236785411.7|default-sales|Local/6002 at default-agent/n|TRANSFER|s|all-hangup|1|26

Since the call center is billing on completed calls the bad queue_log data
makes billing impossible. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-11 10:40 aragon         Note Added: 0101539                          
======================================================================