[asterisk-bugs] [Asterisk 0017954]: [patch] Peer does not hang up when caller hangup while app_dial is executing - Deadagi
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Apr 13 11:37:08 CDT 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17954
======================================================================
Reported By: mn3250
Assigned To: rmudgett
======================================================================
Project: Asterisk
Issue ID: 17954
Category: Applications/app_dial
Reproducibility: always
Severity: minor
Priority: normal
Status: closed
Target Version: 1.8.5
Asterisk Version: SVN
JIRA: SWP-2171
Regression: No
Reviewboard Link: https://reviewboard.asterisk.org/r/1165/
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-09-05 13:36 CDT
Last Modified: 2011-04-13 11:37 CDT
======================================================================
Summary: [patch] Peer does not hang up when caller hangup
while app_dial is executing - Deadagi
Description:
I am trying to execute a dead agi application:
exten => 1111,1,DeadAgi,calling.pl
exten => 1111,n,Hangup()
in calling.pl I have:
$result=$AGI->exec("Background", "connecting");
$dialstr = $type."/$callednumber@".$providerip."|90|rHL(" . ($calltime *
60 * 1000) . ")";
$result=$AGI->exec("DIAL $dialstr");
everything works fine if the caller does not hangup and the progress tone
is played to the caller but if the caller disconnect the call while
connecting.gsm is played, the peer does not disconnect even after the
originating channel is hung up.
Should * not disconnect the briged channel when originating channel
dissconnects?
Asterisk reports the caller disconnect and DIALSTATUS is CANCEL but the
bridged call stays in progress and connects unless a restart is issued. If
this is normal (I do not think so), is there a workaround to disconnect the
bridged leg after caller hangs up in my agi script?
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0018492 Asterisk does not hangup a channel afte...
related to 0018935 [patch] HANGUP is not sent to AGI in time
======================================================================
----------------------------------------------------------------------
(0133732) svnbot (reporter) - 2011-04-13 11:37
https://issues.asterisk.org/view.php?id=17954#c133732
----------------------------------------------------------------------
Repository: asterisk
Revision: 313606
_U trunk/
U trunk/main/channel.c
U trunk/res/res_agi.c
------------------------------------------------------------------------
r313606 | rmudgett | 2011-04-13 11:37:06 -0500 (Wed, 13 Apr 2011) | 62
lines
Merged revisions 313588 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.8
................
r313588 | rmudgett | 2011-04-13 11:31:50 -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=313606
Issue History
Date Modified Username Field Change
======================================================================
2011-04-13 11:37 svnbot Checkin
2011-04-13 11:37 svnbot Note Added: 0133732
======================================================================
More information about the asterisk-bugs
mailing list