Home Internet and Work Calls: What You Can Actually Control

Poor work from home call quality is almost never a shortage of bandwidth. A voice call needs roughly 100 kbps in each direction. What breaks it is competition for the upload path, Wi-Fi interference, and a VPN routing voice through a data center it never needed to visit. All three are fixable from the house.

Why do work calls sound bad at home specifically?

Because a home network is built for downloading, and a call is an upload.

An office network is engineered, at least loosely: a business circuit, a switch, and often a rule giving voice priority. A household network is whatever the ISP shipped, serving a video call in one room, a console patching itself, and a laptop syncing a folder — all on one asymmetric connection whose upload side is a fraction of the download side.

The classic report follows: "they say I sound choppy, but they sound fine to me." That is one-directional, and the direction is upload.

Three words make the rest concrete:

Packet loss — audio that never arrives. Sounds like words dropping out.

Jitter — audio arriving at uneven intervals. Sounds robotic or underwater.

Latency — audio arriving late. Sounds like talking over each other, and becomes noticeable past about 150 ms one way.

Bandwidth causes none of these directly. Congestion causes all three, which is why an upgraded plan so often changes nothing. Why VoIP calls sound bad covers the office version.

How much upload does a VoIP call actually need?

About 87 kbps per call with the standard G.711 codec including overhead, so plan 100 kbps in each direction per concurrent call.

The number settles the argument: if a 300 Mbps connection cannot carry a 100 kbps call cleanly, the problem is not the size of the pipe. Something is taking priority away from voice or introducing variability into the path.

What can you actually control in a house?

Five things, in the order worth doing them.

1. Use Ethernet for the device that carries calls. The highest-value change, and the one most people skip because the desk is not near the router. A long flat cable costs less than one bad call.
2. Stop competing with yourself. Cloud backup, photo sync, and game updates are the usual upload thieves, and all are schedulable. Run them overnight.
3. Turn on QoS, prioritizing the device rather than the protocol. Consumer routers identify voice traffic poorly and prioritize a named device well. Give the work computer or desk phone the top slot.
4. Disable SIP ALG. On by default on many consumer routers, it rewrites SIP packets in transit and corrupts them — one-way audio, dropped registrations, phantom ringing. It causes more VoIP faults than any other setting; network requirements covers it and the ports.
5. Fix the headset before blaming the network. A cheap microphone sounds exactly like a bad connection, and no network work improves it.

Two things you do not control: the neighborhood's evening load, and the far end's phone.

Does a VPN make work calls worse?

Usually, yes — and this is the easiest fix to make and the least often considered.

A VPN sends your voice packets to a corporate gateway before they go anywhere useful, adding a hop, latency, and a queue tuned for file traffic rather than audio. If the gateway sits in another region, every call carries that round trip for no benefit.

The point worth making to whoever administers it: a hosted phone system does not need the VPN. Phones and softphones connect outbound, and no inbound port forwarding is required.

If the VPN is mandatory for other reasons, ask for split tunneling that excludes voice. If that is refused, measure it — place the same call on and off the tunnel and listen.

The same applies to consumer privacy VPNs on a personal laptop — an invisible cause, because nobody counts them as part of the phone setup.

Is Wi-Fi good enough?

For an occasional call, generally yes. For someone whose job is the phone, no — use Ethernet.

Wi-Fi's problem is not throughput, it is variability. A microwave, a neighbor's access point on the same channel, a laptop roaming to a mesh node mid-sentence: each produces jitter, and jitter makes voice sound robotic. A file transfer absorbs this by retrying. A live call cannot retry — the audio was needed a moment ago.

If Ethernet is impossible: use the 5 GHz band, stay within sight of the access point, and stay in one room to avoid mesh handoffs mid-call. Try a powerline or MoCA adapter first. Wi-Fi or Ethernet for desk phones goes deeper on handsets.

What should you report when calls sound bad?

Three facts, and the case resolves in one exchange instead of five.

Which direction. Did you sound bad to them, they to you, or both? One direction points at one end's upload path. Both point at the middle.

Which calls. A date, a time, and the other party's number. Call history holds the record, and a case naming two real calls is diagnosable where "calls have been bad lately" is not.

Constant or time-correlated. Trouble at the same hour daily is congestion; constant trouble is a device, a cable, or a path.

Then say what you checked: wired or wireless, VPN on or off, and whether anything large was uploading. Choppy, robotic, or echoing calls maps symptoms to causes; one-way audio covers the case where they cannot hear you.

One last item, not about quality but usually discovered during it: your home extension's E911 address is registered per location and per number against a validated street address, and it does not follow a device that moves. If you have relocated since the extension was created, that record is wrong now.

Frequently asked questions

Why do my work calls sound bad at home? Almost always congestion on the upload path rather than insufficient bandwidth. A voice call needs about 100 kbps each way; a backup, a video call in another room, or a game update can starve it. Wi-Fi variability and a VPN detour are the other two common causes.

How much upload bandwidth does a VoIP call need? Roughly 87 kbps per concurrent call with the standard G.711 codec including overhead — plan 100 kbps in each direction, so two calls in one house is about 200 kbps. If a fast connection still delivers bad audio, the cause is jitter, loss, or latency, not capacity.

Does a VPN make work calls worse? Usually. It adds a hop, latency, and a queue tuned for data rather than audio, and a hosted phone system does not need it — phones connect outbound and require no inbound port forwarding. Ask for split tunneling that excludes voice, and check for personal VPN software too.

Is Wi-Fi good enough for VoIP calls? For occasional calls, yes. For heavy phone work, use Ethernet. Wi-Fi's issue is variability rather than speed: interference and roaming between access points produce jitter, which makes voice sound robotic. A live call cannot retransmit late audio the way a file transfer can.

What should I report when calls sound bad? Which direction the problem ran, two specific calls with date, time, and the other number, and whether it is constant or hits at the same hour daily. Add whether you were wired or wireless and whether a VPN was on. Those facts usually localize the fault at once.

If your remote staff report audio problems and nobody can tell whether it is the house, the headset, or the platform, send us two example calls with timestamps. We will trace what we see from our side and tell you where the rest lives.