[asterisk-bugs] [Asterisk 0016031]: AMI redirect of caller channel while being answered by queue agent causes caller disconnect

Fri Jan 29 08:54:48 CST 2010

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16031 
====================================================================== 
Reported By:                escape2mtns
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16031
Category:                   Core/ManagerInterface
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.4.26.1 
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-10-06 21:08 CDT
Last Modified:              2010-01-29 08:54 CST
====================================================================== 
Summary:                    AMI redirect of caller channel while being answered
by queue agent causes caller disconnect
Description: 
We're using the AMI to allow queue agents to sometimes cherry-pick
important calls from queue.  If a redirect command is issued on a channel
just as it is being answered by an Agent, the caller is disconnected.
====================================================================== 

---------------------------------------------------------------------- 
 (0117367) escape2mtns (reporter) - 2010-01-29 08:54
 https://issues.asterisk.org/view.php?id=16031#c117367 
---------------------------------------------------------------------- 
This ticket (https://issues.asterisk.org/view.php?id=16566) seems similar
and reports that the issue has been fixed in trunk.  Would that mean that
our issue might be fixed as well?  Could it be a similar issue in another
section of code? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-29 08:54 escape2mtns    Note Added: 0117367                          
======================================================================