Skip to content

Satellite

Why voice over satellite needs different thinking

22/10/2026 · 2 min read · Tanveer Ahmed

Applies to Satellite / VSAT This applies to voice over geostationary satellite links with any PBX, codec or router; the principles are vendor-neutral.

Standard guidance says keep one-way delay under 150 ms for good conversational quality. A geostationary hop is around 250 ms one way before anything else happens. The usual target is unreachable by definition.

That does not make voice over satellite unusable. It means the goals change.

What you optimise instead

Since latency is fixed, everything else must be excellent. Jitter must be minimal, because a jitter buffer adds to a delay budget that is already spent. Loss must be near zero, because concealment is more noticeable when the conversation is already strained by delay.

Consistency matters more than absolute numbers. A steady 600 ms is workable once people adapt. A path varying between 600 and 900 ms is not, because the jitter buffer must grow to accommodate the worst case and everyone pays that cost continuously.

Codec choice

Bandwidth on satellite is expensive, which pushes towards compressed codecs. But compression adds algorithmic delay and reduces resilience to loss. G.729 saves bandwidth and costs quality on a path that has none to spare.

Where capacity allows, a less aggressive codec often produces better calls, because you are not spending quality on a link that is already consuming the delay budget.

Echo becomes audible

Echo that is imperceptible at 20 ms is very obvious at 500 ms — the delay is long enough that the speaker hears their own voice as a distinct repeat. Echo cancellation that was adequate on a terrestrial network may not be over satellite, and this is a frequent cause of complaints that get misattributed to the link.

Queueing

Strict priority for voice, and police it so a misconfigured endpoint cannot starve everything else. On a narrow link, large data packets ahead of a voice packet add meaningful delay — link fragmentation and interleaving addresses that, and it matters more here than anywhere else.

Set expectations

Explain the delay before deployment. Users who expect a pause adapt within days. Users who were promised a normal call experience report a fault that cannot be fixed.

Related reading