[asterisk-bugs] [Asterisk 0014527]: Queue members associated with ZOMBIE channels (breaks wrapuptime and queue_log).

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14527 
====================================================================== 
Reported By:                kebl0155
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14527
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.0.3 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-02-23 06:26 CST
Last Modified:              2009-10-28 09:10 CDT
====================================================================== 
Summary:                    Queue members associated with ZOMBIE channels
(breaks wrapuptime and queue_log).
Description: 
In some circumstances, queue members become associated with a ZOMBIE
channel during the answer process.

When the ZOMBIE channel is hung up under normal clearing as part of the
answer process, an AgentComplete event is generated, and the wrapuptime
counter is set, even though the agent is still on a call.  The queue_log
entry is also written at this time with just 1 second of talk time.

No further AgentComplete event is generated when the call comes to an end.
 The wrapuptime is then counted from the start of the call, not the end of
the call.
====================================================================== 

---------------------------------------------------------------------- 
 (0112849) atis (reporter) - 2009-10-28 09:10
 https://issues.asterisk.org/view.php?id=14527#c112849 
---------------------------------------------------------------------- 
You could always follow UniqueID as workaround. That works perfectly for me
with similar scenarios. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-28 09:10 atis           Note Added: 0112849                          
======================================================================