Your Office Network: Part 10 of 10
There is a pattern that plays out in offices everywhere. The business starts small. The ISP installs a combo modem-router. Someone buys an 8-port switch from the electronics store to add more ports. A consumer WiFi router gets plugged in for wireless. Phones get connected, computers get connected, and everything works well enough.
Then the office grows. More people, more devices, more cloud applications, more video calls. The problems are subtle at first. Calls that sound fine most of the time but occasionally get choppy. WiFi that slows down in the afternoon. A phone that inexplicably reboots every few days. Nothing bad enough to be an emergency, but a steady accumulation of small frustrations that everyone learns to work around.
This is the normal trajectory. Almost every small business goes through it. The question is not whether your network will outgrow its equipment, but whether you recognize when it has, and what to do about it.
The typical growth pattern
Understanding how networks typically evolve helps explain why the problems emerge.
Stage 1: The ISP box. The internet connection comes with a combo device that handles routing, WiFi, and sometimes even a few Ethernet ports. For a handful of people, this works. The device was designed for a home with a few family members, and a tiny office with three people is not that different.
Stage 2: The cheap switch. The ISP box does not have enough Ethernet ports, so someone buys a small unmanaged switch and plugs it in. Now there are more ports. The switch costs $30 and has no management features, no QoS, no VLAN support, and no PoE. But it provides ports, and that is what was needed.
Stage 3: Growing pains. The office has grown to 10, 15, or 20 people. Someone adds another switch. Maybe a second WiFi router gets plugged in for better coverage. Cables are run wherever they fit, some through walls, some across the floor, some held together with cable ties and hope. The network is a patchwork of consumer-grade equipment connected ad hoc over time.
At this stage, the network still mostly works. But "mostly" is doing a lot of heavy lifting. The problems are intermittent, hard to pin down, and easy to blame on the VoIP provider or the internet connection. And that is exactly where this post picks up.
Six signs your network has outgrown its equipment
1. Unexplained call quality problems despite a good internet connection
This is the most telling sign, and the most commonly misdiagnosed. You have a solid internet connection. Your ISP says the line is clean. Your VoIP provider says their platform is fine. But calls still have intermittent quality issues: choppy audio, jitter, brief dropouts, or audio that sounds robotic.
When the ISP is not the problem and the VoIP provider is not the problem, the internal network is the third variable in the blame game. And it is the variable nobody thinks to check because it is "just switches and cables."
The reality is that an internal network with no QoS, cheap unmanaged switches, and consumer-grade routing can introduce enough latency and packet loss to degrade voice quality even on an excellent internet connection. A VoIP quality test can help you confirm whether the problem is inside your building or further upstream. The problem is not the pipe to the internet. The problem is what happens to voice packets between the phone and the router.
2. Slow performance during busy periods
If the network feels fast in the morning but bogs down after lunch, or if everything slows to a crawl when someone starts a large file upload or a video conference, you are seeing the symptoms of a network with no traffic management.
Without QoS, all traffic competes equally for bandwidth. A cloud backup uploading gigabytes of data gets the same priority as a phone call. A software update downloading on 15 machines simultaneously gets the same treatment as the CEO's client call. The available bandwidth gets split up by whatever happens to arrive first, and time-sensitive traffic like voice loses every time.
This is particularly painful when combined with afternoon call quality degradation. The busiest period of the day is also the period when the most people are on calls, and it is exactly when the network is least able to handle them.
3. Running out of ports and daisy-chaining switches
When you need more Ethernet ports than your switch has, the tempting solution is to buy another small switch and plug it into the first one. When that one fills up, buy another one and plug it into the second. This is daisy-chaining, and it is a red flag.
Each switch in the chain adds latency. Each connection between switches is a potential bottleneck (especially if the daisy-chain link is the same speed as the individual device connections, meaning all traffic between the two switches shares a single port's bandwidth). None of the switches have management features, so there is no way to prioritize traffic or monitor what is happening on the network.
If you have more than two switches connected in a chain, or if your "switch" is actually a consumer WiFi router being used as a switch because you needed the extra ports, it is time to consolidate into a single managed switch with enough ports.
4. Phones and computers on the same flat network
If every device in your office, phones, computers, printers, the break room smart TV, and guest laptops, is on the same network with the same IP address range and no separation, you have a flat network.
A flat network means a broadcast storm from one misbehaving device affects everything, including active phone calls. It means a rogue device or malware on a guest's laptop is on the same network as your phone system. It means there is no way to prioritize voice traffic at the switch level because there is no separation between voice and data.
VLANs solve this by creating logical separation on the same physical equipment. But VLANs require managed switches and a router that supports inter-VLAN routing. If your equipment cannot do VLANs, that is a clear sign it needs to be upgraded.
5. WiFi cannot handle the device count
Every year, the number of wireless devices per person increases. A person in your office might have a laptop, a phone, a tablet, and a smartwatch, all connected to WiFi. Twenty people means 60 or more wireless devices competing for airtime on the same access points.
If your WiFi is a consumer router or two, each handling 30 to 40 connections, performance will be poor. Devices on the fringe of coverage will constantly disconnect and reconnect. Video calls will freeze. File downloads will stall.
The signs are obvious: complaints about WiFi speed, devices showing "connected" but unable to load anything, and a general perception that "the WiFi is terrible." The cause is almost always either too few access points, access points that cannot handle the client density, or poor channel planning.
6. The router is the bottleneck
This one ties back to everything we covered in the router post. Your router might be the bottleneck if:
Its CPU is maxed out. Many consumer and small-business routers have processors that are adequate for home use but struggle under office workloads. If the router's management interface shows sustained high CPU utilization, every packet is being delayed.
It has no QoS support. If the router cannot prioritize traffic, voice competes with everything else at the most critical point in the network: the WAN link. This is where congestion is most likely, and where QoS has the most impact.
SIP ALG cannot be disabled. If the router is actively breaking your VoIP traffic with a buggy SIP ALG implementation and there is no way to turn it off, the router is working against you.
Firmware is outdated with no update path. If the manufacturer has end-of-lifed the router and is no longer releasing updates, you are running known-vulnerable software on your internet gateway. This is a security issue as much as a performance issue.
Throughput does not match your internet speed. If you upgraded your internet to 500 megabits but your router's actual throughput (with NAT, firewall, and any VPN active) is 100 megabits, you are paying for speed you cannot use.
The upgrade path: prioritized by impact
If your network is showing several of these signs, you do not need to replace everything at once. Here is the order that delivers the most improvement for the money.
First: a managed PoE switch
Replace the daisy-chained consumer switches with a single managed PoE switch that has enough ports for all your devices, plus room to grow. A 24 or 48-port managed PoE switch gives you:
- Enough ports to eliminate daisy-chaining
- PoE to power phones and access points from the switch, simplifying cable runs and enabling UPS backup for phones
- VLAN support to separate voice and data traffic
- QoS at the switch level to prioritize voice traffic internally
- Port monitoring and statistics to help diagnose problems
- Proper management interface to configure and monitor the network
This single upgrade addresses signs 2, 3, and 4. It is typically the highest-impact change you can make.
Second: a business-class router
Replace the ISP combo box or consumer router with a business-class router that supports QoS on the WAN interface, VLAN routing, configurable NAT timeouts, and ideally has no SIP ALG at all.
This addresses sign 6 and significantly helps with signs 1 and 2. With QoS on the WAN link, voice traffic gets priority over everything else at the point where congestion actually occurs.
Third: proper wireless access points
Replace consumer WiFi routers with business-grade ceiling-mounted access points, properly placed and configured with appropriate channel planning. If you have a managed switch with PoE, the access points can be powered directly from the switch, simplifying installation.
This addresses sign 5 and dramatically improves wireless performance for everyone.
Fourth: cabling
If you are in a building with older cabling (Cat5 or Cat3), or if cable testing reveals problems, address the cabling last. This is the most expensive and disruptive upgrade, but it is also the most durable. Properly installed Cat6 cabling will serve the office for 15 to 20 years.
If cabling is in good shape (Cat5e or Cat6, properly terminated, recently tested), skip this step entirely. Do not replace working cable for the sake of replacing it.
Cost reality
The question everyone asks is "what does this actually cost?" Here are realistic numbers for a 20-person office.
Managed 24-port PoE switch: $300 to $800, depending on brand and features. Ubiquiti, TP-Link Omada, and Netgear offer good options at the lower end. Cisco and Aruba at the higher end. Any of them are a massive improvement over unmanaged consumer switches.
Business-class router: $200 to $600. Ubiquiti EdgeRouter or UniFi Dream Machine, MikroTik, Fortinet FortiGate, or similar. At the higher end, you get more sophisticated features, but even the entry-level options provide QoS, VLAN support, and configurable NAT.
Wireless access points (2 to 3 for a typical 20-person office): $100 to $300 each, so $200 to $900 total. Ubiquiti UniFi, TP-Link Omada, or similar. Ceiling-mount, 802.11ac or WiFi 6, with PoE power.
Cabling (if needed, 20 cable runs): $100 to $200 per run, professionally installed and certified. So $2,000 to $4,000 for a full recable. This is the big-ticket item but is only necessary if existing cabling is Cat3 or has significant problems.
Total without cabling: $700 to $2,300.
Total with cabling: $2,700 to $6,300.
If you are not sure where your network stands, our Bandwidth Calculator can help you estimate whether your current connection and equipment can handle your actual call volume and device count.
For a 20-person office where phone reliability matters, this investment pays for itself quickly. Consider what unreliable phones actually cost: the dropped call with a prospect, the support issue that required a callback because the call dropped, the daily frustrations of the staff person whose phone reboots every afternoon, the IT time spent chasing intermittent problems that would not exist on proper equipment. None of those costs show up on an invoice, but they are real.
When to bring in help
Not every upgrade requires a professional. Replacing a switch and plugging in cables is straightforward. Configuring VLANs and QoS requires more knowledge but is well-documented for most business-grade equipment.
But there are situations where professional help is worth the cost.
Cabling installation. Running cable through walls, ceilings, and conduit is skilled work. Poor installation creates the exact problems we covered in the cabling post. A low-voltage cabling contractor does this daily and will do it right.
Complex VLAN and QoS configuration. If you have multiple VLANs, inter-VLAN routing, QoS policies, and a mix of device types, the configuration can get complex. A network consultant who specializes in SMB environments can set this up correctly in a few hours and save you days of trial and error.
WiFi site surveys. A proper site survey with calibrated equipment produces an accurate coverage map and optimal AP placement plan. This is especially valuable in buildings with unusual construction or challenging layouts.
Ongoing management. If nobody in the office has the time or inclination to monitor and maintain the network, consider a managed service provider. The monthly cost is typically less than the productivity lost to network problems.
The series thesis, now that you have seen the whole picture
We started this series in the network closet, looking at the physical equipment that makes up your network. We covered wired vs. WiFi, switches, VLANs, QoS, PoE, cabling, routers, and WiFi. Each post covered one piece. Together, they form a complete picture of what is inside your network and how it affects your phones.
The thesis of this series is simple: your internal network is the part of the VoIP quality equation that nobody thinks about, and it is the part you can actually fix.
When call quality is bad, the instinct is to blame the VoIP provider or the internet connection. And sometimes those are the problem. But in a remarkable number of cases, the problem is inside the building. A flat network with no QoS. An overloaded consumer router with SIP ALG enabled. Daisy-chained unmanaged switches. Old cabling with intermittent failures. An access point from 2015 trying to serve 40 devices.
These are all fixable. They are fixable at a cost that is modest relative to the problem they cause. And once they are fixed, they stay fixed. A properly configured network does not need constant attention. It needs occasional updates and monitoring, but it does not create the steady drumbeat of unexplained problems that an ad-hoc network does.
You now know what is in your network, what each component does, and what to look for when something goes wrong. That is more than most business owners, office managers, or accidental IT people know. And it is exactly enough to make informed decisions about whether your network is serving you well or holding you back.
If something in this series described your situation, you know what to do next. If everything sounds unfamiliar and you are not sure where your network stands, start with a simple inventory: walk into the network closet, look at what is in there, and see how it compares to what this series described. That is always the first step.
This is the final post in the Your Office Network series. For the other side of the VoIP quality equation, the internet connection between your building and your VoIP provider, see our ISP series. For practical troubleshooting when calls sound bad, see Diagnosing VoIP Problems.
Share
Want to know when we publish new articles? Sign up for updates