No subject

the AGI script right along/after a command response. This does not happen
and the channel is never hung -unless the script returns-.

I am using adhearsion and a very simple dialplan.

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0017954 [patch] Peer does not hang up when call...
====================================================================== 

---------------------------------------------------------------------- 
 (0133728) svnbot (reporter) - 2011-04-13 11:31
 https://issues.asterisk.org/view.php?id=18492#c133728 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 313588

_U  branches/1.8/
U   branches/1.8/main/channel.c
U   branches/1.8/res/res_agi.c

------------------------------------------------------------------------
r313588 | rmudgett | 2011-04-13 11:31:51 -0500 (Wed, 13 Apr 2011) | 55
lines

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

................
  r313579 | rmudgett | 2011-04-13 11:29:49 -0500 (Wed, 13 Apr 2011) | 48
lines
  
  Merged revisions 313545 via svnmerge from 
  https://origsvn.digium.com/svn/asterisk/branches/1.4
  
  ........
    r313545 | rmudgett | 2011-04-13 11:21:24 -0500 (Wed, 13 Apr 2011) | 41
lines
    
    Asterisk does not hangup a channel after endpoint hangs up.
    
    If the call that the dialplan started an AGI script for is hungup
while
    the AGI script is in the middle of a command then the AGI script is
not
    notified of the hangup.  There are many AGI Exec commands that this
can
    happen with.  The reported applications have been: Background, Wait,
Read,
    and Dial.  Also the AGI Get Data command.
    
    * Don't wait on the Asterisk channel after it has hung up.  The
channel is
    likely to never need servicing again.
    
    * Restored the AGI script's ability to return the AGI_RESULT_HANGUP
value
    in run_agi().  It previously only could return AGI_RESULT_SUCCESS or
    AGI_RESULT_FAILURE after the DeadAGI and AGI applications were merged.
    
    (closes issue https://issues.asterisk.org/view.php?id=17954)
    Reported by: mn3250
    Patches:
          issue17954_v1.8.patch uploaded by rmudgett (license 664)
          issue17954_v1.6.2.patch uploaded by rmudgett (license 664)
          issue17954_v1.4.patch uploaded by rmudgett (license 664)
    Tested by: rmudgett
    JIRA SWP-2171
    
    (closes issue https://issues.asterisk.org/view.php?id=18492)
    Reported by: devmod
    Tested by: rmudgett
    JIRA SWP-2761
    
    (closes issue https://issues.asterisk.org/view.php?id=18935)
    Reported by: nvitaly
    Tested by: astmiv, rmudgett
    JIRA SWP-3216
    
    (closes issue https://issues.asterisk.org/view.php?id=17393)
    Reported by: siby
    Tested by: rmudgett
    JIRA SWP-2727
    
    Review: https://reviewboard.asterisk.org/r/1165/
  ........
................

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

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

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-04-13 11:31 svnbot         Checkin                                      
2011-04-13 11:31 svnbot         Note Added: 0133728                          
======================================================================