diff options
author | Russell Bryant <russell@russellbryant.com> | 2006-05-26 18:33:58 +0000 |
---|---|---|
committer | Russell Bryant <russell@russellbryant.com> | 2006-05-26 18:33:58 +0000 |
commit | fba5d28317077854de7a096d6a61457709f4c207 (patch) | |
tree | ac115190e221c8c6d4180891ea91520c64a60b24 /UPGRADE.txt | |
parent | 3e47e08cdc5d9a4b3d9bb64bc5a5acb2bac1c39d (diff) |
document the changes I made yesterday to the exit behavior of the
AGI applications
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@30580 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'UPGRADE.txt')
-rw-r--r-- | UPGRADE.txt | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/UPGRADE.txt b/UPGRADE.txt index b7240b6c9..86751ad8b 100644 --- a/UPGRADE.txt +++ b/UPGRADE.txt @@ -135,6 +135,24 @@ Applications: This addresses the deficiency of not being able to count the number of messages in folders other than INBOX and Old. +* The exit behavior of the AGI applications has changed. Previously, when + a connection to an AGI server failed, the application would cause the channel + to immediately stop dialplan execution and hangup. Now, the only time that + the AGI applications will cause the channel to stop dialplan execution is + when the channel itself requests hangup. The AGI applications now set an + AGISTATUS variable which will allow you to find out whether running the AGI + was successful or not. + + Previously, there was no way to handle the case where Asterisk was unable to + locally execute an AGI script for some reason. In this case, dialplan + execution will continue as it did before, but the AGISTATUS variable will be + set to "FAILURE". + + A locally executed AGI script can now exit with a non-zero exit code and this + failure will be detected by Asterisk. If an AGI script exits with a non-zero + exit code, the AGISTATUS variable will be set to "FAILURE" as opposed to + "SUCCESS". + Manager: * After executing the 'status' manager action, the "Status" manager events |