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

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.

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

Freeze one request and one audible symptom

Record node, release, manager identity, ActionID, exact Channel, Uniqueid, Linkedid, bridge peers, application, requested direction, state, raw response and synchronized timestamps. State who could still hear whom and at which observation point.

Classify the symptom as unknown or denied action, wrong or vanished channel, reversed direction, only one side muted, both sides muted, still audible, recording-only change, conference-only change or unmute without restored speech. Do not combine several calls into one timeline.

Confirm action inventory, module and authority

Check the running action inventory, installed branch, loaded res_mutestream behavior and manager write permission. Resolve the channel again immediately before the action and require the same Uniqueid; a completed, transferred or optimized channel invalidates a stale name.

An unknown action, denied request or absent channel is not a media-direction defect. Keep least privilege and do not substitute broad AMI Command authority for a missing action permission.

Translate the desired silence through the selected leg

For the exact channel, map the desired outcome to audio travelling in to Asterisk, out from Asterisk or all. Then map every bridge peer separately. Do not use caller and callee labels as direction fields after a transfer.

If the target can still be heard, determine whether media is entering through a different channel, conference source, recording playback, whisper or application path. If the target hears silence, determine whether the selected outbound stream was intentionally or accidentally muted.

Separate MuteAudio from recording and conference controls

Inspect the exact action name and vocabulary. MuteAudio uses in, out or all with on or off; MixMonitorMute changes recording read, write or both with 1 or 0; ConfbridgeMute operates in a named conference and can accept a full channel, prefix or documented bulk value.

A silent recording with an audible call points toward recording control. A muted conference participant with unchanged direct-call behavior points toward ConfBridge policy. Do not alternate these actions until one appears to work.

Follow frames, packets and listening results independently

Capture authorized counters or traces on both sides of the Asterisk channel boundary. Determine whether RTP still arrives, whether Asterisk admits audio from the selected channel, whether it sends audio toward the target and whether each authorized listener hears the expected result.

Packet presence is not decoded speech, and silence is not proof of MuteAudio. Endpoint microphone mute, capture failure, negotiated direction, codec failure, NAT, bridge policy, playback choice and output volume can produce similar symptoms.

Correct one owner and prove deterministic restoration

Correct only the first demonstrated divergence: availability, permission, stale identity, direction translation, wrong mute mechanism, topology, media path or restoration ownership. Retest one disposable call, then send the exact approved off action and prove both the intended privacy interval and speech recovery.

Do not loop muting actions, leave an emergency or production path without a recovery guard, or claim privacy from a response alone. No PBX, manager action, dialplan, channel, bridge, conference, recording, packet, media frame, endpoint, speaker, microphone or live call was inspected or tested.

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 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: channel, direction and media proof

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

Read guide →
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 →
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 →
Troubleshooting · RFC 3264 offer/answer behavior, current Asterisk res_pjsip media controls and Wireshark RTP analysis documentation reviewed October 5, 2026; no PBX, endpoint, trunk, firewall, packet stream, media transition or call tested

Intermittent one-way audio after hold, transfer or idle time

Compare the exact working and failing call phase, SDP direction and RTP path across hold, resume, transfer or idle time before changing NAT, direct-media or timeout controls.

Read guide →
Hub

VoIP troubleshooting

Use symptoms and evidence to isolate registration, routing, media and device faults.

Explore topic →