How calls travel

HD Voice explained: why some calls sound crisp and others sound like a tin can

How calls travel · · Published 2026-11-14

Black-and-white photo of a man in a cap talking on a corded payphone in an airport hall, next to a row of phone booths and a luggage trolley
A payphone at Montréal-Trudeau airport. Fixed telephone networks were built to carry only a narrow slice of the human voice, and that legacy still shapes how many calls sound today.

Some calls sound as if the other person is in the room. Others make "f" and "s" impossible to tell apart, so you end up spelling your postcode with "F for Freddie". The difference is rarely your hearing or the other person's phone. It is mostly about how much of the voice the network was asked to carry, and whether every link between the two of you agreed to carry it. That is what the label "HD Voice" is about.

The telephone band: an old compromise still in use

Classic telephone networks carry roughly 300 to 3,400 Hz of sound. That band was chosen as a trade-off: it keeps speech intelligible while saving capacity on cables and switches. When telephone networks went digital, the standard way to encode a call, ITU-T G.711, sampled that band 8,000 times a second and sent it at 64 kbit/s (ITU-T G.711). Engineers call this narrowband audio.

The problem is that a lot of what makes a voice recognisable sits outside that band. The fundamental pitch of many voices is below 300 Hz, so the network leaves your brain to reconstruct it from the harmonics. The hiss of "s", "f" and "th" carries much of its energy above 3.4 kHz, which is why those consonants blur together. Narrowband calls are understandable, but they demand concentration, and in a noisy place or in a second language that effort adds up.

Wideband, super-wideband and fullband

"HD Voice" is a marketing label, used across the mobile industry and promoted by the GSMA, the operators' association, for calls that carry a wider slice of audio. Behind the label are a few codecs, the software that compresses the voice for transmission:

NameTypical audio rangeCodec examplesWhere you meet it
Narrowbandabout 300–3,400 HzG.711, AMRTraditional landlines, 2G calls, any call that falls back
Wideband ("HD Voice")about 50–7,000 HzAMR-WB (G.722.2), G.722Most VoLTE and Wi-Fi calls between compatible phones, many DECT home phones
Super-wideband and fullbandup to about 14,000 Hz (super-wideband) or 20,000 Hz (fullband)EVS, OpusNewer VoLTE and 5G voice where supported, and most calling apps

The mobile wideband codec, AMR-WB, is standardised by the ITU as G.722.2 and designed to give wideband speech at around 16 kbit/s, adapting its rate to radio conditions (ITU-T G.722.2). Its successor, EVS (Enhanced Voice Services), was specified by 3GPP, the body that writes mobile standards, for 4G and later networks. It can switch between narrowband, wideband, super-wideband and fullband, and is built to cope better with lost packets (3GPP TS 26.441). Operators often market calls using it as "HD Voice+" or "Ultra HD Voice", but the names are not standardised.

Wider audio does not have to mean more data. Modern codecs are far more efficient than G.711; our guide to how much data a VoIP call uses works through the bit rates codec by codec.

The weakest link decides

An HD call is an agreement, not a feature of one phone. When a call is set up, the two ends and the networks between them negotiate a codec both sides support. If any link in the chain only speaks narrowband, the whole call drops to narrowband, or the network converts the audio from one codec to another along the way. That conversion, called transcoding, throws away the extra bandwidth and adds a little delay.

In practice, a call is likely to stay wideband when:

International calls are the hardest case. A call that crosses several carriers between two countries has more chances of meeting a narrowband or transcoding hop, so it may sound worse than a domestic call between the same two phones.

Why apps often sound better

When you call through an internet app, both ends run the same software, so the app chooses the codec and never has to negotiate with a telephone network in the middle. Many apps, and browser calls using WebRTC, use Opus, an open codec that adapts from narrowband to fullband according to the connection. That is why an app call between two smartphones on good Wi-Fi often sounds richer than a regular call between the same phones.

The trade-off is that app quality depends entirely on your data connection. On a crowded or unstable network, the app lowers its bit rate, and packet loss and jitter take over as the main problem. Our guide to why VoIP calls break up covers those effects and how to reduce them.

What you can check yourself

  1. Turn on VoLTE and Wi-Fi calling. On most phones both are in the mobile network settings. Some plans include them only on request, or not at all on prepaid or older plans; your operator's help pages say which.
  2. Look for an indicator. Some Android phones show "HD", "VoLTE" or "VoWiFi" in the status bar or on the call screen during an HD call. Not every model does, and the absence of an icon does not prove the call is narrowband.
  3. Test with a known contact. Call someone on the same operator, both on 4G or 5G, then compare with a call to a landline. If the first does not sound clearly better, check the settings on both phones.
  4. Mind your headset. Bluetooth adds its own limit. Older hands-free links carried only narrowband audio, and later versions added wideband speech, so an old headset can downgrade a perfect HD call.
  5. Do not blame the microphone first. A dirty microphone grille, a thick case over it or aggressive noise suppression can make any call sound muffled, but they will not turn a wideband call into a narrowband one. If every call sounds the same, the codec is the more likely cause.

The short version

HD Voice is not a separate service you buy: it is what happens when every part of a call, from your phone and plan to the networks in between and the phone at the other end, supports a wideband codec. A call is only as good as its narrowest link. Keeping VoLTE and Wi-Fi calling on, using a reasonably recent headset and switching to an app for long international calls will remove most of the tin-can effect you can control.