The short answer
Poor VoIP call quality (calls cutting in and out, scratchy or silent) usually comes from a problem between the handset and your provider: unstable Wi-Fi, congestion, jitter, packet loss, router settings or ageing handsets.
If your business hears calls cutting in and out, scratchy audio, silence, or customers saying “I can’t hear you”, the cause is usually somewhere between the handset and the VoIP provider. This guide is for owners and office managers who want to find the problem before they spend money on it.
By the end you will know how to tell a handset fault from a network fault, what to test first, and what to hand your provider so the fault gets fixed faster.
On this page
Why is my VoIP call quality poor?
Poor VoIP call quality usually means voice packets are being delayed, lost or sent through the wrong network path. Start by identifying the exact symptom, because choppy audio, dropped calls and one-way audio often have different causes.
VoIP turns speech into small data packets that travel across your local network and the internet. Unlike an email, those packets need to arrive quickly and in the right sequence; late or missing packets cannot simply be resent without creating more delay.
Microsoft’s VoIP troubleshooting guidance identifies available bandwidth, round-trip time, packet loss and jitter as key factors affecting call quality. In practical terms:
| What staff hear | Likely cause | First check |
|---|---|---|
| Voice sounds robotic, broken or choppy | Jitter, packet loss or congestion | Test during a busy period and check whether uploads or video are running |
| Call drops completely | Network interruption, firewall issue or phone losing registration | Check whether one handset or every handset is affected |
| One person cannot hear the other | Router, firewall, NAT or SIP ALG issue | Check router settings and ask the provider to review the audio path |
| Calls sound scratchy on one desk only | Faulty handset, headset, cable or local port | Test with another handset, headset, cable and switch port |
| Phones keep rebooting or unregistering | Power, network, firmware or device fault | Check power supply, Ethernet connection and device logs |
The first useful question is whether the issue affects one user, one handset, several users or the whole office. A single affected desk points towards the handset, headset, cable or switch port; several affected users at the same time point more towards the router, network or provider connection.
Are Wi-Fi handsets causing my VoIP calls to drop?
Wi-Fi can work for VoIP, but a cabled handset is usually easier to troubleshoot and less exposed to wireless congestion. If calls improve when the same user moves from Wi-Fi to Ethernet, the wireless network is a strong suspect.
Wi-Fi performance changes with distance from the access point, walls, interference, roaming between access points and the number of devices sharing the radio channel. A handset may show a strong signal while still experiencing delay or packet loss when the wireless network is busy.
For a small office, test one affected user with a cabled handset connected directly to the business network. Avoid running the phone through an untested wireless bridge or powerline adapter while diagnosing the problem.
If the phone is connected by Ethernet but still has poor audio, replace the patch cable and try another switch port. Also check whether the phone is receiving power reliably, especially if it uses Power over Ethernet and staff report that it keeps rebooting.
For a complete installation checklist, see how to connect VoIP handsets, the router and NBN.
Can uploads, video calls and backups affect VoIP call quality?
Yes. A voice call can sound poor when other traffic fills the connection, particularly upload traffic such as cloud backups, large file transfers, security-camera uploads and video meetings.
The problem is not always a lack of headline download speed. When the upload path becomes congested, voice packets may queue behind larger data transfers, arrive late or get discarded. Cisco explains that voice packets need to avoid excessive delay, packet loss and variable delay, known as jitter in its QoS troubleshooting guide.
Run a simple test during the time calls usually fail:
If call quality worsens only when the network is busy, ask your IT provider or VoIP provider to review Quality of Service settings. QoS can prioritise voice traffic, but it must be configured correctly across the relevant router, switches, access points and internet connection.
This article focuses on diagnosing call quality rather than choosing an internet service. For that separate decision, read why your business internet connection affects how your VoIP phones sound.
What are jitter and packet loss, and how do they affect calls?
Jitter is variation in the time voice packets take to arrive, while packet loss means some packets do not arrive at all. Jitter can make speech sound robotic or uneven, and packet loss can remove syllables, create gaps or make a conversation difficult to follow.
The RTP standard defines how real-time audio systems monitor packet sequence and interarrival jitter. Packet loss is generally a sign of persistent congestion, while jitter can reveal changing or temporary congestion.
This helps explain why a speed test can look acceptable while calls still sound poor. A speed test measures throughput at a point in time; it may not reveal short bursts of congestion, wireless interference or packet loss during the actual call.
Microsoft’s call-quality guidance uses jitter, packet loss and round-trip time to investigate poor audio. These measurements are useful reference points, but not every VoIP platform reports them in the same way.
Ask your provider for the call’s jitter, packet-loss and latency results in both directions. A one-sided result is important: it can show whether the problem is mainly affecting audio sent from your office or audio arriving at your office.
Why do I have VoIP one way audio?
VoIP one-way audio means one person can hear the conversation but the other person cannot. It is commonly associated with a blocked or misdirected media path involving the router, firewall, NAT or SIP ALG.
SIP is used to establish and manage the call, while the actual voice often travels through a separate media stream. That is why a call can ring and connect successfully even when the audio path is incomplete.
A router’s SIP ALG feature is intended to help SIP traffic pass through NAT, but incorrect implementations can alter signalling or media details. A SIP audio troubleshooting guide from an internet provider lists one-way audio, silence, gaps and garbled audio as symptoms that call for checks of the network path, RTP settings and router behaviour.
Do not change firewall or SIP settings at random. Ask the provider or network administrator to check:
If one-way audio appears only after a router replacement, firmware update or network change, tell the provider exactly when the change occurred. That timing can reduce the investigation substantially.
Can old handsets or headsets cause poor call quality?
Yes. A failing handset, headset, cable, power supply or switch port can create scratchy audio, low volume, intermittent silence or a phone that repeatedly reboots.
Hardware faults often affect one desk rather than the whole office. They may also follow the equipment: if the problem moves when you swap the handset or headset, the original device is the likely cause.
Use this isolation test:
Headsets used for high-call-volume roles need more than a comfortable fit. Microphone positioning, acoustic performance, compatibility and connection type all matter, so use this guide when checking what to look for in a business phone headset.
If only one device remains affected after these swaps, provide the model, firmware version, serial number and test results to the provider or installer. Avoid replacing every phone until the fault has been isolated.
What can I check before contacting my VoIP provider?
You can complete a useful first check by recording the symptom, affected equipment and timing before opening a support ticket. Good evidence is more valuable than a general report that “the phones are bad”.
Do not rely on a generic internet speed result alone. Ask for a VoIP-specific assessment or call-quality report that includes jitter, packet loss, latency, direction and timestamps.
What should I ask my VoIP provider about poor call quality?
Ask the provider to separate the phone, local network and service-side parts of the call. A useful support response should explain what was measured, where the fault appears to be and what test will confirm the fix.
Give the provider the exact date and time of failed calls, the affected extension or handset, the external number involved, whether the caller, recipient or both lost audio, and whether the call dropped or stayed connected. Add your router and handset models, any recent network or firmware changes, and the results from your cable, headset and Wi-Fi tests.
Then ask:
A provider may need to review call records or network data rather than troubleshoot by listening to a short test call. Direction-specific quality data is what separates a local device or network problem from a wider service issue.
How can I get a VoIP setup that sounds right?
Start with a cabled, correctly powered handset, a stable local network and a router configured for your provider’s requirements. Then test under normal office load and keep a record of any remaining faults instead of changing several settings at once.
For a small Australian office, the practical order is:
If your business needs a broader phone-system review, see business VoIP in Australia. The aim is simple: staff should be able to hear customers clearly without calls dropping out, cutting in and out or requiring repeated call-backs.
Frequently asked questions
Why do my VoIP calls keep dropping out?
Usually network trouble. Calls commonly drop because of network interruptions, congestion, packet loss, router or firewall problems, unstable Wi-Fi, or a phone losing registration. Check whether every handset is affected and record the exact time of each failed call.
Why can the customer hear me but I cannot hear them?
That is one-way audio. It is usually caused by a problem with the media path through the router, firewall, NAT or SIP ALG. Ask your provider to check inbound and outbound audio separately rather than treating it as a general handset fault.
Are cabled phones better than Wi-Fi for VoIP?
Generally, yes. Cabled phones are easier to stabilise and troubleshoot because they avoid wireless interference, roaming and shared Wi-Fi airtime. Wi-Fi can work, but it needs to be tested under the conditions where your office normally experiences problems.
What information should I give my VoIP provider?
The call details. Provide the date and time, affected extension, calling and called numbers, direction of the audio problem, symptom, handset type and any recent network changes. Include whether the issue affects one user or the whole office, plus any test results from a different handset, headset, cable or connection.
Get a VoIP setup that sounds right
See how business VoIP works in Australia and what to check before you choose.
