What's in Your Network Closet and What It All Does

Your Office Network: Part 1 of 10

If you have ever walked into that closet, the one with the blinking lights and the tangle of cables that nobody is allowed to touch, and felt a vague unease about what all of it actually does, this post is for you.

The equipment in that closet is the foundation of every phone call, every video meeting, every email, and every file transfer that happens in your office. When everything works, nobody thinks about it. When something breaks, everyone thinks about it at the same time.

Understanding what each piece of equipment does, how they connect to each other, and where things can go wrong is the first step toward having a network that reliably supports your business. You do not need to become a network engineer. You just need to know enough to ask the right questions and recognize when something is not right.

The chain

Every piece of data that moves between the internet and a device on your desk follows a specific path through a series of equipment. The chain looks like this:

ISP connection → Modem or ONT → Router → Switch → Patch panel → Wall jack → Your device

Some offices skip a step or two. Some have extra pieces in between. But this is the general flow, and understanding each link in the chain is what the rest of this post covers.

The important thing to know upfront is that every link in this chain is a potential point of failure. A problem at any single point can degrade or break everything downstream of it. When your VoIP calls sound choppy or you get one-way audio, the cause could be hiding at any point along this path.

The modem or ONT

The first piece of equipment inside your building is usually either a modem or an ONT (optical network terminal). Which one you have depends on what type of internet connection you are using.

Cable modem

If you have cable internet, you have a cable modem. This is the box where the coaxial cable from your internet provider plugs in on one side, and an Ethernet cable comes out the other side. The modem's job is translation. It converts the signal format that your cable provider uses on their coaxial network into standard Ethernet that your router can understand.

Cable modems vary in quality and capability. Older modems may only support DOCSIS 3.0 while your provider has upgraded to DOCSIS 3.1, which means you could be leaving performance on the table. Some modems are provided by the ISP and some are customer-owned. Either way, it is worth knowing what model you have and whether it supports the speeds you are paying for.

The modem itself rarely causes VoIP-specific problems, but it can be the source of general connectivity issues. A modem that overheats, has degraded components, or is running outdated firmware can introduce packet loss or intermittent drops that affect everything, including voice calls.

Fiber ONT

If you have fiber internet, you have an ONT instead of a modem. The ONT does the same fundamental job, just with different technology. It converts the light signals traveling over the fiber optic cable into electrical signals on an Ethernet cable.

ONTs are typically installed and owned by the fiber provider. They are usually mounted on a wall near where the fiber enters the building. Most are fairly reliable, passive devices. The main thing that goes wrong with them is power loss, since they need electricity to operate. If your power goes out, your ONT goes down, and so does your internet, even though the fiber itself is unaffected. Some businesses install a small uninterruptible power supply (UPS) for the ONT specifically for this reason.

DSL modem

If you are on a DSL connection, you have a DSL modem. Same concept, different technology. It converts the signal on the telephone copper pair into Ethernet. DSL modems tend to run warm and can develop issues over time, especially in environments with poor ventilation.

Combination devices

Some ISPs provide a single box that combines the modem and router into one device. These are common in residential service and lower-tier business packages. They technically work, but they give you less control and less visibility into what is happening on your network. If your ISP provided an all-in-one unit and you are having persistent VoIP issues, separating the modem and router functions into dedicated devices is a common first step that IT professionals recommend.

The router

The router is arguably the most important piece of equipment in your network closet. It sits between your modem (the internet side) and everything else in your office (the local side), and it makes decisions about every single packet of data that enters or leaves your network.

What the router does

The router has several jobs.

Routing. It directs traffic between your local network and the internet. When your phone sends a voice packet to your VoIP provider, the router sends it out through the modem. When a packet comes back, the router figures out which device on your network should receive it and delivers it there.

NAT (Network Address Translation). Your ISP gives you one public IP address (sometimes a small handful), but you have dozens of devices inside your office. The router maintains a translation table that lets all of those devices share a single public address. This is essential for normal operation, but it can also be a source of VoIP problems. NAT traversal is one of the most common causes of one-way audio and failed calls.

Firewall. The router inspects incoming traffic and blocks anything that does not look like a response to something your network requested. This is critical for security, but firewalls that are too aggressive can interfere with VoIP traffic, which has unusual traffic patterns compared to web browsing or email.

DHCP. The router typically assigns IP addresses to devices on your network automatically. This is usually invisible until it is not, like when two devices get the same address and one of them stops working intermittently.

Quality of Service. On a properly configured router, Quality of Service rules prioritize voice traffic over less time-sensitive data. This is the single most impactful setting for VoIP quality on your local network. Without it, your phone calls compete equally with file downloads, cloud backups, and software updates for the available bandwidth.

Why the router matters so much for VoIP

The router is the bottleneck where your fast internal network meets your slower internet connection. If your office has gigabit Ethernet internally but a 100 megabit internet connection, the router is the funnel where all that traffic has to squeeze through. During busy periods, this is where congestion happens, and congestion is what causes jitter and packet loss on your calls.

A consumer-grade router handling traffic for 20 or 30 devices will struggle. Its processor is not fast enough, its memory is limited, and its Quality of Service implementation is either nonexistent or rudimentary. Business-grade routers are built for this workload and provide the controls you need to protect voice traffic.

The switch

If the router is the brain of your network, the switch is the nervous system. It provides the physical Ethernet ports where all of your devices connect, and it moves traffic between them.

When your desk phone needs to communicate with the router (to send voice packets to the internet), the switch handles that connection. When your computer needs to reach a printer on the same network, the switch handles that too, without the traffic ever needing to touch the router.

Switches come in two main varieties: unmanaged and managed.

Unmanaged switches are simple. You plug in cables and they work. There is no configuration, no login screen, no settings to adjust. They treat all traffic equally, forwarding packets as fast as they can without any prioritization or segmentation. For a very small office with a handful of devices, an unmanaged switch is often sufficient. But as soon as VoIP quality becomes a concern, the lack of traffic prioritization becomes a liability.

Managed switches add a layer of intelligence. They let you configure VLANs (virtual local area networks) to separate voice and data traffic, enable Quality of Service to prioritize voice packets, monitor port-level traffic for diagnostics, and provide PoE (Power over Ethernet) to power phones directly through the network cable.

We cover switches in much more detail in Part 3 of this series, and VLANs in Part 4.

Wireless access points

Wireless access points provide Wi-Fi for laptops, phones, tablets, and other devices that are not connected with a cable. In some offices, the router has built-in Wi-Fi. In larger offices, dedicated access points are mounted on ceilings or walls and wired back to the switch.

For general office work, Wi-Fi is fine. For VoIP, it is a significant risk factor. Wireless is a shared medium with inherent variability in latency and reliability. A wired connection to a switch provides consistent, predictable performance. A wireless connection provides variable performance that depends on how many devices are active, what the radio environment looks like, and where the device is physically located.

This does not mean you cannot take calls on Wi-Fi. It means you should understand the trade-offs. We dedicate the entire next post to this question because it is the single most impactful decision for VoIP quality in most offices. There is also a standalone deep dive on wired vs. Wi-Fi for VoIP if you want the full technical breakdown.

The patch panel

The patch panel is the least glamorous piece of equipment in the closet, and also one of the most important for maintainability. It is a flat panel with rows of numbered ports, usually mounted on a rack or wall.

Here is what it does. The Ethernet cables that run through your walls to the wall jacks at each desk are permanent installations. They are run through conduit, stapled along joists, and terminated at both ends. You do not want to be plugging and unplugging these cables regularly because the connections at the cable ends wear out and the cables are difficult or impossible to replace without opening walls.

The patch panel solves this. The permanent in-wall cables terminate on the back of the patch panel. On the front, you use short patch cables to connect each port to the corresponding port on your switch. If you need to move someone to a different switch port, you move the patch cable. If a patch cable goes bad, you replace a $3 cable instead of re-running a $300 cable through the wall.

The patch panel itself is passive. There are no electronics, no power, no configuration. But bad terminations on the patch panel are a real and surprisingly common source of intermittent connectivity problems. A pin that is not making solid contact can cause the kind of sporadic packet loss that drives people crazy because it comes and goes unpredictably.

If you are experiencing intermittent network problems that seem to affect specific desks or jacks, the patch panel terminations are worth checking.

Wall jacks and cables

At the other end of the in-wall cables are the wall jacks at each desk. An Ethernet cable runs from the wall jack to the device, whether that is a phone, a computer, or both.

Most VoIP desk phones have two Ethernet ports on the back. One connects to the wall jack (labeled "LAN" or "Network" or with an icon of a globe). The other connects to the computer (labeled "PC" or "Computer" or with an icon of a monitor). This passthrough design lets the phone and computer share a single cable run from the closet. The phone sits in the middle, acting as a tiny switch. This is a standard and reliable configuration, and it means you do not need two cable runs to every desk.

The cables themselves matter more than people realize. Damaged cables, cables that are too long, cables that run alongside electrical wiring, and cables with a lower category rating than the network requires can all cause problems. Cat 5e is the minimum for gigabit Ethernet. If your building has old Cat 5 (not 5e) cabling, those runs should be on the list to replace.

How it all connects

Let's trace the path of a voice packet from your desk phone to the internet.

You are on a call. You say something. The phone captures the audio, compresses it using a codec, and wraps it in a data packet. The packet leaves the phone through the Ethernet cable, travels to the wall jack, through the in-wall cable to the patch panel, through the patch cable to the switch.

The switch reads the destination address on the packet and forwards it to the port where the router is connected. The router sees that the packet is destined for an address on the internet (your VoIP provider), applies any Quality of Service rules, performs the NAT translation from your internal address to your public address, and sends it out through the modem.

The modem converts the signal for your ISP's network, and the packet begins its journey across the internet to your VoIP provider.

Coming back, the reverse happens. A packet arrives from your VoIP provider, through the modem, to the router. The router's NAT table tells it which internal device this packet belongs to. It forwards the packet to the switch, which delivers it through the patch cable, through the in-wall cable, out the wall jack, and down the cable to your phone. The phone decodes the audio and plays it through the speaker.

This entire round trip takes somewhere between 20 and 150 milliseconds depending on where your VoIP provider is and how your network is configured. Every piece of equipment in the chain adds a small amount of processing time. On a healthy network, each local device adds well under a millisecond. But problems at any point, a congested router, an overloaded switch, a bad cable, can add delay, jitter, or outright packet loss that degrades the call.

Every link is a potential problem

This is the key takeaway. Your network is a chain, and every link in that chain can introduce problems.

A flaky modem causes intermittent drops. An undersized router adds latency under load. An unmanaged switch cannot prioritize voice traffic. A bad patch panel termination causes sporadic packet loss. A damaged cable creates intermittent errors. A wireless connection adds unpredictable jitter.

The good news is that this is also the part of the voice path you control. You own this equipment. You can configure it, upgrade it, and replace it. Problems that originate inside your building are the most fixable problems in the entire chain.

The rest of this series walks through the most important decisions and configurations for each piece. If you want a quick read on whether your current setup can handle VoIP, our Bandwidth Calculator can estimate how much capacity your office actually needs based on your call volume and device count. We start with the single most impactful choice most offices face: whether to run their voice devices on wired Ethernet or Wi-Fi.

What comes next

The next post tackles the wired versus Wi-Fi question head on. It is the single decision that affects VoIP quality more than almost anything else in your office, and the answer is more nuanced than just "always use wired."

This is Part 1 of the Your Office Network series. Part 2: Wired Versus WiFi: Why This Decision Matters More Than You Think covers the most important infrastructure decision for voice quality.