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

diff --git a/UPGRADE.txt b/UPGRADE.txt
index b6539d60e718a7c132b19e916f940efa1543cd55..953a6613344b0ca0c124a6d3539ff65c53a72aee 100644 (file)
--- 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