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

[Asterisk Bug Tracker]

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:                     new
Asterisk Version:           1.8.0 
JIRA:                        
Regression:                 No 
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-02 09:09 CDT
====================================================================== 
Summary:                    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.
====================================================================== 

---------------------------------------------------------------------- 
 (0128549) lmadsen (administrator) - 2010-11-02 09:09
 https://issues.asterisk.org/view.php?id=18230#c128549 
---------------------------------------------------------------------- 
First thing I see different is here:

WORK:

[Oct 28 18:11:30] DEBUG[16810]: pbx.c:4297 __ast_pbx_run: Spawn extension
(test,s,6) exited non-zero on 'SIP/1003-00000001'
  == Spawn extension (test, s, 6) exited non-zero on 'SIP/1003-00000001' 

NOT WORKING:

[Oct 28 17:14:42] DEBUG[7349]: pbx.c:4724 __ast_pbx_run: Spawn extension
(test,s,4) exited non-zero on 'SIP/1003-00000001'
  == Spawn extension (test, s, 6) exited non-zero on 'SIP/1003-00000001' 


The NOT WORKING part shows test,s,4 for some reason. Not too sure why that
happens, or if it's just an incorrect DEBUG message? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-11-02 09:09 lmadsen        Note Added: 0128549                          
======================================================================