Understanding VoIP Bandwidth Requirements for Your Business

Voice over Internet Protocol (VoIP) has transformed the way UK businesses communicate, replacing expensive traditional phone lines with flexible, feature-rich internet-based telephony. Yet one question continues to trip up IT managers and business owners alike: how much bandwidth does VoIP actually need?

The answer is rarely as simple as a single number. Your bandwidth requirements depend on the codec your system uses, how many concurrent calls your team makes, what other traffic shares your network, and how well your infrastructure is configured for real-time voice data. Get it wrong and you’ll face choppy audio, dropped calls, and frustrated customers. Get it right and VoIP delivers crystal-clear calls at a fraction of the cost of legacy ISDN or analogue lines.

In this comprehensive guide, we’ll walk through everything a UK business needs to know about VoIP bandwidth — from codec-level calculations and quality of service configuration to choosing the right broadband product and scaling your connection as you grow.

How Much Bandwidth Does VoIP Actually Need?

At its core, a VoIP call converts your voice into small digital packets and sends them across the internet. The amount of bandwidth each call consumes depends primarily on the audio codec being used — the algorithm that compresses and decompresses the voice signal.

A common misconception is that VoIP is bandwidth-hungry. In reality, a single VoIP call uses remarkably little data compared to video streaming or large file transfers. However, VoIP is extremely sensitive to network quality. A 4K video stream can buffer for a moment without anyone noticing; a VoIP call cannot. Every millisecond of delay, jitter, or packet loss translates directly into audible degradation.

The raw codec bitrate tells only part of the story. Each voice packet also carries overhead from network protocol headers — IP, UDP, and RTP headers add approximately 40 bytes to every packet. When you factor in this overhead, the actual bandwidth consumed per call is significantly higher than the codec’s nominal bitrate.

Codec Bandwidth Requirements Explained

Different codecs strike different balances between audio quality and bandwidth consumption. Here are the three codecs you’re most likely to encounter in a modern UK business VoIP deployment:

G.711 – The Gold Standard for Quality

G.711 is the oldest and most widely supported VoIP codec. It delivers toll-quality audio — essentially indistinguishable from a traditional landline call — but at the highest bandwidth cost. G.711 uses a raw bitrate of 64 Kbps in each direction. Once you add IP, UDP, and RTP headers (with a typical 20 ms packet interval), the total bandwidth per call rises to approximately 87–100 Kbps per direction, or roughly 200 Kbps symmetrical for a single call.

G.729 – The Bandwidth Saver

G.729 compresses audio far more aggressively, using just 8 Kbps of raw codec bitrate. With protocol overhead, this translates to roughly 31–40 Kbps per direction. The trade-off is a slight reduction in audio fidelity — perfectly acceptable for business calls, but you may notice the difference on music-on-hold or conference calls with many participants. G.729 requires a licence fee, though many hosted VoIP providers include this in their per-seat pricing.

Opus – The Modern All-Rounder

Opus is a newer, open-source codec increasingly used by platforms such as Microsoft Teams, Zoom, and modern SIP providers. It’s adaptive, meaning it can dynamically adjust its bitrate from as low as 6 Kbps to over 500 Kbps depending on network conditions. For typical voice calls, Opus operates at around 16–40 Kbps per direction, delivering excellent quality with efficient bandwidth usage.

Calculating Bandwidth for Your Office

Knowing the per-call requirement is only the starting point. To calculate your total VoIP bandwidth needs, you need to estimate your peak concurrent calls — the maximum number of calls happening at the same time during your busiest period.

Here’s a straightforward formula:

Required VoIP Bandwidth = Peak Concurrent Calls × Bandwidth Per Call × 2 (upload + download)

For example, a 50-person office where up to 20 people might be on the phone simultaneously using G.711:

20 calls × 100 Kbps × 2 = 4,000 Kbps (4 Mbps)

That 4 Mbps is purely for voice traffic. You must add bandwidth for all other business activities — email, web browsing, cloud applications, file syncing, and video conferencing. A sensible rule of thumb is to reserve at least 30% additional headroom above your calculated VoIP requirement to ensure quality remains consistent even during peak usage.

Concurrent Call Capacity by Connection Speed

The following table illustrates how many simultaneous G.711 calls different connection speeds can support, assuming dedicated VoIP bandwidth with appropriate QoS in place:

Quality of Service (QoS) Configuration

Raw bandwidth alone does not guarantee good VoIP quality. Without Quality of Service (QoS) configuration, your VoIP packets compete equally with every other type of traffic on your network. A large file upload or a Windows update downloading in the background can cause voice packets to queue, arrive late, or be dropped entirely.

QoS tells your network equipment to prioritise VoIP traffic above all other data. This is achieved through several mechanisms:

DSCP Marking

Differentiated Services Code Point (DSCP) marking tags VoIP packets with a priority flag (typically EF – Expedited Forwarding, DSCP value 46). Your router and switches then use these markings to place voice traffic in a high-priority queue, ensuring it’s transmitted first even when the network is congested.

Traffic Shaping and Policing

Traffic shaping limits the rate at which non-critical traffic can consume bandwidth, reserving a guaranteed portion for VoIP. For instance, on a 100 Mbps connection, you might reserve 20 Mbps exclusively for voice, ensuring that even if someone saturates the remaining 80 Mbps with downloads, your calls remain unaffected.

Bandwidth Reservation

Many business-grade routers allow you to create explicit bandwidth reservations for specific traffic classes. This guarantees a minimum allocation for VoIP regardless of what else is happening on the network. We recommend reserving bandwidth equivalent to your peak concurrent call estimate plus 20% overhead.

VLAN Separation for Voice Traffic

One of the most effective steps you can take to improve VoIP quality is to place all voice devices on a separate Virtual LAN (VLAN). This creates a logically isolated network segment for your phones and softphones, separating voice traffic from general data traffic at Layer 2.

The benefits are substantial:

• Reduced broadcast traffic — Data broadcasts from PCs, printers, and other devices don’t flood your voice network.
• Simplified QoS — You can apply QoS policies to the entire Voice VLAN rather than configuring rules per device.
• Enhanced security — Isolating voice traffic protects against eavesdropping and reduces the attack surface.
• Easier troubleshooting — When voice and data are separated, identifying the source of quality issues becomes far more straightforward.

Most managed switches support VLANs, and virtually all business-grade IP phones support VLAN tagging (802.1Q). If your current switches are unmanaged, upgrading to managed switches is one of the highest-value investments you can make for VoIP quality.

Understanding Jitter and Latency Thresholds

Two network metrics matter far more to VoIP quality than raw bandwidth: latency and jitter.

Latency (Delay)

Latency is the time it takes for a voice packet to travel from sender to receiver. In a phone conversation, high latency creates an awkward delay — you finish speaking and wait noticeably before the other party responds. The ITU-T G.114 recommendation sets the following thresholds:

For UK businesses calling within the UK, latency should comfortably sit below 50 ms on a quality connection. International calls naturally add latency due to physical distance, but a well-routed connection to Europe should still remain under 100 ms.

Jitter (Variation in Delay)

Jitter is the variation in latency between successive packets. Even if your average latency is low, high jitter means some packets arrive much later than others, causing gaps and distortion in the audio. VoIP phones use a jitter buffer to smooth out these variations, but the buffer can only compensate so much before it starts adding delay of its own.

Target jitter below 30 ms for reliable VoIP. Below 15 ms is ideal. If your jitter regularly exceeds 50 ms, you’ll experience audible quality degradation regardless of how much bandwidth you have.

Packet Loss

Packet loss occurs when voice packets fail to reach their destination entirely. VoIP is remarkably intolerant of packet loss — even 1% packet loss can cause noticeable audio artefacts, and anything above 2–3% typically renders a call unusable. Unlike web browsing or file downloads, lost VoIP packets cannot be retransmitted because the conversation has already moved on.

UK Broadband Options for VoIP

The UK broadband market offers several connection types, each with different characteristics for VoIP performance. Choosing the right product is critical for voice quality.

Testing Your Connection Before Deployment

Before deploying VoIP across your business, it’s essential to test your existing connection to confirm it can support the number of concurrent calls you need. A standard speed test alone is not sufficient — you need to measure the metrics that actually affect voice quality.

What to Test

• Bandwidth (upload and download) — Confirm your actual speeds match your contracted speeds, paying particular attention to upload.
• Latency — Measure round-trip time to your VoIP provider’s servers, not just to a generic test server. Ask your provider for their SIP server IP addresses.
• Jitter — Run tests over a sustained period (at least 10 minutes) during your busiest hours. Short tests can miss intermittent jitter spikes.
• Packet loss — Even brief periods of packet loss above 1% will cause audible issues. Test during peak business hours when your network is busiest.

Recommended Testing Tools

Several free and paid tools can help you assess your connection’s VoIP readiness:

• VoIP-specific speed tests — Services such as the Spearline network test or the 8x8 VoIP test simulate actual VoIP traffic and report a Mean Opinion Score (MOS).
• PingPlotter or WinMTR — These trace-route tools show latency and packet loss at every hop between your office and your VoIP provider, helping identify exactly where problems occur.
• iPerf — For more technical teams, iPerf can generate sustained UDP traffic that mimics VoIP patterns, giving you precise bandwidth and jitter measurements.
• Your VoIP provider’s pre-qualification tool — Most reputable UK VoIP providers offer a network assessment as part of their onboarding process. Take advantage of this — it’s in everyone’s interest for the deployment to succeed.

Monitoring Tools for Ongoing Quality

Testing before deployment is essential, but ongoing monitoring is equally important. Network conditions change — your ISP may experience congestion, new devices may join your network, or a misconfigured backup job may saturate your upload bandwidth overnight and into the morning.

Network Monitoring Solutions

Invest in monitoring tools that provide continuous visibility into your network’s VoIP performance:

• PRTG Network Monitor — Offers pre-built VoIP sensors that track jitter, latency, packet loss, and MOS scores in real time. The free tier covers up to 100 sensors, which is sufficient for most small businesses.
• Observium or LibreNMS — Open-source network monitoring platforms that can track bandwidth utilisation, interface errors, and QoS queue statistics across your switches and routers.
• VoIP provider dashboards — Most hosted VoIP platforms include call quality analytics showing per-call MOS scores, jitter, and packet loss. Review these regularly — they’re your best source of truth for end-to-end voice quality.
• SolarWinds VoIP & Network Quality Manager — For larger deployments, this provides deep packet inspection of SIP and RTP traffic, correlating network metrics with call quality in real time.

Key Metrics to Monitor

Set up automated alerts so you’re notified when any metric breaches its threshold. It’s far better to catch a developing issue before your team starts complaining about call quality than to investigate reactively.

Scaling Bandwidth as Your Business Grows

Your bandwidth requirements today won’t be your requirements in two years’ time. As your business grows, so does your demand for concurrent calls, cloud applications, and data transfer. Planning for scalability from the outset saves disruptive and expensive mid-contract upgrades.

Planning for Growth

Consider these factors when sizing your initial connection:

• Headcount projections — If you plan to hire 20 additional staff over the next two years, factor their VoIP and data bandwidth needs into your current procurement.
• Unified Communications adoption — If you’re likely to add video conferencing, screen sharing, or collaboration tools, these will significantly increase bandwidth demands beyond voice alone.
• Cloud migration — Moving from on-premises servers to cloud-hosted applications (Microsoft 365, Google Workspace, cloud ERP) adds sustained bandwidth consumption.
• Multi-site connectivity — If you’re opening additional offices or supporting a growing remote workforce, consider SD-WAN solutions that can intelligently distribute VoIP traffic across multiple connections.

Connection Upgrade Paths in the UK

Understanding the upgrade timeline for different connection types helps you plan ahead:

• SOGEA to FTTP — If you’re currently on SOGEA and FTTP becomes available, the upgrade is straightforward and typically takes 1–2 weeks. Monitor Openreach’s rollout plans for your postcode.
• FTTP speed upgrades — Most FTTP providers allow in-contract speed upgrades (e.g., 100 Mbps to 500 Mbps) with minimal lead time, often activated within 24 hours.
• Leased line provisioning — New leased line installations typically take 45–90 working days. If you anticipate needing a leased line within the next year, start the procurement process now.
• Secondary connections — Adding a second broadband connection for redundancy or additional capacity can be done relatively quickly. Combined with SD-WAN, two FTTP connections can provide both the bandwidth and resilience of a leased line at a lower cost.

Putting It All Together: A Practical Example

Let’s walk through a real-world scenario for a typical UK business:

Company: A 75-person professional services firm in Manchester
Peak concurrent calls: 25 (estimated from call logs)
Codec: G.711 (provider default)
Other traffic: Microsoft 365, cloud CRM, general web browsing

Step 1: Calculate VoIP Bandwidth

25 calls × 100 Kbps × 2 directions = 5 Mbps for VoIP

Step 2: Estimate Total Bandwidth

General business use for 75 users: approximately 50–80 Mbps during peak hours. Adding VoIP: 55–85 Mbps total. With 30% headroom: 72–110 Mbps.

Step 3: Choose Connection

A 150 Mbps symmetrical FTTP business connection at approximately £45–£55/month provides ample bandwidth with room to grow. A 4G/5G backup connection at £35/month provides resilience.

Step 4: Configure Network

• Create a Voice VLAN (VLAN 100) for all IP phones
• Configure DSCP EF marking for all traffic on VLAN 100
• Set up QoS on the router to prioritise marked traffic
• Reserve 10 Mbps guaranteed bandwidth for voice (double the calculated need for headroom)

Step 5: Test and Monitor

Run a 3-day VoIP quality test before go-live. Deploy PRTG with VoIP sensors for ongoing monitoring. Set alerts for jitter >20 ms, packet loss >0.5%, or bandwidth utilisation >70%.

Common VoIP Bandwidth Mistakes to Avoid

In our experience working with UK businesses, these are the most frequent mistakes we encounter:

• Ignoring upload speed — Most consumer and many business broadband packages have asymmetric speeds. VoIP needs bandwidth in both directions equally. If your download is 80 Mbps but your upload is only 10 Mbps, you’re limited by that 10 Mbps upload.
• No QoS configuration — Simply having enough bandwidth isn’t sufficient. Without QoS, a single large file upload can starve your VoIP of bandwidth for its duration. This is the number one cause of intermittent call quality issues.
• Forgetting about overhead — Using the codec bitrate (e.g., 64 Kbps for G.711) rather than the actual per-call bandwidth (100 Kbps including headers) leads to under-provisioning.
• Testing at the wrong time — Network tests run outside business hours give a misleadingly positive picture. Always test during your busiest periods.
• Single connection, no failover — When your internet goes down, so do all your phones. A £35/month 4G backup connection is cheap insurance against losing all inbound calls.
• Flat network architecture — Running VoIP and data on the same VLAN with unmanaged switches is a recipe for inconsistent quality. Invest in managed switches and VLAN separation.

The PSTN Switch-Off and Why This Matters Now

The UK’s traditional Public Switched Telephone Network (PSTN) is being retired by Openreach, with the full switch-off scheduled for completion by January 2027. Every UK business will need to migrate to VoIP — there is no alternative. ISDN lines, analogue phone lines, and even alarm systems that rely on the copper network will all need to transition to IP-based alternatives.

This isn’t a distant future concern. Openreach has already stopped selling new ISDN and analogue lines in many exchange areas, and the migration programme is well underway. If you haven’t already assessed your bandwidth readiness for VoIP, now is the time.

Summary

VoIP bandwidth planning is not simply a matter of buying the fastest broadband package available. It requires understanding your codec requirements, calculating concurrent call capacity, configuring QoS and VLAN separation, selecting the appropriate UK broadband product, and implementing ongoing monitoring to catch issues before they affect your team.

The good news is that VoIP is remarkably bandwidth-efficient. Even a modest FTTP connection can comfortably support dozens of concurrent calls alongside normal business traffic, provided your network is correctly configured. The key is preparation — understanding your requirements, testing thoroughly before deployment, and monitoring continuously after go-live.

With the PSTN switch-off approaching, every UK business needs to ensure their network infrastructure is ready for VoIP. Start with the calculations and testing outlined in this guide, and if you need expert assistance, CloudSwitched is here to help you make the transition smoothly and confidently.

CloudSwitched

London-based managed IT services provider offering support, cloud solutions and cybersecurity for SMEs.