From a09110c81099022c4f0abc718a86298bced6f108 Mon Sep 17 00:00:00 2001
From: BJ Weschke <bweschke@btwtech.com>
Date: Fri, 5 May 2006 20:12:59 +0000
Subject: [PATCH]  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
---
 UPGRADE.txt | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/UPGRADE.txt b/UPGRADE.txt
index b6539d60e7..953a661334 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
-- 
GitLab