Switching to a cloud phone system is one of the smartest moves a growing Australian business can make — but it does come with one non-negotiable dependency: a reliable, well-configured internet connection. Unlike traditional copper landlines, a cloud or VoIP phone system sends your voice as data packets over the internet. That means the quality of every call your team makes or receives is directly tied to the quality of your connection. Get it right, and your phone system becomes a seamless business tool. Get it wrong, and you are dealing with dropped calls, robotic audio, and frustrated customers before you have even finished the morning coffee.
This guide breaks down exactly what your internet connection needs to handle — from raw bandwidth to latency, jitter, and network architecture — so you can make confident decisions before or after moving to a cloud business phone system.
Why Internet Quality Is the Foundation of VoIP Call Quality
Traditional phone systems transmitted voice over dedicated copper circuits. The signal had its own protected path from end to end, which is why those calls were remarkably stable even on a mediocre network. Cloud phone systems — also called VoIP or hosted PBX systems — work completely differently. Voice is captured at your handset or softphone, converted into small digital packets, transmitted across the public internet, and reassembled at the other end in real time.
That real-time requirement is what makes internet quality so critical. A slow file download just takes longer. A delayed or dropped voice packet cannot be replayed — it either arrives late and disrupts the conversation, or it disappears and creates an audible gap. This is why businesses moving to VoIP need to think about more than just download speed. Factors like upload speed, latency, jitter, and packet loss each play a distinct role in the experience your callers and your team will have.
If you are still building your understanding of how cloud telephony works at a fundamental level, the VoIP business guide from Pickle is a solid starting point before diving into the technical requirements below.
Upload Speed: The Metric Most Businesses Overlook
When most people talk about their internet speed, they mean download speed — how fast data comes to them. For general browsing, streaming, and file downloads, download speed is the dominant factor. For VoIP, upload speed matters just as much, and in many cases more.
Every active call consumes bandwidth in both directions simultaneously. Your voice travels upstream to the other party while their voice travels downstream to you. On a typical Australian NBN connection, download speeds are far higher than upload speeds — a 50/20 Mbps plan offers 50 Mbps down but only 20 Mbps up. For businesses running multiple concurrent calls, that asymmetry can become the bottleneck.
The amount of bandwidth each call requires depends on the audio codec your phone system uses. The G.711 codec delivers uncompressed, near-landline-quality audio and uses approximately 80–100 kbps in each direction per call. The G.729 codec applies compression to reduce that figure to around 24–32 kbps per call, which is useful where bandwidth is constrained, though there is a marginal reduction in audio richness. Most modern cloud phone systems support both, and some will automatically negotiate the best available codec based on network conditions.
Using G.711 as a conservative benchmark, here is how the numbers scale with concurrent calls:
- 5 concurrent calls: approximately 500 kbps upload and 500 kbps download in use at peak
- 10 concurrent calls: approximately 1 Mbps upload and 1 Mbps download at peak
- 20 concurrent calls: approximately 2 Mbps upload and 2 Mbps download at peak
Those figures look modest against modern NBN speeds, but there is an important caveat: those are raw voice figures only. Your connection is also handling email, file uploads to cloud storage, video conferencing, software updates, and anything else your team is doing at the same moment. A good rule of thumb is to calculate your peak concurrent call requirement, apply the codec bandwidth, and then plan for at least two to three times that figure to remain as headroom for everything else on the network.
Latency, Jitter, and Packet Loss: The Three Hidden Culprits
Bandwidth is the most visible metric, but three other factors have a greater practical impact on call quality than raw speed figures suggest. Understanding them helps you diagnose existing problems and design a network that avoids them from the start.
Latency
Latency is the time it takes for a data packet to travel from your device to the destination and back — measured in milliseconds. For VoIP, the relevant figure is one-way latency, and the threshold that telecommunications engineers generally consider acceptable is 150 ms or below. When one-way latency creeps above 200–300 ms, conversations start feeling strange. People begin talking over each other because the slight delay means each party cannot judge when the other has finished speaking. This is the same experience you have had on a poor international call — that awkward half-second lag that makes natural conversation nearly impossible.
Latency is influenced by physical distance to the VoIP provider's servers, the routing path your data takes across the internet, and the processing time introduced by each network device it passes through. Choosing a VoIP provider with Australian-based infrastructure and data centres significantly reduces baseline latency for Australian businesses, rather than routing calls through servers located overseas.
Jitter
Jitter describes the variation in packet arrival times. Even if average latency is acceptable, if some packets arrive in 20 ms and others in 80 ms, the voice stream becomes uneven and difficult to reconstruct cleanly. The result is choppy, clipped, or robotic-sounding audio — one of the most common complaints from businesses moving to VoIP on a poorly configured network.
Jitter buffers built into modern VoIP equipment and software help compensate by holding arriving packets briefly and releasing them at a consistent rate. However, a jitter buffer introduces a small additional delay, and when jitter is excessive — generally above 30 ms — even a well-configured buffer cannot fully compensate. The target for acceptable jitter is below 30 ms. Anything above that will typically produce noticeable audio degradation.
Jitter is almost always a symptom of network congestion. When your connection is under heavy load, packets get queued and released inconsistently. The fix is rarely a faster connection — it is usually better network management, which brings us to QoS.
Packet Loss
Packet loss is exactly what it sounds like: a percentage of the voice packets sent never reach their destination. Unlike file transfers, which can simply retransmit lost packets, real-time voice has no time for retransmission. Lost packets create audible gaps in speech, and at higher rates of loss, the audio becomes distorted and largely unintelligible.
For acceptable VoIP quality, packet loss should remain below 1%. At 2–3%, callers will notice. Above 5%, calls become practically unusable. Packet loss is usually caused by network congestion, faulty hardware (particularly aging routers or switches), or poor Wi-Fi signal strength when using softphones on wireless devices.
How Network Congestion Undermines Call Quality
Even a fast internet connection can deliver poor VoIP quality when the network is under heavy load. This is one of the most common issues businesses experience after setting up a cloud phone system — everything works perfectly during initial testing, but quality deteriorates noticeably during business hours when the team is active.
The cause is competition for the same internet pipe. Staff conducting video conferences, uploading large files to cloud storage, streaming training content, and browsing simultaneously all consume bandwidth and introduce congestion. Guest Wi-Fi networks that share the business internet connection compound the problem further. When the connection approaches saturation, all traffic — including voice — suffers from increased latency, jitter, and packet loss.
This is why many businesses find that the solution to call quality problems is not upgrading to a faster internet plan, but rather managing the traffic they already have more intelligently.
QoS: The Single Most Important Network Setting for VoIP
Quality of Service, universally abbreviated to QoS, is a feature available on business-grade routers and managed switches that allows you to assign priority levels to different types of network traffic. With QoS correctly configured, your router knows that voice packets must be delivered with minimal delay, and it will queue and transmit them ahead of lower-priority traffic like file downloads or general browsing.
The practical effect is significant. A network with QoS enabled can deliver excellent call quality even when the connection is running at 80–90% capacity, because voice packets jump the queue and are not delayed by the bulk data transfers happening simultaneously. Without QoS, all traffic is treated equally, and during congestion, voice packets wait in line alongside everything else — which is where choppy audio and latency problems emerge.
Most consumer-grade routers sold with home internet services either do not support QoS or implement it in a limited, poorly configurable way. Business-grade routers from manufacturers like Cisco, Ubiquiti, or Fortinet provide proper QoS controls that allow your network administrator or IT provider to define precise prioritisation rules for voice traffic. If your business is running a cloud phone system on a router that shipped with your NBN modem, QoS capability is the first thing worth assessing.
Internal Network Design: Beyond the Internet Connection
Many VoIP quality issues originate not on the external internet connection but on the internal network between devices and the router. Two areas deserve particular attention: VLAN segmentation and Wi-Fi quality.
A Voice VLAN is a logically separated network segment dedicated exclusively to voice traffic. By isolating phone system traffic from general data traffic at the switch level, you prevent non-voice devices from competing directly with your phones for internal network resources. VLAN configuration requires managed switches rather than the unmanaged switches commonly found in smaller offices, but the investment is modest and the reliability improvement for businesses with five or more concurrent calls is substantial.
For teams using softphones — VoIP applications installed on laptops or mobile devices rather than dedicated desk phones — Wi-Fi quality becomes part of the equation. A softphone user on a weak Wi-Fi signal will experience exactly the same packet loss and jitter problems as a poor external connection would cause, regardless of how good the internet plan is. Ensuring adequate Wi-Fi access point coverage, and ideally running softphone-heavy areas on dedicated access points or a separate SSID, removes this variable from the quality equation.
Business-Grade Internet Versus Standard NBN for VoIP
Whether a standard NBN plan is sufficient for your business phone system depends primarily on the number of concurrent calls you expect to run and the nature of your other internet usage. For a small team making a handful of calls at any one time, a well-configured standard NBN connection with proper QoS will typically deliver excellent call quality. As concurrent call volumes grow, the case for business-grade internet strengthens.
Business-grade internet services in Australia differ from residential and small business NBN plans in several important ways. Guaranteed upload speeds on business plans are not subject to the contention ratios that affect standard NBN connections — the bandwidth you pay for is the bandwidth you reliably receive, even during peak periods. Many business plans also offer Service Level Agreements that commit the provider to restoration timeframes in the event of an outage, which is directly relevant if your phone system is the primary way customers reach you. Static IP addresses, often available on business plans, simplify some VoIP configurations and are required by certain security and firewall setups.
For businesses running 10 or more concurrent calls, those with critical customer-facing phone requirements, or those operating across multiple sites, the additional cost of a business-grade internet service is almost always justified by the reliability improvement.
Understanding the full architecture of a hosted PBX versus a traditional phone system can also inform how you plan internet requirements across different locations or setups.
Signs Your Network Is Not Ready for VoIP
Before or after deploying a cloud phone system, the following symptoms indicate that your internet connection or network configuration needs attention.
Dropped calls that cannot be explained by poor mobile coverage are one of the clearest indicators. If calls on your cloud system terminate unexpectedly — particularly during periods of heavy internet usage — the connection is being disrupted in a way that causes the VoIP session to time out.
Audio delay or echo is typically a latency problem. If callers report hearing themselves slightly after they speak, or if conversations feel laggy and unnatural, one-way latency is almost certainly above acceptable thresholds.
Robotic or garbled audio that comes and goes, particularly during specific times of day, points strongly to jitter caused by network congestion. The timing pattern — worse at 10 am or 3 pm when the office is busiest — is itself diagnostic.
Calls that degrade specifically when other heavy internet activity is occurring confirm that QoS is absent or misconfigured. The fix here is not more bandwidth; it is proper traffic prioritisation.
One-sided audio, where one party can hear the other but not vice versa, is often a firewall or NAT configuration issue rather than a pure bandwidth problem, and is worth flagging with your VoIP provider's technical team specifically.
How to Assess Your Network Before Moving to a Cloud Phone System
A straightforward assessment process reduces the risk of discovering problems after you have already ported your business numbers and the team is live on the new system.
Start with a broadband speed test that measures both upload speed and latency — not just download. Services like Speedtest by Ookla or the Australian government's nbn broadband speed test provide this data. Run the test during peak business hours, not during a quiet period, to get a realistic picture of your available bandwidth under load. Note the upload speed specifically and compare it against your expected peak concurrent call requirement using the 100 kbps per call figure for G.711.
Calculate your expected concurrent calls realistically. For most businesses, not everyone calls simultaneously — a business with 20 staff might peak at 8–10 concurrent calls. Consider your busiest periods and build your capacity calculation around that figure, not the total headcount.
Audit your router and switch hardware. Check whether your router supports QoS configuration, and whether the switches in your network are managed (allowing VLAN configuration) or unmanaged. If your current equipment does not support QoS, budget for a hardware upgrade as part of the phone system migration.
If you are planning to run the phone system across multiple sites or integrate it with other cloud services, review our guide on how to set up a business phone system to ensure your network planning covers the full deployment picture.
Quick-Reference: VoIP Internet Requirements
The following thresholds represent the targets your network should meet for reliable, business-quality VoIP performance.
Upload speed should provide at least 100 kbps per concurrent call using G.711, with a minimum of two to three times that figure reserved as headroom for other business internet traffic. Latency should remain below 150 ms one-way between your site and your VoIP provider's infrastructure. Jitter should be below 30 ms under normal operating conditions. Packet loss should stay below 1% consistently. QoS should be enabled and configured at the router level to prioritise voice traffic. Business-grade internet is recommended for operations expecting more than 10 concurrent calls or with SLA requirements for uptime.
These figures are not aspirational targets — they are the practical floor for professional call quality. Exceeding them by a comfortable margin is always preferable to operating at the minimum.
Frequently Asked Questions
Q: How much internet speed does a VoIP business phone system need in Australia?
A: As a practical starting point, allow 100 kbps of upload and download bandwidth per concurrent call using a standard G.711 codec, then multiply by your expected peak concurrent call volume and add headroom for other internet usage. A business running 10 concurrent calls needs approximately 1 Mbps dedicated to voice, plus sufficient headroom for other traffic — so a 50/20 Mbps NBN plan would be more than adequate from a raw speed perspective, provided QoS is configured correctly.
Q: Is standard NBN fast enough for a business VoIP phone system?
A: For small to medium businesses with moderate concurrent call volumes, a standard NBN service is often sufficient provided the network is properly configured with QoS. The more important variable is upload speed and network management rather than raw download speed. However, businesses with high concurrent call volumes, critical uptime requirements, or multiple sites should consider a business-grade service with guaranteed upload speeds and an SLA.
Q: What causes robotic or choppy audio on a VoIP phone call?
A: Robotic or choppy audio is almost always caused by jitter — inconsistent packet arrival times — or elevated packet loss. Both are typically symptoms of network congestion rather than insufficient total bandwidth. Enabling QoS on your router to prioritise voice traffic is usually the most effective solution. If the problem persists after QoS configuration, examine whether there is a hardware issue with aging switches or a Wi-Fi signal problem for softphone users.
Q: Do I need a static IP address for a business VoIP phone system?
A: Not always, but it depends on your specific VoIP provider and configuration. Many cloud phone systems work reliably on dynamic IP addresses. However, a static IP simplifies firewall configuration, improves compatibility with certain SIP trunk setups, and eliminates any risk of the system needing to re-register after an IP address change. It is worth discussing with your provider before committing to a plan.
Q: What is the difference between latency and jitter, and which matters more for VoIP?
A: Latency is the consistent delay for packets to travel between two points — if your latency is 80 ms, packets reliably take 80 ms. Jitter is the variation in that delay — packets arriving sometimes at 20 ms and sometimes at 120 ms. Both matter for VoIP, but jitter tends to cause more noticeable audio problems because it disrupts the smooth flow of the voice stream. High but consistent latency makes conversations feel slightly delayed; high jitter makes audio sound choppy and robotic. In practice, jitter is the more common culprit in business VoIP quality complaints.
Ready to Move to a Cloud Phone System?
If your internet connection meets the requirements above — or you are ready to get the right advice before making changes — the team at Pickle can walk you through exactly what your business needs.
Pickle's cloud phone systems are designed and supported by people who understand Australian business internet, NBN realities, and the network configurations that make VoIP work reliably from day one. Whether you are setting up a new system or troubleshooting an existing one, we will give you straight answers.
Call us on 1300 688 588, email [email protected], or explore Pickle's business phone systems to find the right solution for your team.