diff options
| author | Matthew Jordan <mjordan@digium.com> | 2015-04-07 15:22:42 +0000 |
|---|---|---|
| committer | Matthew Jordan <mjordan@digium.com> | 2015-04-07 15:22:42 +0000 |
| commit | c2f50ba6f47e04c0457baa0bb5bf84b22a26d20b (patch) | |
| tree | bef776975d16755afde6f2809bd5fae43fd7075a /CHANGES | |
| parent | af4d8027730fff35dba65eb2d7ade73ade4a4a8e (diff) | |
ARI: Add the ability to intercept hold and raise an event
For some applications - such as SLA - a phone pressing hold should not behave
in the fashion that the Asterisk core would like it to. Instead, the hold
action has some application specific behaviour associated with it - such as
disconnecting the channel that initiated the hold; only playing MoH to channels
in the bridge if the channels are of a particular type, etc.
One way of accomplishing this is to use a framehook to intercept the
hold/unhold frames, raise an event, and eat the frame. Tasty. This patch
accomplishes that using a new dialplan function, HOLD_INTERCEPT.
In addition, some general cleanup of raising hold/unhold Stasis messages was
done, including removing some RAII_VAR usage.
Review: https://reviewboard.asterisk.org/r/4549/
ASTERISK-24922 #close
........
Merged revisions 434216 from http://svn.asterisk.org/svn/asterisk/branches/13
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@434217 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'CHANGES')
| -rw-r--r-- | CHANGES | 16 |
1 files changed, 16 insertions, 0 deletions
@@ -118,6 +118,22 @@ chan_pjsip more information. Defaults to 'no' as setting it to 'yes' can result in many unnecessary messages being sent to the caller. +res_ari_channels +------------------ + * Two new events, 'ChannelHold' and 'ChannelUnhold', have been added to the + events data model. These events are raised when a channel indicates a hold + or unhold, respectively. + +func_holdintercept +------------------ + * A new dialplan function, HOLD_INTERCEPT, has been added. This function, when + placed on a channel, intercepts hold/unhold indications signalled by the + channel and prevents them from moving on to other channels in a bridge with + the hold initiator. Instead, AMI or ARI events are raised indicating that + the channel wanted to place someone on hold. This allows external + applications to implement their own custom hold/unhold logic. + + ------------------------------------------------------------------------------ --- Functionality changes from Asterisk 13.2.0 to Asterisk 13.3.0 ------------ ------------------------------------------------------------------------------ |