summaryrefslogtreecommitdiff
path: root/CHANGES
diff options
context:
space:
mode:
authorMatt Jordan <mjordan@digium.com>2015-10-20 12:06:52 -0500
committerMatt Jordan <mjordan@digium.com>2015-10-20 22:24:00 -0500
commit7be6194d6f731bf7dec9fcad596132c32d66ee6c (patch)
tree6fdee6431500404fd40e4a85a2d50a8ef8101421 /CHANGES
parentb19860c03a1656fbf6409daf99b5fc98101e7134 (diff)
funcs/func_holdintercept: Actually add the HOLD_INTERCEPT function
When ab803ec342 was committed, it accidentally forgot to actually *add* the HOLD_INTERCEPT function. This highlights two interesting points: * Gerrit forces you to put the patch as it is going to into the repo up for review, which Review Board did not. Yay Gerrit. * No one apparently bothered to use this feature, or else they don't know about it. I'm going to go with the latter explanation. ASTERISK-24922 Change-Id: Ida38278f259dd07c334a36f9b7d5475b5db72396
Diffstat (limited to 'CHANGES')
-rw-r--r--CHANGES13
1 files changed, 13 insertions, 0 deletions
diff --git a/CHANGES b/CHANGES
index 88743cc7b..c8e9b847a 100644
--- a/CHANGES
+++ b/CHANGES
@@ -186,6 +186,19 @@ cdr_adaptive_odbc
------------------------------------------------------------------------------
+--- Functionality changes from Asterisk 13.6.0 to Asterisk 13.7.0 ------------
+------------------------------------------------------------------------------
+
+Dialplan Functions
+------------------
+ * The HOLD_INTERCEPT dialplan function now actually exists in the source tree.
+ While support for the events was added in Asterisk 13.4.0, the function
+ accidentally never made it in. That function is now present, and will cause
+ the 'hold' raised by a channel to be intercepted and converted into an
+ event instead.
+
+
+------------------------------------------------------------------------------
--- Functionality changes from Asterisk 13.5.0 to Asterisk 13.6.0 ------------
------------------------------------------------------------------------------