One-way or no audio on calls

Symptom: you can hear the other person but they cannot hear you (or the reverse), or there is no audio at all.

Quick checks first

  1. Make sure the handset, headset or speakerphone is not muted.
  2. Try the handset, then a headset, to rule out a faulty handset or headset.
  3. Test both directions — make a call out and receive a call in.
  4. Dial 160 (echo test). If you hear your own voice echoed back, audio is working in both directions on that leg.

Most common causes

  • SIP ALG on the router — the single most common cause. It rewrites the audio (RTP) port information inside SIP packets. Disable it (see the SIP ALG article).
  • Codec mismatch — both ends must agree on the audio codec (for example G.711, G.722 or G.729). Check the codec settings on your handset or PBX against the platform defaults.
  • RTP blocked by the firewall — the SIP signal (port 5060) connects but the audio stream (RTP) is blocked, so the call connects with no sound.
  • NAT or port translation — a router that does not keep NAT sessions alive can drop the audio path. This is worse behind CGNAT (see the CGNAT article).

What to try

  1. Disable SIP ALG and any SIP transformations on the router, then reboot the router and phone.
  2. Move the phone to a wired Ethernet connection to rule out Wi-Fi.
  3. Reboot the phone and allow it to re-register.
  4. If the phone supports it, enable TLS for SIP signalling — this bypasses ALG inspection entirely.

If the problem persists, raise a ticket and tell us whether the fault is on incoming, outgoing or both call directions, and whether the echo test (160) works.

ArmourTel · www.armour.tel · support@armour.tel