Your Local Network: The Part You Control

VoIP From the Ground Up: Part 6 of 10

When voice quality problems hit, there is a natural tendency to blame the VoIP provider or the internet connection. Sometimes that is the right call. But more often than people expect, the problem is inside their own building.

Your local network is the one piece of the entire voice path that you actually own and have the power to fix. Understanding what is in it and how it affects voice traffic is the most practical thing you can learn in this series.

What is in your local network

A typical office or home network has a handful of key components. Each one plays a role in how voice traffic moves.

The router

The router is the gateway between your local network and the internet. All traffic entering or leaving your building passes through it. The router makes decisions about where to send packets, can prioritize certain types of traffic over others, and typically includes a firewall that filters out unwanted connections.

For VoIP, the router is critical. If it is underpowered and struggling to process traffic quickly, it adds latency to every packet. If its Quality of Service features are not configured, voice packets get treated the same as everything else and have to compete for bandwidth during busy periods.

Switches

Switches are the connectors. They provide the physical ports where devices plug into the network with ethernet cables. When a device on one port needs to talk to a device on another port, the switch handles that connection.

In small environments, a single switch might handle everything. In larger offices, multiple switches are connected together, sometimes in a chain. Every switch a packet passes through adds a small amount of processing time. Older or lower-quality switches can also introduce errors or drop packets under heavy load.

Managed switches give you the ability to configure traffic prioritization at the port level. Unmanaged switches treat all traffic equally, which means voice packets get no special treatment.

Wireless access points

Wireless access points let devices connect to the network without a cable. They are convenient, but they introduce a set of problems that wired connections do not have. For a detailed comparison, see our post on wired vs. Wi-Fi for VoIP.

Wireless is a shared medium in a very literal sense. Every device connected to the same access point is competing for airtime on the same radio frequency. The access point can only talk to one device at a time, so it rapidly switches between them. This adds latency and jitter that are inherent to the technology, not the result of a misconfiguration.

Wireless signals are also susceptible to interference from other devices operating on the same frequencies: neighboring wireless networks, Bluetooth devices, microwave ovens, cordless phones, and various other electronics. Physical obstacles like walls, glass, and metal further degrade the signal.

For VoIP, wireless is a significant risk factor. Not because it cannot work, but because it introduces variability that wired connections simply do not have. A wired connection to a switch delivers consistent, predictable performance. A wireless connection delivers variable performance that changes based on how many devices are active, what the radio environment looks like at that moment, and where the device is physically located.

Cables

It sounds basic, but cabling matters. A damaged ethernet cable can cause intermittent packet loss that is maddening to diagnose because it comes and goes. Cables that are too long (beyond 100 meters for standard ethernet) degrade signal quality. Cables run alongside electrical wiring can pick up interference.

Old Category 5 cabling (not to be confused with Category 5e) in a building that has been upgraded to gigabit networking is a problem. The 1000BASE-T standard requires Category 5e as a minimum. Plain Category 5 cables will typically fail to negotiate a gigabit link at all, falling back to 100 megabits or refusing to connect reliably.

The bandwidth question

People often assume that poor VoIP quality means they need a faster internet connection. This is sometimes true, but less often than you would think.

A single VoIP call using the common G.711 codec requires roughly 85 to 100 kilobits per second in each direction when you account for all the overhead. That is almost nothing by modern standards. A typical business internet connection measured in tens or hundreds of megabits per second can theoretically carry hundreds of simultaneous calls.

The issue is usually not total bandwidth. It is what happens to the bandwidth during the moments of peak usage.

When someone in the office starts a large file download, kicks off a cloud backup, or joins a video conference, that traffic can temporarily consume enough bandwidth to crowd out voice packets. The voice call only needs a tiny slice of the connection, but it needs that slice consistently. A file download that temporarily saturates the connection for two seconds causes a two-second disruption to every active call, even though total bandwidth was adequate 99% of the time.

This is why bandwidth alone is a misleading metric for VoIP readiness. What matters is whether the network can guarantee consistent, low-latency delivery for voice traffic even when other applications are competing for the same connection.

Common local network problems

Based on real-world troubleshooting, these are the local network issues that most frequently degrade voice quality.

No traffic prioritization. Voice packets are treated identically to all other traffic. During congestion, they are delayed or dropped like everything else. Configuring Quality of Service on your router and switches to prioritize voice is the single highest-impact change most networks can make. We cover Quality of Service in detail later in the series.

VoIP phones on wireless. Desk phones, softphone applications, or headsets connected over wireless instead of ethernet. Every wireless connection adds jitter and latency that a wired connection avoids entirely.

Daisy-chained consumer switches. Small unmanaged switches plugged into other small unmanaged switches to add more ports. Each hop adds latency and none of them offer traffic prioritization. A single managed switch with enough ports is almost always the better solution.

Old or damaged cabling. Intermittent physical layer problems that cause sporadic packet loss. These can be extremely difficult to pinpoint because the problem comes and goes, often correlating with temperature changes or physical movement near the cable.

Overloaded router. A consumer-grade router handling traffic for 20 or 30 devices in a small office. The router's processor cannot keep up, adding latency to all traffic and sometimes dropping packets entirely when its buffers fill up.

No network segmentation. Voice traffic and data traffic sharing the same flat network with no separation. A broadcast storm or misbehaving device can affect everything, including active calls.

What you can actually do

The good news is that local network problems are the most fixable problems in the VoIP quality chain. You own the equipment. You control the configuration.

Start with the physical layer. Make sure VoIP endpoints are on wired connections wherever possible. Verify that cables are in good condition and rated for the speeds your network requires. Replace consumer-grade equipment with business-grade hardware in any environment where call quality matters.

Then move to configuration. Enable Quality of Service on your router and managed switches. If your network is large enough, put voice traffic on its own virtual local area network to isolate it from data traffic. Monitor your network during business hours to identify bandwidth hogs and usage spikes.

These steps will not solve every voice quality problem. Some problems originate beyond your network boundary, and those require a different approach. But fixing the local side first eliminates the most common causes and gives you a clean baseline for diagnosing anything that remains. Running a VoIP quality test before and after making changes gives you concrete data on whether your local network improvements actually moved the needle.

What comes next

The next post covers the other side of the equation: the internet, the long stretch of infrastructure between your building and your VoIP provider that you do not own and cannot directly fix. Understanding that part of the path is essential for knowing when the problem is not yours to solve and having the data to prove it.

This is Part 6 of the VoIP From the Ground Up series. Part 7: The Internet, The Part You Don't Control covers what happens to your voice traffic after it leaves your building.