]> git.ipfire.org Git - thirdparty/asterisk.git/commit
res_mixmonitor: MixMonitorMute by MixMonitor ID
authorMike Bradeen <mbradeen@sangoma.com>
Mon, 13 Mar 2023 19:27:06 +0000 (13:27 -0600)
committerFriendly Automation <jenkins2@gerrit.asterisk.org>
Mon, 20 Mar 2023 14:29:48 +0000 (09:29 -0500)
commitfa635a872ea410d656d1f912a49bae66e95f1ae9
treec2f0ed5a2ef99c2aa9b0db714c3dfba440352855
parent8d2ffc8aa54315b937712bc725fd813a37e73158
res_mixmonitor: MixMonitorMute by MixMonitor ID

While it is possible to create multiple mixmonitor instances
on a channel, it was not previously possible to mute individual
instances.

This change includes the ability to specify the MixMonitorID
when calling the manager action: MixMonitorMute.  This will
allow an individual MixMonitor instance to be muted via id.
This id can be stored as a channel variable using the 'i'
MixMonitor option.

As part of this change, if no MixMonitorID is specified in
the manager action MixMonitorMute, Asterisk will set the mute
flag on all MixMonitor spy-type audiohooks on the channel.
This is done via the new audiohook function:
ast_audiohook_set_mute_all.

ASTERISK-30464

Change-Id: Ibba8c7e750577aa1595a24b23316ef445245be98
apps/app_mixmonitor.c
doc/CHANGES-staging/app_mixmonitor_mute_by_id.txt [new file with mode: 0644]
include/asterisk/audiohook.h
main/audiohook.c