VoIP call quality problems small business owners face usually trace back to the network, not the phone system. Choppy audio, robotic voices, and dropped calls frustrate clients and disrupt your team. Most causes live inside your own office and are within reach to fix without an IT background.
This guide covers the four most common causes and the order you should check them. By the end, you will know what to test, what questions to ask your provider, and at least one thing you can adjust on your own network today.
What Jitter, Latency, and Packet Loss Actually Mean
Your voice call travels as small data packets sent across the internet. When those packets behave badly, your audio suffers. Three problems cause most of the trouble, and each sounds different on a call.
Latency is delay. Your voice leaves your phone, crosses the network, and arrives late. The other person hears a lag. Conversations start to overlap because both sides keep talking to fill the silence.
Jitter is uneven delivery. Packets should arrive at steady intervals. When they arrive in bursts or out of order, your phone has to guess how to reassemble them. VoIP codecs are designed to handle packets that each carry up to 200 ms of audio data (IETF RFC 3551). When jitter pushes packets outside that expected timing window, the receiver drops or scrambles them, and that is what you hear as choppy or robotic audio.
Packet loss is exactly what it sounds like: some packets never arrive. You hear gaps, clicks, or clipped syllables. Even a small amount of loss causes audible problems on a live call. The timestamp in a VoIP stream advances by 160 for every 160-period sampling block, whether that block is sent as a packet or discarded during silence (IETF RFC 3550). That steady clock means the receiver knows precisely when a packet is missing, even if it cannot reconstruct what was said.
These three problems can happen separately or together. Learning to tell them apart by ear helps you describe the symptom accurately when you call your provider, and it speeds up diagnosis considerably.
How to Run a VoIP Quality Test and Read the Results
Running a VoIP-specific test is different from a standard speed test. A regular speed test measures raw throughput. A VoIP test measures how your network handles real-time audio packets under simulated call conditions, which is what actually determines call quality.
Search for a free VoIP quality test tool and run it from the same device and network segment your phones use. Results from a laptop on Wi-Fi will not reflect what a wired desk phone experiences on your office network.
Key metrics to look for in your results:
- MOS (Mean Opinion Score): An overall grade for call quality on a scale of 1 to 5. A score of 4.0 or above is considered good and sounds natural to callers. Scores between 3.5 and 4.0 are acceptable but noticeable. Scores below 3.5 are poor, and callers will consistently complain. If your score is below 3.5, something specific needs to be fixed before you blame the phone system.
- Jitter: The lower this number, the more consistent your audio delivery. High jitter causes choppy, robotic sound.
- Packet loss: Even a trace amount causes audible gaps. Any meaningful loss makes calls unreliable.
- Latency: Lower round-trip time allows natural conversation without awkward pauses.
Run the test several times across the day. A single snapshot misses problems that only appear during peak business hours. Save your results as a screenshot before you call your provider. Concrete numbers give a technician something to investigate instead of a vague complaint about bad calls.
QoS Settings That Fix VoIP Call Quality Problems
Your router decides which data gets through first when your connection gets busy. Without rules, a large file download can crowd out a phone call mid-sentence. Quality of Service, or QoS, lets you tell the router to treat voice traffic as the highest priority.
Log into your router's admin panel. The address is usually printed on the router itself. Look for a section labeled QoS, Traffic Priority, or Bandwidth Control. Some routers hide it under Advanced Settings.
Once you find it, enable QoS and look for a way to prioritize by application or traffic type. Select VoIP, SIP, or your phone system's name if it appears. If you must prioritize by device, add the IP addresses of your desk phones or the computer running your softphone app.
- Set voice traffic to the highest priority tier.
- Set video streaming and file backups to a lower tier.
- Save and reboot the router.
Rerun your VoIP quality test after the reboot. If jitter and packet loss improve, QoS was the problem. If numbers stay poor, the issue likely sits upstream with your internet circuit, not inside your office. A common mistake is to enable QoS but leave voice traffic in the default tier, which does nothing. Confirm voice traffic is explicitly marked high priority, not just enabled in a general sense.
How Much Bandwidth Each Concurrent Call Actually Needs
Your internet plan's raw download speed is not what matters for VoIP. What matters is how many calls run at the same time, and whether your connection has enough headroom for voice alongside everything else running on the network.
The two most common codecs in business VoIP are G.711 and G.729. G.711 is uncompressed and uses significantly more bandwidth per call. G.729 compresses the audio and uses far less. Ask your VoIP provider which codec your system uses and how much bandwidth they recommend per concurrent call. With that number in hand, multiply by your maximum concurrent calls to find the minimum upload you need dedicated to voice.
Some codecs also vary their frame size based on detected voice activity in each slice, so actual bandwidth use shifts during a call rather than staying flat (IETF RFC 3551). That variability means your network needs breathing room beyond average load.
To size your connection, count your maximum concurrent calls, not your total extensions. A ten-person office where only four people are on calls at once needs capacity for four simultaneous streams. A safe rule is to leave at least half your upload bandwidth free for voice after accounting for everything else. Upload is usually the constraint, not download. If your math comes out close to your plan's limit, upgrade the plan or move VoIP to a separate dedicated circuit.
Wired Connections Beat Wi-Fi for Desk Phones
Wi-Fi introduces problems that a cable eliminates. Wireless signals compete with other devices, fluctuate with distance, and get interrupted by interference from neighboring networks. Each of those interruptions shows up in your call as a skip, a pop, or a moment of silence.
Desk phones should always connect by ethernet cable to your switch. This is not a preference; it is a requirement for reliable VoIP. A wired connection gives the phone a stable, dedicated path with consistent timing. VoIP audio is sensitive to timing gaps between packets, and Wi-Fi makes that unevenness worse because the signal itself varies second to second.
Softphones on laptops are a common weak point. A salesperson on a call walks away from the router, signal drops, and the customer hears it. If a softphone user has call quality complaints, the first question is always whether they are on Wi-Fi. Move them to a wired USB adapter or a wired headset with a physical ethernet connection.
Also check your switch ports. A port set to half-duplex instead of full-duplex causes collisions that look exactly like packet loss. Set every VoIP device port to full-duplex and confirm it negotiated correctly in the switch's status screen. This step is easy to miss and fixes a surprising number of complaints.
When to Escalate to Your ISP or VoIP Provider
You have fixed the switch ports, set QoS rules, and moved phones to wired connections. If calls still drop or sound bad, the problem is upstream. Before you call anyone, gather evidence so you are not just describing symptoms.
Run your VoIP quality test at three times: morning, midday, and late afternoon. Save each result. If packet loss and jitter spike at the same hours every day, that pattern points to your ISP's network under load. Call your ISP with those timestamps and test results in hand. Ask them to check for errors on your circuit and to confirm your connection type is not shared bandwidth with neighbors.
If your tests show clean numbers but calls still break up, the fault likely sits with your VoIP provider. Contact them with call logs, the affected phone numbers, and the times. Ask whether their upstream carrier had an outage or routing change during those periods.
If problems appear only on calls to one region or one carrier, your VoIP provider's interconnect is the likely cause, not your local setup or your ISP. The rule is simple: bad local tests point to a local or ISP problem. Clean local tests with bad calls point to a provider problem. Fix what your evidence points to, then retest before moving on.
To explore your phone system options, see our business VoIP phone systems and contact center solutions pages, or read about keeping your business phone number when you switch providers. If your internet connection is part of the problem, our business internet and SD-WAN page covers circuit options worth considering.
If you would like help working through this, book a free 30-minute call with Joshua. He can look at your setup and tell you exactly where the problem is before you spend money on the wrong fix.




