diff options
author | bweschke <bweschke@f38db490-d61c-443f-a65b-d21fe96a405b> | 2006-05-05 20:12:59 +0000 |
---|---|---|
committer | bweschke <bweschke@f38db490-d61c-443f-a65b-d21fe96a405b> | 2006-05-05 20:12:59 +0000 |
commit | 811ed760ef2d5ebfad3df8f6adbd60aeb1ef5a3b (patch) | |
tree | 19559a28445374afc94c382fc63ba5a60ed5929c /UPGRADE.txt | |
parent | 2d71e6a743277c6857288ce09f03f93601959e83 (diff) |
Adding documentation about API change approved in order to fix bug(s).
git-svn-id: http://svn.digium.com/svn/asterisk/trunk@25012 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'UPGRADE.txt')
-rw-r--r-- | UPGRADE.txt | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/UPGRADE.txt b/UPGRADE.txt index b6539d60e..953a66133 100644 --- a/UPGRADE.txt +++ b/UPGRADE.txt @@ -93,6 +93,16 @@ Applications: option, it will default to "no" to keep backward compatability with the old behavior. +* ast_play_and_record would attempt to cancel the recording if a DTMF + '0' was received. This behavior was not documented in most of the + applications that used ast_play_and_record and the return codes from + ast_play_and_record weren't checked for properly. + ast_play_and_record has been changed so that '0' no longer cancels a + recording. If you want to allow DTMF digits to cancel an + in-progress recording use ast_play_and_record_full which allows you + to specify which DTMF digits can be used to accept a recording and + which digits can be used to cancel a recording. + Manager: * After executing the 'status' manager action, the "Status" manager events |