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

[misterti misterti]

Hello,
The track of call is lost when using queues. 
 Tested in Asterisk 1.4.13 
  
 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.

TIA, Jozza


 
       
---------------------------------
Never miss a thing.   Make Yahoo your homepage.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-bugs/attachments/20080112/1a52e088/attachment-0001.htm 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: AMI_scenario.txt
Url: http://lists.digium.com/pipermail/asterisk-bugs/attachments/20080112/1a52e088/attachment-0001.txt