VOS3000 fix

VOS3000 echo and delay

A softswitch does not make echo, but customers will still blame you. Here is how to find where it really comes from.

Updated · By the VOS3000 Web team

Quick answer: VOS3000 does not create echo: echo comes from a phone or a PSTN line on one side and becomes noticeable when the delay is high. Find out whether it follows one carrier or one customer, check the round-trip delay to that side, and remove extra hops such as a far-away server or an unneeded media proxy.

Echo source
A phone, headset or PSTN line
Makes it worse
High delay
First check
Does it follow one carrier?
Fix delay
Shorter path, fewer hops

Where echo comes from

Echo is a caller hearing their own voice back. It is created at the far end of the call: by a speakerphone or headset that leaks sound into the microphone, or by a PSTN line (a 2-wire to 4-wire hybrid) without good echo cancellation. VOS3000 forwards packets; it does not create echo.

Delay is what turns a little echo into a problem. With a short delay the echo blends with your own voice; above about 150 ms one way, the delay itself is noticeable and the echo becomes clear.

Step 1: find the pattern

  • In Recent CDR, check whether the complaints share one routing gateway (a carrier) or one mapping gateway (a customer).
  • Make test calls to the same number through a different carrier. If the echo goes away, the first carrier's route is the cause; send them the examples.
  • Ask who hears the echo. If your customer hears themselves, the echo is made on the called side.

Step 2: measure the delay

From the VOS3000 server, ping the customer's and the carrier's IPs. The one-way delay of the call is roughly the sum of both paths, plus the time the phones and gateways need to encode and buffer audio.

Step 3: cut the delay

  • Server location: a server close to your customers and carriers saves the most. Traffic from Europe to Europe through a server in Asia can add 300 ms or more. We host VOS3000 in London, Frankfurt, Singapore and New York; see VOS3000 hosting.
  • Media proxy: with it on, audio goes through your server. That fixes NAT problems but adds a hop when your server is far from both sides. Use Auto unless a gateway needs On; see media proxy.
  • Codecs: G.729 adds a little encoding delay compared with G.711, and every transcoding step adds more. Use the same codec end to end where you can; see codecs and DTMF.
  • Ptime: on a routing gateway's SIP settings, Ptime adaptive keeps the packet interval consistent with what the other side expects when media proxy is on.
  • Server load and network: a busy server or a full network link adds jitter, which phones hide by buffering more, which adds delay. Check CPU use and bandwidth at busy hours.

Other audio problems

No audio, or audio in one direction only, is a different problem; see one-way audio. To look at the actual RTP streams, capture the call; see debug trace and SIP capture.

Questions about this topic

Can VOS3000 cause echo?

No. Echo comes from a phone, headset or PSTN line at one end. VOS3000 can only make it more noticeable by adding delay, for example through a distant server.

Who hears the echo?

The person who hears their own voice back. The echo is created at the other end of the call, so look at the far side first.

How much delay is too much?

Above roughly 150 ms one way, people start to notice it, and echo becomes much easier to hear.

Run VOS3000 without the server work

Pick a VOS3000 server hosted by us, or have us install VOS3000 on your own server. VOS3000 Web and the Android app come with it.