diff options
| author | BJ Weschke <bweschke@btwtech.com> | 2006-05-05 20:12:59 +0000 |
|---|---|---|
| committer | BJ Weschke <bweschke@btwtech.com> | 2006-05-05 20:12:59 +0000 |
| commit | a09110c81099022c4f0abc718a86298bced6f108 (patch) | |
| tree | 19559a28445374afc94c382fc63ba5a60ed5929c /UPGRADE.txt | |
| parent | c1649932ec191b125577f955ede2cf03f8e35589 (diff) | |
Adding documentation about API change approved in order to fix bug(s).
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@25012 65c4cc65-6c06-0410-ace0-fbb531ad65f3
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 |