summaryrefslogtreecommitdiff
path: root/CHANGES
diff options
context:
space:
mode:
authorMark Michelson <mmichelson@digium.com>2014-04-09 21:43:23 +0000
committerMark Michelson <mmichelson@digium.com>2014-04-09 21:43:23 +0000
commit755696dcd0b9144754a914129e80116da1ebdbd8 (patch)
treea2610547eab064d96f9612ae2cfd6584061b11e9 /CHANGES
parentc613ef6b308cbb18a4eea0549b797ecba6e1094b (diff)
Add a Command header to the AMI Mixmonitor action.
This fixes a parsing error that occurred during the processing of the AMI action. The error did not result in MixMonitor itself misbehaving, but it could result in the AMI response not giving correct information back. The new header allows for one to specify a post-process command to run when recording finishes. Previously, in order to do this, the post-process command would have to be placed at the end of the Options: header. Patches: mixmonitor_command_2.patch by jhardin (License #6512) ........ Merged revisions 412048 from http://svn.asterisk.org/svn/asterisk/branches/12 git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@412050 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'CHANGES')
-rw-r--r--CHANGES3
1 files changed, 3 insertions, 0 deletions
diff --git a/CHANGES b/CHANGES
index 382f0f749..f5f652448 100644
--- a/CHANGES
+++ b/CHANGES
@@ -128,6 +128,9 @@ AMI
used to set the UniqueId on creation. The other id is assigned to the
second channel when dialing LOCAL, or defaults to appending ;2 if only
the single Id is given.
+
+ * The Mixmonitor action now has a "Command" header that can be used to
+ indicate a post-process command to run once recording finishes.
RealTime
------------------