Troubleshooting call quality on 3CX
Diagnose and fix poor 3CX call quality — jitter, latency, packet loss and the QoS settings that actually help.
Choppy, robotic, echoey or dropping calls are the fastest way to make a business sound unprofessional. The frustrating part is that the 3CX phone system itself is rarely the cause. Voice is just data, and when that data arrives late, out of order, or not at all, you hear it as broken audio. Fix the path the audio travels and the calls clean up.
This guide explains what actually causes poor call quality on 3CX, how to pin down where it is going wrong, and the handful of changes that make the biggest difference — in plain terms, without needing a network qualification.
What "bad call quality" actually means
Almost every quality complaint comes down to three measurable things happening to your voice packets between the handset and the far end:
Jitter
packets arriving at uneven intervals. You hear this as stuttering or robotic audio.
Latency (delay)
packets taking too long to arrive. Past about 150 milliseconds one way, people start talking over each other and it feels like a bad satellite call.
Packet loss
packets that never arrive at all. Even 1–2% loss causes audible gaps, clipped words and dropouts.
3CX shows call quality information in its call reports, often as a MOS (Mean Opinion Score) — a 1-to-5 rating where anything above about 4.0 is good. If your scores are low, the numbers point you straight at whether the problem is jitter, loss or delay.
Diagnose it in the right order
Work from the inside out. The pattern of when calls are bad tells you where to look.
Test extension to extension.
Call between two desk phones in the same office. If internal calls are crystal clear but external calls are rough, the problem is your internet connection or the trunk, not your LAN or 3CX.
Check wired vs Wi-Fi.
If a softphone or app user is bad on Wi-Fi but fine on a cabled connection, the Wi-Fi is the culprit. Voice and patchy Wi-Fi are a poor match.
Look at timing.
If calls only break up mid-morning or when the office is busy, you are almost certainly running out of internet bandwidth or fighting other traffic for it.
Read the 3CX call reports.
Low MOS with high jitter points at the network; consistent one-way trouble is usually a NAT or firewall issue — see our guide on fixing one-way audio.
The fixes that actually help
Once you know the symptom, these are the changes worth making, roughly in order of impact.
Put voice on a wire. Desk phones and computers running the 3CX app should be on cabled Ethernet wherever possible. It removes the single most common source of jitter and loss in a small office.
Make sure you have enough upload. Each concurrent call needs only around 100 kbps, but it needs that headroom consistently. A connection with weak or contended upload — common on basic plans — will sound fine on one call and fall apart on five. A business-grade service such as gigabit fibre or a properly sized business NBN plan gives voice the room it needs.
Prioritise voice with QoS. On your router and switches, enable Quality of Service (QoS) and tag voice traffic (DSCP EF / 46) so calls get priority over file downloads, backups and video. This is the single biggest win on a connection shared with everything else the business does.
Turn off SIP ALG. Many routers ship with SIP ALG switched on. It meddles with VoIP traffic and causes more problems than it solves. Disable it.
Check your codecs. G.711 gives the best audio and is the right default on a healthy connection. G.729 uses far less bandwidth at a small quality cost — useful on a constrained link or a busy branch. Make sure the codecs agreed at both ends overlap, especially across your SIP trunk.
When it is the internet, not the phones
Be honest with yourself here. If internal calls are perfect and only external calls suffer, no amount of 3CX tweaking will help — the bottleneck is the line into the building or the carrier. The clean fix is a better-quality connection, ideally one designed for voice with a service-level agreement behind it. If staying online through an outage also matters, pair it with internet failover so calls ride a second connection when the primary drops.
If you would rather not chase this down yourself, SIP Connect installs and supports 3CX across Melbourne and Australia every day. We can read your call reports, check your line quality and tune QoS for you — call 1300 747 266 or send a recent bill through our free bill review and we will look at the connection underneath your phones too.
What we see installing this in Melbourne
The single biggest pattern we see in Melbourne offices is a consumer-grade router left in place after an NBN install, with SIP ALG quietly on by default. The phones register, a one-on-one call sounds fine, then five concurrent calls hit and the audio falls apart. Swapping that router for something business-grade and turning ALG off usually does more than any 3CX setting change.
The other recurring issue is upload. Plenty of suburban sites are on FTTN or fixed wireless plans where the upload sits around 20 Mbps on a good day and collapses under a Teams meeting or a cloud backup running mid-morning. We always test on the actual office connection at a realistic time of day, not the showroom-floor speed test at 7am.
Where we add the most value is after cutover — sitting with reception for an hour on day one, reading the MOS scores from the first week of calls, and tuning QoS or the codec mix once we can see what the real traffic looks like.
Frequently asked questions
Why do my 3CX calls sound robotic or choppy?
That is almost always jitter or packet loss on the network — voice packets arriving unevenly or going missing. Move the device onto a wired connection, enable QoS to prioritise voice, and check your internet has enough spare upload bandwidth during busy periods.
How much internet speed do I need for good 3CX call quality?
Each simultaneous call uses only about 100 kbps in each direction, so raw speed matters less than consistency and low contention. A business-grade connection with steady upload and QoS will outperform a faster but congested consumer plan every time.
Will using Wi-Fi hurt call quality?
It can. Wi-Fi introduces jitter and packet loss that voice is sensitive to, especially in a busy office or at the edge of coverage. Use cabled Ethernet for desk phones and computer softphones where you can, and keep Wi-Fi for mobile staff who genuinely need it.
Is poor call quality a 3CX problem or an internet problem?
Usually the internet or the local network, not 3CX. The quickest test is an internal extension-to-extension call: if that is clear and only external calls are bad, the issue is your connection or the SIP trunk, and that is where the fix belongs.
Get a free bill analysis — and stop overpaying
Send us a recent phone or internet bill. We’ll show you exactly where the waste is — our bill reviews have identified savings of up to 65%.