VoIP Quality for Remote Teams: What IT Should Be Monitoring

The visibility problem

When everyone worked in the office, IT controlled the network end to end. Switches, routers, QoS policies, ISP uplinks. If call quality dropped, someone could walk to the network closet and start diagnosing.

Remote work changed that equation. Voice traffic now starts on a home network that IT has never seen, crosses a residential ISP that IT has no relationship with, traverses the public internet, and arrives at the VoIP provider. IT's visibility covers maybe the last hop. Everything before that is a black box.

This is not a theoretical problem. In most organizations with remote workers, the first indication of a voice quality issue is a complaint on Slack: "My calls sound terrible today." By the time someone looks into it, the problem may have resolved itself, leaving no data to analyze.

What changed with remote work

Office networks are purpose-built. Dedicated bandwidth, QoS configuration, wired connections, enterprise-grade access points. Home networks are not.

Shared bandwidth. A remote worker's video call competes with their kid's game download and their partner's streaming. A 100 Mbps residential connection has plenty of bandwidth, but when it gets saturated, everything degrades at once because there is no QoS to protect voice traffic.

Consumer-grade hardware. Home routers often have oversized buffers (bufferbloat), no QoS support, and firmware that rarely gets updated. The ISP-provided router/modem combo is usually the worst offender.

Variable ISP quality. Residential internet service has different SLAs than business service. Oversubscription ratios are higher. Maintenance windows are less predictable. And the "up to" speeds in the marketing materials have a lot of room between them and reality.

Wi-Fi everywhere. In the office, VoIP phones sit on wired connections. At home, almost everything is wireless. The laptop on the kitchen table connects over Wi-Fi to a router two rooms away, and nobody thinks about it until calls start breaking up.

The metrics that matter

If you are going to monitor VoIP quality for remote workers, focus on these four metrics. Everything else is either derived from these or secondary.

Packet loss

The single most impactful metric. Even 1% packet loss produces audible degradation. Measure it with UDP traffic that mimics voice packet patterns (small packets at regular intervals), not with ICMP ping, which often gets different treatment on the network.

Track both average loss and burst loss. A worker with 0.5% average loss spread evenly sounds fine. A worker with 0.5% average loss concentrated in 2-second bursts every few minutes sounds terrible.

Jitter

Variation in packet arrival times. Keep it under 30ms for acceptable quality. Jitter above 50ms means the connection is not suitable for voice without significant buffer compensation, which adds latency.

Home Wi-Fi and bufferbloat are the most common causes of high jitter on remote connections.

Latency

Round-trip time matters for conversational flow. Under 150ms one-way is fine. Between 150ms and 250ms, people start to notice delays and talk over each other. Above 250ms, natural conversation becomes difficult.

For most domestic remote workers, latency to the VoIP provider should be well under 100ms. If it is not, there is likely a routing issue.

MOS (Mean Opinion Score)

The composite metric that combines the above into a single quality score. Useful for dashboards and alerting, but always dig into the component metrics when investigating an issue.

What IT can actually do

You do not control the home network. That is the uncomfortable reality. But you are not completely helpless.

Establish a baseline for each worker. Run a VoIP quality test during onboarding or periodically. Know what each person's home connection looks like so you have something to compare against when problems arise.

Provide guidance on home network setup. Publish a simple guide: use the 5 GHz band, sit near the access point, use an Ethernet cable for your workstation if possible, check for bufferbloat. Most remote workers will follow straightforward advice if you give it to them.

Offer to ship Ethernet cables and USB adapters. A $15 USB-C to Ethernet adapter and a 10-foot cable solve half of all home VoIP quality issues. Many IT teams have found this to be the single highest-ROI investment for remote call quality.

Enable endpoint quality reporting in your VoIP platform. Most modern platforms (Teams, Zoom Phone, RingCentral, 8x8) collect call quality metrics from the client. Set up dashboards to spot workers who consistently report poor metrics.

Set up proactive monitoring. Rather than waiting for complaints, run periodic quality probes from remote locations to your VoIP infrastructure. This gives you trend data and lets you catch degradation before users notice.

Call quality is not the only per-worker record that goes stale, either — E911 dispatchable location for remote softphones needs the same periodic verification, or 911 calls route to the office address instead of the worker's home.

The provider blame game, remote edition

When an office worker has bad call quality, the ISP and VoIP provider point fingers at each other. When a remote worker has bad call quality, add the home ISP, the home router, and the Wi-Fi to the mix. Five potential culprits, none of whom want to own the problem.

The only way to cut through this is data. If you can show that a remote worker's jitter is 8ms at the Ethernet port but 45ms after the home router, the problem is clear. If latency spikes happen on the ISP's second hop, you have something concrete to take to the provider.

Without measurement data from the remote endpoint, every troubleshooting conversation is speculation. That is why VoIP Test focuses on testing from the user's actual location, on their actual connection, under their actual conditions. The data has to come from where the problem is.

For a systematic approach to finding where quality problems originate, see How to Tell Where the Problem Actually Is in our VoIP From the Ground Up series.