A call through a DID number sometimes sounds worse than a mobile call: the voice buzzes, words overlap, the other person drops out mid-sentence. Figuring out whose fault it is — your network, the carrier, or the other side — only makes sense once you know what voice quality depends on. Here is what shapes it, what counts as normal, what symptoms mean, and what you can fix.
What voice quality is built from
Voice in a SIP call becomes a stream of data packets, and four parameters define its quality. The codec compresses and decompresses the audio: one option carries voice with almost no loss at the cost of a wide channel, another saves bandwidth at the cost of a rougher timbre. The codec sets the quality ceiling before a packet reaches the network.
Packet loss is the share of voice fragments that never arrive or arrive corrupted: the codec smooths over each lost packet or turns it into a click. Jitter is the unevenness of intervals between packets: the network doesn't deliver them on schedule, so the receiver keeps a buffer to reassemble a steady stream. Delay is the time from a spoken word to its arrival — encoding, network path, and buffering combined.
What values count as acceptable
One-way delay under 150 ms isn't felt as a conversation at all — replies overlap the way they would in person. Between 150 and 300 ms, tiny pauses and interruptions appear, but the dialogue stays comfortable. Past 300 ms, a call turns into a walkie-talkie exchange, both sides waiting their turn.
Packet loss under 1% is practically inaudible: the codec substitutes a smoothed patch for the missing fragment instead of silence. At 1–3%, clicks and dropouts slip through; above 5% a call gets choppy enough that redialing is easier. Jitter under 30 ms is fully absorbed by the receiving buffer. Above that, the buffer either grows, adding delay, or discards packets that arrived too late.
Typical symptoms and their causes
A metallic, "robotic" voice usually points to packet loss: the loss-concealment mechanism substitutes a synthetic fragment for the missing speech, and it sounds unnatural. The same effect appears when codecs conflict between the sides and the signal gets re-encoded several times, losing timbre detail.
Echo is a delayed copy of your voice returning through mic-speaker coupling or a gateway desync; the longer the delay, the more noticeable the echo. One-way audio is a classic sign the voice stream is blocked in one direction by network equipment, even though registration went through fine. Dropped calls usually line up with bursts of packet loss on a congested segment or a timeout between device and server.
What you can fix on your side, and what you can't
There is a lot you can influence yourself. A wired connection instead of wireless removes the micro-delays typical of Wi-Fi. Prioritizing voice traffic on a router stops background downloads from eating the channel mid-call. The jitter buffer in a softphone can be tuned: bigger for a small delay on an unstable channel, smaller for responsiveness on a steady one. A wired headset instead of a built-in mic cuts echo.
What you can't control is backbone route quality, congestion on the carrier's side, and how many hops a packet crosses. The only lever left is a provider that shares quality statistics openly and lets you switch routes.
Why calls break down before web pages do on a congested link
Voice traffic is real-time and cannot wait: a packet more than a few dozen milliseconds late is already useless and gets dropped — irreversible and audible at once. A web page is different: it's "elastic" traffic, where a lost packet gets requested again, and an extra 200 ms turns into one extra second of a spinner nobody notices.
That's why, on the same congested link, voice breaks first — crackling, turning metallic, dropping words — while pages and messengers keep loading as if nothing happened. If calls got worse specifically during peak hours, the culprit is channel contention, not the number.
Frequently Asked Questions
How do I tell if the problem is my network or the other person's?
Call someone else from the same device over a different connection — mobile data instead of wired. If the problem repeats regardless of party or network, the cause is on your side; if audio is clean except with one person, the issue is likely on their end.
Can I improve the sound without buying new equipment?
Yes — settings usually do it: switch to a wired connection, enable voice traffic priority on the router, and pause background downloads during calls. That clears up most jitter and loss at no cost.
Why does the sound disappear in only one direction?
Usually the voice stream is blocked in one direction by network equipment while registration passes freely, creating the impression the connection is "half working." This is covered in the article on SIP connection of a number to a softphone.
If sound stays unstable after checking settings, check call statistics in your dashboard and describe a persistent issue to support. The catalogue of DID numbers by country and connection type is in the DID numbers section on turbon.rent.