Skip to content
Phone Guides

Diagnose one-way and missing Asterisk audio

Name the missing direction first: which party cannot hear which other party? Then identify where media is expected to travel for that call. Successful registration, ringing and answer establish signalling stages; audio needs its own evidence.

Source-reviewed, 19 October 2026. Prepared from the cited documentation. No audio path has been independently tested by Phone Guides. Scope: Asterisk 22/PJSIP diagnosis; exact endpoints, networks and clients remain deployment-specific.

Describe one failed call

Record the two endpoints, carrier if involved, time, call identifiers, answer stage and whether failure starts immediately or after hold/transfer. Compare a local call with a carrier call only after recording how their paths differ.

Use the upstream PJSIP NAT guidance and PJSIP option reference for the relevant address and media settings. Avoid copying a complete NAT recipe without matching its topology.

Compare the advertised and observed paths

Evidence Question it answers
Negotiated SDP Where does each participant say it will receive media?
Observed media packets Is traffic sent towards that address and port?
Observation on the receiving side Does traffic arrive through the network boundary?
Negotiated formats Do payload and codec interpretations agree?
Endpoint playback/input Is received audio rendered and microphone audio produced?

Inspect both directions. Seeing packets leave one system does not prove they arrive at the other. A SIP-only trace cannot establish the entire RTP path. Keep packet material private because it can include recoverable conversation audio.

Follow one media direction across the call

For a single affected call, record the negotiated SDP for each call leg and any later offer/answer after hold or transfer. Compare the advertised connection address and audio port with the actual RTP destination and the packets observed at each network boundary. This separates a wrong advertised destination from packets that leave one side but fail to arrive at the next. Keep timestamps and the call's channel identifiers with each observation.

Before expecting to see RTP on Asterisk's external interface, establish whether media should traverse Asterisk. The PJSIP direct_media setting controls whether endpoints may send media directly to one another. With direct media in use, an empty Asterisk-side capture during the established media phase does not by itself prove packet loss. If Asterisk should remain in the media path, compare the exact transport's local-network and external-media address settings with the observed topology. The official NAT guide explains the separate roles of local_net, external_media_address, external_signaling_address and direct_media; it is an example topology, not a universal configuration.

Check where Asterisk belongs in the path

Determine whether media should pass through Asterisk or travel directly between endpoints. A change after answer, hold or transfer can produce a different destination from the initial offer. Include re-negotiation when the symptom begins later in the call.

For NAT, distinguish signalling contact handling from media address handling. The options controlling them have different purposes. Confirm the configured local networks and external address against the actual topology; do not treat every private address in a trace as erroneous.

Inspect formats and devices

Use codecs and transcoding for negotiated formats and module availability. Traffic arriving at the expected address does not prove that it decodes into useful speech. Include mute, input selection, output selection and browser microphone permission where relevant.

If encrypted media is used, check the documented security negotiation on that exact leg. Correct the trust/keying mismatch through its supported configuration; turning off protection is not a diagnosis.

Make a narrow correction

Preserve the old setting, change the value supported by the evidence and repeat the same call. Check both audio directions, hold/resume, transfer and hangup where those features are in scope. Stop extra diagnostics afterwards.

Use NAT and RTP for the topology worksheet and WebRTC for browser-specific dependencies. If media is present but digits fail, use DTMF diagnosis.

Return to Asterisk documentation.