[asterisk-bugs] [Asterisk 0010661]: [patch] fix the redirect thru the ami

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10661 
====================================================================== 
Reported By:                junky
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10661
Category:                   Core/PBX
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     confirmed
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 81858 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             09-06-2007 17:28 CDT
Last Modified:              12-16-2007 05:32 CST
====================================================================== 
Summary:                    [patch] fix the redirect thru the ami
Description: 
When you have a channel in a meetme room (and inside an AGI), if you
redirect throught the AMI, you get

Action: Redirect
Channel: SIP/10-0822b188
Context: meetme
Exten: 19
Priority: 2

Response: Success
Message: Redirect successful

but the channel is hanguped instead of being redirected correctly.

this is the command used in the AMI:
Action: Redirect
Channel: SIP/10-08231dd8
Context: meetme
Exten: 19
Priority: 1

with this patch, for an unknown reason, the chan->pbx has to be NULL so it
could branched correctly in pbx.c::ast_explicit_goto().

====================================================================== 

---------------------------------------------------------------------- 
 junky - 12-16-07 05:32  
---------------------------------------------------------------------- 
since trunk Rev 81858 is really stable for me (with this patch), im running
that specific version on a customer, so I dont know the exact status.
Since file changed the status to confirmed, maybe he knows more about it.

Also, i never mentionned 1.4 for this bug report. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-16-07 05:32  junky          Note Added: 0075512                          
======================================================================