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

Asterisk ARI snoop is silent or whisper is not heard

Follow one target and snoop ID through parameter validation, Stasis ownership, direction, channel lifecycle, downstream media and audible result before changing the wider call path.

Reviewed 2026-10-09Current first-party Asterisk 22 and Certified Asterisk 22.8 ARI Channels, channel lifecycle, ARI configuration, REST-over-WebSocket, data-model and ChanSpy documentation reviewed October 9, 2026; no HTTP server, ARI identity, Stasis application, target channel, snoop channel, bridge, endpoint, packet, media stream, recording, monitor, whisper or call was inspected or testedAdvancedDocumentation based · not lab tested

Freeze the target, snoop ID and intended direction

Preserve one authorized attempt with timestamp and timezone, running Asterisk version, ARI identity, Stasis application, target channel ID and state, snoop ID, spy, whisper, appArgs, HTTP response and all target and snoop channel events. Do not replace the target with a new call leg while diagnosing the original request.

Classify the symptom precisely: 400 invalid parameters, 404 target missing, snoop channel created but no StasisStart, spy silent, wrong talker or direction, whisper absent, whisper reaches only one party, downstream recorder or External Media silent, or media works but the expected listener cannot hear it.

Resolve request failure before media debugging

A 400 indicates invalid snoop parameters; verify the exact allowed spy and whisper values and required application. A 404 means the referenced target channel was not found. Correlate the target's creation, UniqueID and hangup time before treating that response as an ARI transport or authorization failure.

Confirm the target is the real media-bearing channel, not a stale name, Local-channel half or display label selected from an earlier snapshot. Correct target identity or request syntax before opening firewall rules, changing codecs or rebuilding the application.

Prove the snoop channel entered the intended application

Match the returned snoop Channel object to StasisStart in the requested application and retain its channel ID independently from the target. If the event connection was unavailable, reconcile server-side channel state and the application subscription before issuing another snoop.

A target still in Stasis does not prove the new snoop channel is being consumed. Verify the later operation that connects the snoop to recording, playback, a bridge or External Media, together with that resource's own response and events.

Test spy direction with known audio

Verify that spy is not none, then map in, out or both relative to the selected target channel. Use a bounded authorized source on one side at a time and correlate target-channel packets or decoded audio with the snoop consumer. Do not infer caller and agent direction from the words alone.

If only one talker appears, first determine whether that is the requested scope. Then separate an empty direction from a consumer, translation, recording or External Media fault. A valid snoop channel with a silent selected direction is not evidence of packet loss.

Test whisper direction and the actual listener

Verify that whisper is not none, identify which direction on the target is being injected and name the endpoint expected to hear it. Correlate application-produced samples, snoop-channel media, target-channel output and the far endpoint's decoded result. A write accepted by the application or a channel event is not audible evidence.

If both parties were expected to hear the intervention, confirm that the chosen target and direction can produce that outcome. Do not broaden to both until the authorization and call graph support it, and do not treat whisper as a substitute for explicit conference membership.

Correct one owner, retest and remove the snoop

Change only the evidenced owner: target identity, invalid parameter, Stasis subscription, spy direction, whisper direction, downstream media consumer, format or channel lifetime. Retest one authorized call and retain request, events, directional source, consumer result, listener result and cleanup.

Hang up the snoop channel at the authorized end without terminating the target unless the call owner requires it. Remove temporary captures and logs, confirm no orphaned snoop remains, and preserve the audit record required by local policy. No channel, packet, monitor, whisper or call was inspected or tested for this diagnostic.

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 first-party Asterisk 22 and Certified Asterisk 22.8 ARI Channels, channel lifecycle, ARI configuration, REST-over-WebSocket, data-model and ChanSpy documentation reviewed October 9, 2026; no HTTP server, ARI identity, Stasis application, target channel, snoop channel, bridge, endpoint, packet, media stream, recording, monitor, whisper or call was inspected or tested

Asterisk ARI snoop channels: spy, whisper and directional media

Attach an application-owned snoop channel to one target channel, preserve spy and whisper direction separately, and prove the resulting media path without treating channel creation as audible success.

Read guide →
Guide · Current Asterisk 23 ARI channel, Stasis and bridge documentation reviewed October 9, 2026; no HTTP server, TLS profile, WebSocket, ARI user, application, host, endpoint, channel, bridge, media path or call was inspected or tested

Asterisk ARI channel origination: create, dial and prove application control

Choose direct originate or create-then-dial, retain client identifiers, and separate HTTP acceptance, Stasis ownership, answer, bridge membership, media and application outcome.

Read guide →
Guide · Current first-party Asterisk ARI Channels, External Media, AudioSocket, WebSocket, ARI configuration and bridge documentation reviewed October 9, 2026; no HTTP server, ARI user, Stasis application, channel, bridge, host, socket, DNS answer, firewall, RTP packet, AudioSocket frame, WebSocket frame, codec, transcription service, media stream or call was inspected or tested

Asterisk ARI External Media: channel, driver and bridge boundaries

Choose the RTP, AudioSocket or WebSocket driver tuple, fix the media format, join the intended bridge and prove both media directions independently.

Read guide →
Troubleshooting · Current first-party Asterisk ARI Channels, External Media, AudioSocket, WebSocket, ARI configuration and bridge documentation reviewed October 9, 2026; no HTTP server, ARI user, Stasis application, channel, bridge, host, socket, DNS answer, firewall, RTP packet, AudioSocket frame, WebSocket frame, codec, transcription service, media stream or call was inspected or tested

Asterisk ARI External Media is silent, one-way or decoded incorrectly

Trace the External Media driver tuple, channel and bridge state, selected format, outbound destination and inbound return tuple before changing codecs or firewall rules.

Read guide →
Guide · Current first-party Asterisk ARI recording, channel, bridge, data-model and configuration documentation reviewed October 9, 2026; no HTTP server, ARI user, WebSocket, Stasis application, channel, bridge, recording, stored file, codec, packet, endpoint, participant, consent workflow or call was inspected or tested

Asterisk ARI recordings: live control, stored files and media scope

Record a channel or bridge with an application-owned name, then keep live state, events, stop or cancel, stored-file state and audible content as separate evidence.

Read guide →
Troubleshooting · Current first-party Asterisk ARI recording, channel, bridge, data-model and configuration documentation reviewed October 9, 2026; no HTTP server, ARI user, WebSocket, Stasis application, channel, bridge, recording, stored file, codec, packet, endpoint, participant, consent workflow or call was inspected or tested

Asterisk ARI recording is missing, empty or wrong scope

Follow one recording name through target ownership, start response, events, live controls, stop or cancel, stored inventory and decoded media evidence.

Read guide →
Guide · Current first-party Asterisk ARI bridge, mixing, holding, operations, event-model and recording documentation reviewed October 9, 2026; no HTTP server, ARI user, Stasis application, bridge, channel, endpoint, socket, packet, media frame, playback, recording, DTMF result or call was inspected or tested

Asterisk ARI bridges: ownership, membership and media topology

Choose a mixing or holding bridge deliberately, keep it inside the intended Stasis application and prove channel membership separately from media behavior.

Read guide →
Troubleshooting · Current first-party Asterisk ARI bridge, mixing, holding, operations, event-model and recording documentation reviewed October 9, 2026; no HTTP server, ARI user, Stasis application, bridge, channel, endpoint, socket, packet, media frame, playback, recording, DTMF result or call was inspected or tested

Asterisk ARI channel will not join a bridge or has no media

Trace the exact bridge and channel through Stasis ownership, add-channel response, membership events and selected media topology before changing codecs or recreating resources.

Read guide →
Troubleshooting · Current Asterisk ARI overview, configuration, getting-started, Stasis application, res_ari and outbound-WebSocket documentation reviewed October 6, 2026; exact running branch, build options, modules, configuration, credentials, application process, proxy, WebSocket, dialplan, channel and call require runtime verification

Asterisk ARI Stasis application is not registered: control-path diagnosis

Trace HTTP service, ARI user, WebSocket ownership, exact application name and Stasis lifecycle when a channel immediately leaves an ARI application.

Read guide →
Guide

PBX logs and packet captures: useful evidence with limited exposure

Collect enough to diagnose a call while protecting identities, secrets and audio.

Read guide →