VOS3000 fix

VOS3000 one-way audio or no audio

The call connects, but one side hears nothing. Here is why it happens and how to fix it.

Updated · By the VOS3000 Web team

Quick answer: One-way or no audio in VOS3000 is almost always a media (RTP) problem, not a signalling one: NAT puts a private address in the SDP, a firewall blocks RTP, SIP ALG rewrites packets, or the two sides share no codec. The usual fix is to turn the gateway's Media proxy on, check the codecs and let RTP through every firewall on the path.

Usual cause
NAT, a firewall or SIP ALG on the audio path
First setting
Additional Settings, Normal, Media proxy
Codec check
Additional Settings, Codec
CDR clues
NoAudioDataTimeout (-55), AudioCodecsNotMatch (-45)

Why it happens

A SIP call has two parts. Signalling (SIP) sets the call up, and the SDP inside it tells each side where to send the audio. The audio itself (RTP) travels separately. When the call connects but audio fails, signalling worked and the audio path did not. The usual causes are:

  • NAT: a device behind a router puts its private address in the SDP, so audio is sent somewhere it can never arrive.
  • Firewalls: a firewall lets SIP through but blocks the RTP ports.
  • SIP ALG: a router "helps" by rewriting SIP packets and breaks the SDP.
  • Codecs: the two sides share no codec, so no audio can be exchanged.

1. Find the pattern in the CDR

Open the CDR for the failing calls. Do they share one mapping gateway (one customer) or one routing gateway (one carrier)? Look at the Caller ip, Callee ip and Termination reason. NoAudioDataTimeout (-55) means audio stopped arriving, AudioCodecsNotMatch (-45) means no shared codec, and MediaForwardingFail (-80) means VOS3000 could not relay the audio.

2. Turn on Media proxy

Open the gateway's Additional Settings → Normal. Media proxy has the options Auto, On, Off and Must on. With Media proxy on, the audio of the call flows through VOS3000, so each side only has to reach your server. This fixes most NAT problems. Set it on the gateway where audio fails: the customer's mapping gateway or the carrier's routing gateway.

3. Use the address packets really come from

Under Additional Settings → Protocol → SIP, Reply address can be Socket, Via Port or Via, and Request address can be Socket, Contact Port or Contact. Socket uses the address the packets actually came from, not the address written inside them, which helps with devices behind NAT.

4. Turn off SIP ALG

Ask the customer or carrier to turn off SIP ALG (sometimes called SIP helper or SIP inspection) on their router or firewall. It is a frequent cause of one-way audio that no switch setting can fully undo.

5. Let RTP through every firewall

Audio uses a range of UDP ports, separate from the SIP port. Make sure the firewalls at your data centre, at the customer and at the carrier allow RTP, not only SIP.

6. Check the codecs

Under Additional Settings → Codec, choose between Auto negotiation and Softswitch specified, and order the codecs with Move up and Move down. Make sure both sides share at least one codec, for example G729 or PCMA. If they cannot, turn on Allows audio transcoding. For G729, G729 negotiation mode on the SIP tab can be Auto, G729, G729a or G729&G729a.

Rtp interrupt detection

On the Normal tab, Rtp interrupt detection (None, Server to remote, Remote to server or Bidirection) ends calls when audio stops, so you are not billing silent calls. If many calls end with NoAudioDataTimeout, fix the audio path with the steps above rather than turning the check off.

Questions about this topic

Does Media proxy use more bandwidth?

Yes. With Media proxy on, the audio of those calls flows through your VOS3000 server, so the server carries both directions of every call.

Is one-way audio a VOS3000 bug?

Rarely. It is almost always NAT, a firewall or SIP ALG between the switch and a customer or carrier.

Why do calls end with NoAudioDataTimeout?

VOS3000 stopped receiving audio and ended the call. Rtp interrupt detection in Additional Settings controls this check. The cause is usually upstream: fix the audio path rather than turning the check off.

Should I turn on Media proxy for every gateway?

No. Use it where audio fails, usually customers or carriers behind NAT. Leaving it on Auto elsewhere saves server bandwidth.

Try every step in the live demo

Each screen in this guide is in the VOS3000 Web demo, with made-up data. Sign in with demo / demo.