[asterisk-bugs] [Asterisk 0018230]: [regression] 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:                rmudgett
====================================================================== 
Project:                    Asterisk
Issue ID:                   18230
Category:                   Channels/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
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:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-10-29 06:27 CDT
Last Modified:              2010-11-22 13:36 CST
====================================================================== 
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.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0018211 Channel hangs up when redirected throug...
related to          0018185 Blind transfer failure, A calls B, B tr...
related to          0018322 Redirect two bridged channels to the sa...
====================================================================== 

---------------------------------------------------------------------- 
 (0129047) svnbot (reporter) - 2010-11-22 13:36
 https://issues.asterisk.org/view.php?id=18230#c129047 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 295866

_U  branches/1.8/
U   branches/1.8/apps/app_macro.c
U   branches/1.8/include/asterisk/channel.h
U   branches/1.8/include/asterisk/frame.h
U   branches/1.8/main/channel.c
U   branches/1.8/main/pbx.c

------------------------------------------------------------------------
r295866 | rmudgett | 2010-11-22 13:36:11 -0600 (Mon, 22 Nov 2010) | 60
lines

Merged revisions 295843 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/branches/1.6.2

................
  r295843 | rmudgett | 2010-11-22 13:28:23 -0600 (Mon, 22 Nov 2010) | 53
lines
  
  Merged revisions 295790 via svnmerge from 
  https://origsvn.digium.com/svn/asterisk/branches/1.4
  
  ........
    r295790 | rmudgett | 2010-11-22 12:46:26 -0600 (Mon, 22 Nov 2010) | 46
lines
    
    The channel redirect function (CLI or AMI) hangs up the call instead
of redirecting the call.
    
    To recreate the problem:
    1) Party A calls Party B
    2) Invoke CLI "channel redirect" command to redirect channel call leg
    associated with A.
    3) All associated channels are hung up.
    
    Note that if the CLI command were done on the channel call leg
associated
    with B it works.
    
    This regression was a result of the fix for issue
https://issues.asterisk.org/view.php?id=16946
    (https://reviewboard.asterisk.org/r/740/).
    
    The regression affects all features that use an async goto to execute
the
    dialplan because of an external event: Channel redirect, AMI redirect,
SIP
    REFER, and FAX detection.
    
    The struct ast_channel._softhangup code is a mess.  The variable is
used
    for several purposes that do not necessarily result in the call being
hung
    up.  I have added doxygen comments to describe how the various
_softhangup
    bits are used.  I have corrected all the places where the variable was
    tested in a non-bit oriented manner.
    
    The primary fix is the new AST_CONTROL_END_OF_Q frame.  It acts as a
weak
    hangup request so the soft hangup requests that do not normally result
in
    a hangup do not hangup.
    
    JIRA SWP-2470
    JIRA SWP-2489
    
    (closes issue https://issues.asterisk.org/view.php?id=18171)
    Reported by: SantaFox
    (closes issue https://issues.asterisk.org/view.php?id=18185)
    Reported by: kwemheuer
    (closes issue https://issues.asterisk.org/view.php?id=18211)
    Reported by: zahir_koradia
    (closes issue https://issues.asterisk.org/view.php?id=18230)
    Reported by: vmarrone
    (closes issue https://issues.asterisk.org/view.php?id=18299)
    Reported by: mbrevda
    (closes issue https://issues.asterisk.org/view.php?id=18322)
    Reported by: nerbos
    
    Review:	https://reviewboard.asterisk.org/r/1013/
  ........
................

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=295866 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-11-22 13:36 svnbot         Checkin                                      
2010-11-22 13:36 svnbot         Note Added: 0129047                          
======================================================================