How to Ensure Crystal-Clear VoIP Call Quality in Your Office

If your office phone system sounds like a conversation through a tin can — choppy audio, echoing voices, words dropping mid-sentence — the problem almost certainly is not your VoIP provider. It is your network. Voice over IP transforms analogue voice signals into digital packets that travel across your data network alongside emails, file downloads, and video streams. When that network is not properly configured, voice quality suffers dramatically.

For UK businesses that have migrated from traditional landlines to VoIP (and with the PSTN switch-off arriving in 2027, that is nearly everyone), network optimisation is the single most important factor in call quality. A poorly optimised network will make even the most expensive hosted telephony platform sound dreadful, while a well-tuned network can deliver call quality that rivals — or surpasses — traditional ISDN lines.

This guide covers everything you need to know about ensuring crystal-clear VoIP call quality in your office, from understanding the technical fundamentals to practical configuration steps your IT team can implement today.

Understanding the Three Enemies of VoIP Call Quality

Before diving into solutions, you need to understand the three network metrics that directly determine whether your VoIP calls sound professional or painful. These are latency, jitter, and packet loss — and each one affects your calls in a different way.

Latency (Delay)

Latency is the time it takes for a voice packet to travel from your phone to the recipient. Think of it as the gap between when you speak and when the other person hears you. Low latency means natural, real-time conversation. High latency creates that awkward satellite-phone effect where both parties talk over each other because of the delay.

The ITU-T G.114 standard recommends a maximum one-way latency of 150 milliseconds for acceptable voice quality. Anything above 200ms becomes noticeably disruptive, and above 300ms the call is essentially unusable for normal conversation.

Jitter (Variation in Delay)

Jitter measures the inconsistency in packet arrival times. Even if your average latency is low, high jitter means packets arrive at irregular intervals — some early, some late, some out of order. Your VoIP system uses a jitter buffer to reorder these packets, but if jitter exceeds the buffer’s capacity, the result is choppy, robotic-sounding audio or gaps in the conversation.

For business VoIP, jitter should ideally stay below 15 milliseconds. Most jitter buffers can compensate for up to 30ms, but anything beyond that will produce audible artefacts. The primary causes of jitter in office networks are network congestion, poorly configured QoS, and overloaded switches or access points.

Packet Loss

Packet loss occurs when voice data packets fail to reach their destination entirely. Unlike web browsing or email — where lost packets are simply retransmitted — VoIP operates in real time. There is no opportunity to resend a lost voice packet without creating unacceptable delay. Even 1% packet loss can cause noticeable audio degradation, and anything above 2–3% makes calls sound broken and unintelligible.

Metric	Excellent	Acceptable	Poor	Unusable
Latency (one-way)	< 80ms	80–150ms	150–300ms	> 300ms
Jitter	< 15ms	15–30ms	30–50ms	> 50ms
Packet loss	< 0.1%	0.1–1%	1–3%	> 3%
MOS score	4.0–4.5	3.5–4.0	3.0–3.5	< 3.0

Bandwidth Requirements for Crystal-Clear Calls

One of the most common misconceptions about VoIP is that it requires enormous amounts of bandwidth. In reality, a single VoIP call uses relatively little bandwidth — typically between 30 and 100 Kbps depending on the codec. The challenge is not total bandwidth but consistent, guaranteed bandwidth that is protected from contention with other network traffic.

Here is what each common VoIP codec requires per concurrent call, including protocol overhead:

For a typical UK office with 25 employees, you should plan for a minimum of 10–15 concurrent calls at peak times. Using G.711 (the most common codec for office VoIP), that translates to approximately 1.3 Mbps of dedicated upstream and downstream bandwidth for voice alone. While this sounds trivial on a 100 Mbps leased line, problems arise when that bandwidth is not protected from competing traffic.

As a rule of thumb, never allocate more than 75% of your total available bandwidth to all traffic combined, and reserve at least 20% of your total bandwidth exclusively for voice. If your internet connection regularly exceeds 80% utilisation, VoIP quality will suffer regardless of any other optimisation you apply.

QoS and DSCP Configuration: Prioritising Voice Traffic

Quality of Service (QoS) is the single most impactful configuration change you can make to improve VoIP call quality. QoS tells your network equipment — routers, switches, and firewalls — to prioritise voice packets over other types of traffic. Without QoS, a large file download or a Windows update can consume all available bandwidth and starve your phone calls of the resources they need.

The mechanism behind QoS is called DSCP (Differentiated Services Code Point) marking. Each network packet carries a small header field that indicates its priority level. Voice packets are typically marked with DSCP value EF (Expedited Forwarding, decimal 46), which tells every piece of network equipment along the path to treat them with the highest priority.

Traffic Type	DSCP Value	DSCP Name	Priority Level	Bandwidth Allocation
VoIP media (voice)	46	EF	Highest	Strict priority queue
VoIP signalling (SIP)	24	CS3	High	10–15% guaranteed
Video conferencing	34	AF41	Medium-high	20–30% guaranteed
Business applications	18	AF21	Medium	20–30% guaranteed
Email and web browsing	0	BE (Best Effort)	Standard	Remaining bandwidth
Bulk downloads / backups	10	AF11	Low	Scavenger class

VLAN Separation: Isolating Voice from Data

Virtual LAN (VLAN) separation is the practice of creating a dedicated, logically isolated network segment for your VoIP phones. Instead of sharing the same network as your computers, printers, and IoT devices, your phones operate on their own VLAN with its own subnet, DHCP scope, and QoS policies.

This is not merely a best practice — it is effectively a requirement for any office with more than five VoIP handsets. Without VLAN separation, broadcast traffic from computers, ARP requests, and network scans all compete with voice packets. A single misbehaving device can flood the network and destroy call quality for everyone.

Codec Selection: Balancing Quality and Bandwidth

A codec (coder-decoder) determines how your voice is digitised, compressed, and transmitted across the network. The codec you choose directly impacts call quality, bandwidth consumption, and resilience to packet loss. Most modern VoIP platforms support multiple codecs and can negotiate the best option automatically, but understanding your choices helps you make informed decisions.

Codec	Bandwidth (with overhead)	MOS Score	Audio Quality	Best Use Case
G.711 (a-law/μ-law)	87 Kbps	4.1	Toll quality	Office LAN with ample bandwidth
G.722	80 Kbps	4.5	HD wideband	Premium office calls, conference rooms
G.729	32 Kbps	3.9	Good (compressed)	Limited bandwidth or WAN links
Opus	36–510 Kbps	4.0–4.5	Excellent (adaptive)	WebRTC, softphones, variable networks
iLBC	28 Kbps	3.7	Acceptable	High packet loss environments

For most UK office environments with a decent leased line or FTTP connection, G.722 is the recommended choice. It delivers noticeably richer, clearer audio than G.711 at almost the same bandwidth cost, and most modern IP handsets and softphones support it natively. If bandwidth is constrained — for example, over a 4G/5G backup connection — G.729 provides acceptable quality at a fraction of the bandwidth.

Router, Switch, and Wi-Fi Requirements

Your networking hardware is the foundation upon which VoIP quality is built. Consumer-grade equipment simply cannot provide the features needed for reliable voice communications. Here is what you need at each layer of your network infrastructure.

Router / Firewall

Your edge router or firewall must support SIP ALG (Application Layer Gateway) — though ironically, it often needs to be disabled, as many implementations are buggy and cause more problems than they solve. More importantly, it must support proper QoS with DSCP marking, traffic shaping, and bandwidth management. Business-grade options from vendors like Fortinet, SonicWall, Cisco Meraki, or Draytek are essential. Expect to budget £300–£1,500 depending on your office size and throughput requirements.

Managed Switches

Unmanaged switches have no concept of VoIP traffic prioritisation. You need managed or smart-managed PoE+ switches that support 802.1Q VLAN tagging, LLDP-MED (Link Layer Discovery Protocol for Media Endpoint Devices), and QoS with at least four priority queues. PoE (Power over Ethernet) is also critical — it eliminates the need for separate power adapters on every handset and enables centralised power management. Budget £200–£800 per 24-port PoE+ managed switch.

Wi-Fi Access Points

If your office uses wireless handsets or softphones on laptops, your Wi-Fi infrastructure needs particular attention. Voice over Wi-Fi is inherently more challenging than wired VoIP due to the shared, half-duplex nature of wireless communication. You need access points that support WMM (Wi-Fi Multimedia) with automatic voice traffic prioritisation, band steering to push capable devices to 5 GHz, fast roaming (802.11r/k/v) for seamless handoff between access points, and adequate channel planning to minimise co-channel interference.

Network Readiness Scorecard

Before deploying or troubleshooting VoIP, assess your network against these key readiness criteria. Each area should score above 80% for reliable, professional-grade voice quality.

Network Assessment: Testing Before You Deploy

A thorough network assessment before deploying or upgrading VoIP is not optional — it is the difference between a smooth rollout and weeks of frustrating troubleshooting. At Cloudswitched, we perform comprehensive network assessments for every VoIP deployment, and the number of pre-existing issues we uncover is consistently surprising even to experienced IT managers.

A proper VoIP network assessment should cover the following areas in detail:

1. Bandwidth utilisation audit — monitor your existing bandwidth usage over at least 5 business days to identify peak utilisation patterns and contention points
2. Latency and jitter measurement — test to your VoIP provider’s data centres specifically, not just to generic internet hosts like Google DNS
3. Packet loss analysis — continuous measurement over several days, as packet loss can be intermittent and only appear during peak hours
4. Switch and cabling audit — verify all cabling is Cat5e or better, all switch ports negotiate at Gigabit, and no daisy-chained unmanaged switches lurk under desks
5. Wi-Fi site survey — measure signal strength, noise floor, channel utilisation, and interference at every potential wireless VoIP user location
6. Firewall and NAT traversal testing — ensure SIP and RTP traffic can traverse your firewall without being mangled or blocked
7. PoE budget verification — confirm your switches can deliver sufficient power to all connected handsets simultaneously without exceeding budget

Monitoring Tools: Keeping Quality Consistent

Deploying VoIP is not a one-time project — it requires ongoing monitoring to catch degradation before your staff or customers notice it. Network conditions change constantly as new devices are added, bandwidth usage patterns shift, and ISP performance fluctuates.

Essential monitoring tools and approaches for UK businesses include:

• PRTG Network Monitor — excellent for monitoring bandwidth, QoS queue performance, and VoIP-specific metrics like MOS scores via built-in sensors
• PingPlotter / PingPlotter Cloud — provides continuous, visual latency and packet loss tracking to specific destinations, invaluable for proving ISP issues to your provider
• VoIP provider dashboards — most hosted VoIP platforms (3CX, RingCentral, 8x8, Gamma Horizon) include call quality analytics and per-call MOS scoring
• SNMP monitoring — configure your switches and routers to report interface utilisation, error rates, and QoS queue drops via SNMP to a centralised monitoring platform
• Wireshark — the go-to tool for deep packet inspection when troubleshooting specific call quality issues; its VoIP analysis module can decode SIP signalling and analyse RTP streams in granular detail

Common VoIP Problems and How to Fix Them

Even with careful planning, VoIP issues can arise. The good news is that most problems follow predictable patterns and have well-established solutions. Here are the issues we encounter most frequently across our client base at Cloudswitched, along with proven fixes for each one.

Problem	Symptoms	Likely Cause	Fix
Choppy / robotic audio	Words break up, metallic sound	High jitter or packet loss on LAN	Enable QoS, check for duplex mismatches, replace failing cables
One-way audio	Caller or receiver cannot hear the other party	NAT/firewall blocking RTP ports	Open UDP port range for RTP (typically 10000–20000), disable SIP ALG
Echo on calls	Speaker hears own voice with delay	Acoustic feedback or impedance mismatch	Replace handset, adjust volume levels, check for analogue gateway issues
Dropped calls	Calls disconnect after 30–60 seconds	SIP session timeout, firewall closing UDP sessions	Increase firewall UDP timeout to 300+ seconds, enable SIP keep-alives
Peak-hour degradation	Quality degrades 9–11am and 2–4pm	Bandwidth saturation from data traffic	Implement QoS traffic shaping, upgrade bandwidth, or limit bulk transfers
Static / crackling	Persistent background noise on line	Faulty Ethernet cable or PoE issue	Replace patch cable, test different switch port, check PoE power budget
Delayed audio (latency)	Noticeable gap before other party responds	Geographic distance to provider or ISP congestion	Choose VoIP provider with UK data centres, switch ISP, or enable SD-WAN
Registration failures	Phones show “offline” or “no service”	DNS resolution failure or blocked SIP ports	Verify DNS, ensure UDP/TCP 5060 and TLS 5061 are open, check VLAN routing

Building a VoIP-Ready Network: A Practical Checklist

To pull everything together, here is a concise checklist for ensuring your office network is optimised for crystal-clear VoIP. Whether you are deploying a new system or troubleshooting an existing one, work through each item methodically.

1. Verify your internet connection — ensure you have a business-grade circuit with guaranteed bandwidth, low latency to your VoIP provider, and an SLA for uptime and fault resolution
2. Deploy managed PoE+ switches — replace any unmanaged or consumer-grade switches with managed models supporting 802.1Q, QoS, and LLDP-MED
3. Configure voice VLANs — create a dedicated VLAN for voice traffic, completely separate from your data, guest, and IoT networks
4. Implement QoS end-to-end — mark voice packets as DSCP EF (46) at the phone, honour markings on every switch and router, and configure strict priority queuing
5. Audit your cabling — ensure all cabling is Cat5e or Cat6, properly terminated, and tested with a cable certifier. Replace any cables showing CRC errors
6. Configure your firewall — open required SIP and RTP ports, set UDP session timeouts to 300+ seconds, and disable SIP ALG unless specifically required by your provider
7. Plan your Wi-Fi — if using wireless VoIP, deploy business-class access points with WMM, fast roaming, and adequate coverage density throughout the office
8. Select appropriate codecs — use G.722 for wideband quality on your LAN and configure G.729 as a fallback for constrained or backup links
9. Deploy monitoring — set up continuous monitoring of latency, jitter, packet loss, and MOS scores with automated alerting for threshold breaches
10. Test before going live — run a comprehensive network assessment and pilot with a small group of users before rolling out to the entire office

When to Call in the Experts

Network optimisation for VoIP sits at the intersection of telephony, networking, and security — three specialist disciplines that few small or mid-sized businesses have the in-house expertise to handle simultaneously. If you are experiencing persistent call quality issues, planning a VoIP migration from ISDN, or simply want to ensure your network is properly prepared for the PSTN switch-off, professional assistance can save you weeks of frustration and thousands of pounds in lost productivity.

At Cloudswitched, we have designed and configured VoIP-optimised networks for hundreds of UK businesses across London and the South East. Our network engineers perform thorough assessments, implement best-practice configurations across every layer of your infrastructure, and provide ongoing monitoring to ensure your call quality stays crystal-clear as your business grows and your demands evolve.