[asterisk-bugs] [Asterisk 0018230]: [regression] Redirect function (over console or AMI) is not work anymore

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Nov 3 03:23:48 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18230 
====================================================================== 
Reported By:                vmarrone
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18230
Category:                   Channels/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.8.0 
JIRA:                       SWP-2489 
Regression:                 Yes 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-10-29 06:27 CDT
Last Modified:              2010-11-03 03:23 CDT
====================================================================== 
Summary:                    [regression] Redirect function (over console or AMI)
is not work anymore
Description: 
With Asterisk 1.8.0, after have Originated a call, and request by AMI or by
console the command redirect to another priority of the same context or
another context, extension and priority, the channel is "hangupped" by
Asterisk without errors.
In previous versions, when was requested the redirect, correctly the
channel was jumped to the extension or priority in the dialplan doing the
correct application.
====================================================================== 

---------------------------------------------------------------------- 
 (0128581) vmarrone (reporter) - 2010-11-03 03:23
 https://issues.asterisk.org/view.php?id=18230#c128581 
---------------------------------------------------------------------- 
Is just an incorrect debug message.. I have made many test with different
priority, and I have mix the results for explain reasons, sorry for the
mistake, but is sure that don't work! I have worked much with Asterisk and
the AMI... Anyway, if you try the example You can verify this.
Thanks for the answer! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-11-03 03:23 vmarrone       Note Added: 0128581                          
======================================================================




More information about the asterisk-bugs mailing list