[asterisk-bugs] [Asterisk 0011757]: AMI bug - call track lost - when using queues

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11757 
====================================================================== 
Reported By:                jozza
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   11757
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.13 
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             01-13-2008 05:43 CST
Last Modified:              02-06-2008 13:07 CST
====================================================================== 
Summary:                    AMI bug - call track lost - when using queues
Description: 
Hello,
The track of call is lost when using queues.

Sample: incoming call on capi line with uniqueId 1200051030.8283 joins
queue.
After it joins queue, there is no way to know what happened to the call
with this uniqueId until trunk hangs up. The track of this call is lost as
no message specifies the bridge connection with source UniqueId which is
capi and destination which is a queued call  local/105
Can anyone confirm this or maybe suggest a workaround?

Attached is a text file with this call scenario in AMI events.
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 02-06-08 13:07  
---------------------------------------------------------------------- 
I will provide a patch that improves the AgentCalled event to include the
"AgentChannel" and the "UniqueID" paramaters. The "AgentChannel" will
actually be the channel name (including the unique suffix) as opposed to
the interface called. The "UniqueID" will be the UniqueID of the calling
channel as it appears in other manager events. I will have it uploaded
shortly. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-06-08 13:07  putnopvut      Note Added: 0081805                          
======================================================================