]> 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)
committerAsterisk Development Team <asteriskteam@digium.com>
Mon, 8 May 2023 18:13:35 +0000 (18:13 +0000)
commite00eaa74e3baf067545e18aabc9b15bc210ae7b2
tree8df025aeb63315a485eed6a87e584ebf6e904575
parent3a4fd2fa4213e652cdcc8c8a35a447ed667635bf
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
(cherry picked from commit fa635a872ea410d656d1f912a49bae66e95f1ae9)
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