Voice Over Satellite and High-Latency Links: Designing for Delay You Cannot Remove
A geostationary satellite adds roughly a quarter of a second in each direction before any terrestrial network is involved. Half a second of round-trip delay is not a bug to be fixed. It is a property of physics, and the phone system either accommodates it or the site has unusable voice.
Build a Delay Budget Before Choosing Anything
The single most useful design artefact for a high-latency site is a delay budget: a table of every contribution to round-trip time, with a target for the total. Codec packetisation, jitter buffer, satellite hop, terrestrial backhaul, and any media relay each add their own. When the budget is written down, the trade-offs become visible, and arguments about audio quality turn into decisions about where to spend milliseconds.
Above roughly 300 milliseconds round trip, conversation changes character. People finish sentences and start again, because the pause tells them the other party has not heard. That behaviour is not something training can fully correct, and it is worth telling users in advance rather than letting them conclude the system is broken.
| Contribution | Typical value | Where the millisecond goes |
|---|---|---|
| Codec packetisation | 20 to 40 ms | Smaller packets cost bandwidth, not delay |
| Jitter buffer | 20 to 80 ms | Adaptive buffers grow under jitter and stay grown |
| Satellite hop, geostationary | about 240 ms each way | Fixed, not negotiable |
| Satellite hop, low earth orbit | 30 to 60 ms each way | Varies with constellation geometry |
| Terrestrial backhaul | 5 to 40 ms | Controllable by path choice |
| Media relay or SBC | 1 to 10 ms | Worth measuring rather than assuming |
Codec Choice Is a Bandwidth Decision, Not a Delay Decision
A common misconception is that a higher-compression codec reduces delay. It usually reduces bandwidth and may increase delay, because more compressed speech needs more frames to recover from loss. On a high-latency link the priority order is: prevent loss, keep packets small enough for the link's MTU, and select a codec the link can carry without congestion. A modest codec at a stable rate beats an excellent codec on a saturated link.
Echo Control Becomes Critical
Echo is unnoticeable at low delay and unbearable at high delay, because the reflected speech arrives long after the speaker has stopped. The echo canceller has to be good, and the acoustic path has to be quiet: handsets rather than speakerphones, headsets rather than laptop speakers. Where the site uses conference equipment, an external echo canceller is often the only way to make a satellite call usable.
- Write the delay budget and review it whenever the path changes
- Prefer handsets and headsets over speakerphones on high-latency links
- Keep packet loss near zero; loss hurts more than delay
- Set jitter buffers explicitly rather than letting them grow unbounded
- Tell users what to expect so they do not attribute delay to a fault
- Provide local call handling so internal calls do not traverse the link
- Test with the real codec, on the real link, at peak hours
Local Survivability Does Most of the Work
Where the link is slow, expensive, and occasionally absent, the most valuable design decision is to keep internal calls inside the site. A local gateway or a local instance that registers against the central platform gives extensions that can call each other, reach emergency services through a local trunk, and continue operating when the satellite link drops. The central platform then handles what it is good at: configuration, numbering, and reporting, with the delay confined to calls that genuinely need to leave the building.
Redstone Approach
Redstone deployments at remote and high-latency sites use local gateways for internal call handling and PSTN breakout, with the central IP-PBX retaining configuration and numbering authority. Codec and jitter buffer settings can be set per site, which allows a slow link to be tuned without changing behaviour at well-connected offices.
Redstone Systems, Inc. founded in Delaware, USA in December 2002, has been the ODM vendor for many well-known communications companies, serving the Southeast Asian market. In 2020, Redstone Systems will begin to return to the North America market with its self-developed brand.
Redstone has a complete product line of intelligent voice gateways, providing IP-PBXs, analog VoIP gateways (FXS/FXO), digital VoIP gateways (E1/T1), border appliances, and session boundary controllers (SBCs).
With advanced technology in digital signal processor (DSP), speech coding and speech processing, as well as efficient operational tools such as cloud remote management, auto provisioning, Redstone gateways are widely used in markets of enterprise communications, cloud communications, call centers, operators’ IMS/SIP trunks, bringing users friendly, efficient and reliable communication experience.
For more information about Redstone, You can follow us on Facebook, Linkedin, and Youtube to be the first to get the latest news.

Current Location :

