[asterisk-bugs] [Asterisk 0011553]: [patch] ChannelRedirect causes the channel executing it to terminate if any form of error occurs.
noreply at bugs.digium.com
noreply at bugs.digium.com
Thu Dec 27 17:37:40 CST 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11553
======================================================================
Reported By: johan
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 11553
Category: Applications/app_channelredirect
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Asterisk Version: 1.4.15
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 12-14-2007 11:05 CST
Last Modified: 12-27-2007 17:37 CST
======================================================================
Summary: [patch] ChannelRedirect causes the channel executing
it to terminate if any form of error occurs.
Description:
When you use ChannelRedirect on a channel that does not exist the call will
be terminated, and the execution of the dial plan will end. Instead only
the error message should be returned, and the execution of the dial plan
can then continue as it should.
The enclosed patch change the behaviour of ChannelRedirect to set the
channel variable CR_STATUS to either SUCCESS, NOARGS, BADARGS, NOCHANNEL,
BADEXTENSION or FAIL, so that your dial plan does not have to crash and
burn in agony.
======================================================================
----------------------------------------------------------------------
Corydon76 - 12-27-07 17:37
----------------------------------------------------------------------
Okay:
1) the name of the status variable should be CHANNELREDIRECT_STATUS.
2) The help text should wrap at 80 columns.
3) This needs to be patched against trunk, not 1.4.
4) You need to document these changes in the CHANGES and UPGRADE.txt
files.
Issue History
Date Modified Username Field Change
======================================================================
12-27-07 17:37 Corydon76 Note Added: 0076076
======================================================================
More information about the asterisk-bugs
mailing list