[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-04-2008 11:56 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.
====================================================================== 

---------------------------------------------------------------------- 
 jozza - 02-04-08 11:56  
---------------------------------------------------------------------- 
Thanks for your reply.

I need to know what the incoming line is when the phone rings, because a
user program needs this info a that point, so agentconnect event is too
late. I wouldnt have gone so deeply and track the calls otherwise.
Fortunately, i'm an expert on csta protocol and it was not that hard to
unravel the call flow.
It might even be possible to write csta module that would extend ami.

I see in the logs that before AgentCalled event, there are always two
messages with a Local channel created. Then Agentcalled message has that
channel specified without unique id in its agentcalled parameter. If that
is fixed, then there should be no problem tracking calls in queue anymore.
Will you provide a patch?

J. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-04-08 11:56  jozza          Note Added: 0081674                          
======================================================================