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

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
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:                     resolved
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:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             01-13-2008 05:43 CST
Last Modified:              01-14-2008 11:59 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 - 01-14-08 11:59  
---------------------------------------------------------------------- 
What you want is already provided via the eventwhencalled option in
queues.conf. Setting this option to yes will cause app_queue to generate
manager events whenever a queue member is called. One of these is the
"AgentConnect" event which has the information you want.

I am going to close this since changing this configuration setting is all
that is necessary to fix the problem. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-14-08 11:59  putnopvut      Status                   assigned => resolved
01-14-08 11:59  putnopvut      Resolution               open => no change
required
01-14-08 11:59  putnopvut      Note Added: 0076912                          
======================================================================