VoIP.infoThe independent guide to business communications.
VoIP.info Guide

Asterisk AMI MuteAudio: channel, direction and media proof

Mute one channel stream without confusing PBX-relative direction, action acknowledgement, bridge peers, recordings, conferences or endpoint mute.

Reviewed 2026-10-25Current branch-23-generated, Asterisk 22 and Certified Asterisk 22.8 MuteAudio action references, the current MUTEAUDIO function, MixMonitorMute, ConfbridgeMute, CoreShowChannel, Manager API and AMI v2 references were reviewed October 25, 2026; installed release, loaded modules and actions, manager permission, live channel identity, bridge technology, media path, recording, conference policy and endpoint state remain deployment-specific; no PBX, manager session, action, dialplan, channel, bridge, conference, recording, packet, media frame, endpoint, speaker, microphone or live call was inspected or testedAdvancedDocumentation based · not lab tested

Bind the control to one live channel

Record the Asterisk node, installed release, manager identity, unique ActionID, exact Channel, Uniqueid, Linkedid, bridge membership, channel creation time, action time, requested direction and requested state. Resolve the current channel immediately before the action.

MuteAudio operates on the named channel. It does not name a caller, endpoint, whole linked call or every member of a bridge, so a reused display value or stale peer map is not a safe target.

Read in and out from the PBX boundary

The current, Asterisk 22 and Certified 22.8 action pages define in as audio travelling to the PBX, out as audio travelling from the PBX and all as both streams. Translate the desired human outcome through the selected channel leg before sending the action.

On one bridged leg, muting inbound audio can stop that party audio from entering Asterisk; muting outbound audio can stop media sent from Asterisk toward that party. Those labels are not microphone and speaker names, and the opposite bridge leg has its own perspective.

Treat the response as one control boundary

Use State on to turn stream muting on and State off to turn it off, preserving the raw response and matching ActionID. A success response establishes that the action was accepted for processing, not that a listener heard silence or speech.

The generated action page does not document a dedicated MuteAudio state event or a query field for current mute state. Prove the later media effect separately and retain the application policy that owns restoration.

Keep four mute mechanisms separate

The dialplan MUTEAUDIO function controls inbound, outbound or both channel streams from dialplan execution. MixMonitorMute mutes recording directions using read, write or both and numeric state, while ConfbridgeMute targets a conference participant or documented bulk scope.

Endpoint microphone mute, softphone mute, operating-system capture controls and physical headset mute are further layers. Similar words do not make these controls interchangeable; each needs its own target, direction vocabulary, owner and observable result.

Rebuild topology after transfers and optimization

CoreShowChannel can provide the channel name, Uniqueid, Linkedid, bridge ID, application and duration for a timestamped inventory response. Rebuild the intended path after transfer, Local-channel optimization, bridge replacement or masquerade before changing mute state.

Bridge membership establishes only a potential media relationship. It does not prove decoded audio, and changing one channel does not guarantee that another linked or conference channel inherited the same stream restriction.

Validate privacy and recovery on a disposable call

In an approved nonproduction window, use one disposable call and distinct authorized phrases for each direction. Capture the action response, channel and bridge identities, inbound and outbound packet or frame evidence, far-end and local listening results, then restore with the exact inverse action and prove speech recovery.

Test transfer or bridge change only when required by policy. Use a dedicated least-privilege manager identity and a timed restoration guard owned by the application. Documentation does not establish privacy, compatibility, audio quality or fail-safe recovery, and no live system was tested for this guide.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.

Continue your research

Guide · Current Asterisk interface documentation reviewed September 30, 2026; implementation must be checked against the installed branch and integration library

Asterisk AMI, ARI and AGI: choose the control boundary

Separate management events, synchronous dialplan work and application-owned call control before exposing an integration.

Read guide →
Guide · Asterisk branch-23-generated and branch-22-generated ListCommands references plus official AMI syntax, v2 specification, manager-command, change/versioning, permission, module-loader and network-security documentation reviewed October 16, 2026; installed branch and maintenance release, build, package and module set, manager user, read and write authorizations, session mask, action registration, request framing, parameters, target objects, response, related events and service outcome remain deployment specific; no PBX, module, package, manager user, manager session, request, response, event, configuration file, channel, packet, media stream or live call was inspected or tested

Asterisk AMI command inventory and permission evidence

Use ListCommands and the administrator CLI to distinguish the actions visible to one manager user from the actions registered by the running Asterisk instance.

Read guide →
Guide · Current Asterisk Latest API CHANNEL_EXISTS, CHANNELS and CHANNEL references, CLI channel-operation and Local-channel optimization documentation, AMI CoreShowChannels surfaces and the upstream func_channel implementation were reviewed October 19, 2026. The generated API pages reported branch 23; installed branch, loaded modules, channel drivers, names, unique IDs, linked IDs, Local optimization, permissions, timing and call outcomes remain deployment specific. No PBX, module, dialplan, channel, bridge, manager session, packet, media stream or live call was inspected or tested

Asterisk channel inventory, identity and lifetime

Treat a channel list as a changing observation, distinguish name from unique identity, and revalidate the exact leg before an authorized operation.

Read guide →
Guide · Current Asterisk branch-23-generated CoreShowChannelMap, CoreShowChannelMapComplete, CoreShowChannels, CoreShowChannel, CoreShowChannelsComplete, Status, StatusComplete, Newchannel and Rename references plus the branch 22 map action and completion event reviewed October 16, 2026; installed branch, loaded actions and events, manager permissions, session ordering, channel names, stable identifiers, bridge membership, variables, signaling and media remain deployment specific; no PBX, AMI session, manager user, permission, channel, bridge, variable, packet, media stream or live call was inspected or tested

Asterisk AMI channel snapshots and connected maps

Choose CoreShowChannels, CoreShowChannelMap or Status deliberately, preserve list boundaries, and correlate mutable channel, linked and bridge identities without treating a snapshot as a final call result.

Read guide →
Guide · Current Asterisk branch-23-generated AMI Bridge, BridgeList, BridgeInfo, BridgeKick and bridge-event references plus branch 22 Bridge and BridgeKick references reviewed October 15, 2026; installed branch, loaded manager actions, AMI user permissions, live channel and bridge identities, event delivery, signaling, bridge technology and media remain deployment specific; no AMI session, user, permission, host, manager action, bridge, channel, packet, media stream or live call was inspected or tested

Asterisk AMI bridge control: actions, membership and event evidence

Bridge two live channels, inventory bridge identity and remove a member without confusing action acknowledgement, bridge membership, signaling and media.

Read guide →
Guide · Asterisk 22 LTS application references and current audiohook architecture reviewed September 30, 2026; no PBX, call, channel, recording, file, processor, storage or playback path was tested

Asterisk MixMonitor: channel scope, files and recording evidence

Plan recording policy, bind MixMonitor to the intended channel and verify each file lifecycle boundary.

Read guide →
Guide · Current branch-23-generated and branch-22 AMI MixMonitor, MixMonitorMute and StopMixMonitor action references, current MixMonitorStart, MixMonitorMute and MixMonitorStop event references, and current dialplan MixMonitor and StopMixMonitor references reviewed October 17, 2026; AMI request, action response, channel-bound audiohook, start or mute or stop event, filename, open file handle, durable file, decoded audio, retention and caller outcome remain separate evidence boundaries; installed branch, loaded app_mixmonitor module, manager permissions, event filters, channel lifetime, storage, legal basis and generated FreePBX dialplan remain deployment specific; no PBX, module, manager account, credential, session, channel, audiohook, event stream, file, packet, media stream, recording or live call was inspected or tested

Asterisk AMI MixMonitor controls and recording-event evidence

Separate AMI recording requests, channel-scoped audiohooks, start, mute and stop events, file-handle release, stored files, decoded audio and retention outcomes.

Read guide →
Guide · Current Asterisk branch-23-generated ConfbridgeLock, ConfbridgeUnlock, ConfbridgeMute, ConfbridgeUnmute, ConfbridgeKick, ConfbridgeStartRecord and ConfbridgeStopRecord action references, branch-22 lock and recording references, current recording events, and official ConfBridge AMI, CLI and manager-command documentation reviewed October 17, 2026; an accepted manager action, room lock state, participant mute state, participant membership, recording event, generated path, durable file, captured audio and caller outcome remain separate evidence boundaries; installed branch, loaded app_confbridge module, active conference identity, channel names, manager permissions, event policy, recording directory and filesystem behavior remain deployment specific; no PBX, module, manager account, credential, session, conference, participant, channel, lock, mute, kick, recorder, file, packet, audio or live call was inspected or tested

Asterisk AMI ConfBridge moderation and recording controls

Operate ConfBridge lock, mute, kick and recording actions with exact targets, bounded authority and separate response, event, state and outcome evidence.

Read guide →
Guide · Asterisk 22 ConfBridge application plus current first-party configuration and CLI documentation reviewed October 10, 2026; generated FreePBX profiles and loaded runtime state remain installation-specific, and no PBX, profile, conference, participant, media stream, recording or call was inspected or tested

Asterisk 22 ConfBridge profiles, lifecycle and acceptance

Separate bridge ownership, participant policy, DTMF menus, audio processing, recording and room lifecycle.

Read guide →
Troubleshooting · Current branch-23-generated, Asterisk 22 and Certified Asterisk 22.8 MuteAudio action references, the current MUTEAUDIO function, MixMonitorMute, ConfbridgeMute, CoreShowChannel, Manager API and AMI v2 references were reviewed October 25, 2026; installed release, loaded modules and actions, manager permission, live channel identity, bridge technology, media path, recording, conference policy and endpoint state remain deployment-specific; no PBX, manager session, action, dialplan, channel, bridge, conference, recording, packet, media frame, endpoint, speaker, microphone or live call was inspected or tested

Asterisk AMI MuteAudio uses the wrong direction, wrong leg or stays audible

Find the first divergence across action availability, live channel identity, PBX-relative direction, response, topology and the actual media path.

Read guide →
Troubleshooting · Asterisk 22 LTS · FreePBX 17 / Debian 12 checks

One-way VoIP audio

Trace the missing direction from advertised media address to receiving endpoint.

Read guide →