The Cabling in Your Walls: Why Bad Cable Breaks Calls

Your Office Network: Part 7 of 10

Every network discussion eventually gets to switches, routers, VLANs, and QoS. Those are the things you configure. But underneath all of that configuration sits a physical reality: copper wire in the walls, terminated into jacks, punched into patch panels, connected by patch cables. That cabling is the physical foundation of your entire network, and when it has problems, everything built on top of it has problems too.

The frustrating part is that cable problems rarely cause a clean failure. A bad cable does not usually stop working entirely. Instead, it works most of the time and fails some of the time, in a pattern that seems random, is difficult to reproduce, and makes you question your own troubleshooting.

For VoIP, this matters more than it does for most other applications. And the reason goes back to a fundamental difference in how voice and data handle errors.

Why cabling problems hit voice harder than data

When you download a file or load a web page, the underlying protocol (TCP) detects lost or corrupted packets and retransmits them. If a bad cable corrupts a packet, TCP notices, requests the data again, and the file arrives intact. The download might slow down slightly, but it completes correctly. You might not notice anything at all.

Voice does not work this way. VoIP uses UDP, which does not retransmit. A voice packet that arrives corrupted or does not arrive at all is simply gone. There is no mechanism to request it again because by the time the retransmission would arrive, the conversation has moved on. The moment has passed.

This means that a cable with a marginal connection, one that introduces errors on perhaps 0.5 percent of packets, can be essentially invisible to normal data usage while causing noticeable choppy or robotic audio on voice calls. Web browsing works fine. File transfers complete. Email arrives. But phone calls have intermittent quality issues that nobody can pin down.

This is why cabling is worth an entire post in this series. It is the most overlooked component in most office networks, and when it is the source of a problem, the symptoms point everywhere except at the cable.

Cable categories: what the labels mean

Ethernet cables are classified by category, which defines their performance specifications. The category determines the maximum frequency the cable can carry and, consequently, the maximum data rate it supports over a given distance.

Cat3

Category 3 cable was designed for 10 megabit Ethernet and traditional telephone systems. If your building had a legacy phone system with analog lines running to every desk, those cables are almost certainly Cat3. You can identify it by the markings printed on the cable jacket, which should say "CAT3" or "Category 3."

Cat3 is not suitable for modern networking. It cannot reliably support 100 megabit Ethernet, let alone gigabit. It has two or four pairs of wires, but the twist rate (the number of twists per inch, which is critical for canceling electromagnetic interference) is too low for higher speeds. If your building's data cabling is Cat3, it needs to be replaced. There is no configuration that makes Cat3 work for a modern VoIP deployment.

One nuance: if your building has Cat3 running from a legacy phone system, those cables were probably run to every desk and are terminated in a phone-style patch panel. You cannot repurpose those cables for Ethernet. They need to be replaced with proper data cabling.

Cat5

Plain Category 5 (not Cat5e) was the standard for 100 megabit Ethernet in the late 1990s. It has four pairs of wire and supports 100BASE-TX at distances up to 100 meters. You will find it in buildings wired during roughly 1995 to 2002.

Cat5 is marginal for modern use. The 1000BASE-T standard (gigabit Ethernet) technically requires Cat5e as a minimum. Plain Cat5 cables will sometimes negotiate a gigabit link successfully, especially on shorter runs, but they were not designed or tested for that speed and may introduce errors under load that show up as intermittent problems.

For VoIP, Cat5 can work if the runs are short and the cables are in good condition. But if you have Cat5 cabling and you are experiencing intermittent quality issues, the cabling should be high on your suspect list. Testing the cables (more on this below) can tell you whether they meet Cat5e performance specifications even if they are labeled Cat5.

Cat5 also supports PoE, provided all four pairs are intact and the cable is in good condition. But the lower twist rate compared to Cat5e means it is more susceptible to interference, which can cause problems when power and data share the same cable.

Cat5e

Category 5e (the "e" stands for enhanced) is the minimum recommended cable for modern office networks. It supports gigabit Ethernet at distances up to 100 meters and is the baseline for reliable PoE delivery. Cat5e became the standard in the early 2000s and is still the most commonly installed cable in buildings wired in the last 20 years.

If your building has Cat5e cabling in good condition, there is no urgent need to replace it. It will handle gigabit speeds, PoE, and VoIP without issues. The "minimum" label does not mean it is inadequate. It means it meets the requirements with appropriate margin.

Cat6

Category 6 cable offers better performance than Cat5e, with tighter twist rates, better separation between wire pairs, and support for 10 gigabit Ethernet at distances up to 55 meters. For gigabit Ethernet (which is what most office networks actually run), Cat6 provides more headroom against interference and crosstalk.

For a new installation, Cat6 is the recommended choice. The cost premium over Cat5e is modest, and the improved performance margin means the cabling will be more tolerant of slightly imperfect terminations, longer-than-ideal runs, and proximity to interference sources. It also provides a degree of future-proofing if you eventually need 10 gigabit speeds on some runs.

Cat6a

Category 6a supports 10 gigabit Ethernet at the full 100-meter distance. It is a thicker, heavier cable that is more expensive and harder to work with. For most office environments, Cat6a is future-proofing beyond what current needs require.

The main use case for Cat6a in a typical office is the cable run from the network closet to a wireless access point that might someday need a 10 gigabit uplink. If you are pulling new cable and the cost difference is acceptable, Cat6a on access point runs is a reasonable investment. For desk runs to phones and computers, Cat6 is sufficient.

Common cable problems

Cabling fails in ways that are more varied and more insidious than most people expect. Here are the problems that show up most often in office environments.

Damaged connectors

The RJ45 connector at the end of a patch cable, or the jack in the wall plate, is a mechanical connection with eight tiny metal contacts. Those contacts can be bent, corroded, or worn. A connector that has been plugged and unplugged many times develops wear on the contact surfaces. A connector that was crimped poorly during installation might have one or more wires that are not making solid contact.

The result is an intermittent connection. The cable works fine when nothing is touching it, but a slight vibration, a temperature change that causes metal to expand or contract, or just the weight of the cable pulling on the connector can break contact momentarily. That momentary break drops packets. For data, TCP retransmits. For voice, the audio stutters.

Kinks and tight bends

Ethernet cable has a minimum bend radius. Cat5e and Cat6 should not be bent tighter than about four times the cable diameter. When cable is kinked or bent sharply, the internal wire pairs can be pushed out of their proper position, changing the electrical characteristics of the cable. In extreme cases, the insulation on individual wires can be damaged, allowing them to short against each other.

Kinks often happen at wall plates where too much cable was pushed into a small junction box, or behind furniture where cables are bent around tight corners. The cable might test fine with a basic continuity tester because the wires are not broken, but the altered electrical characteristics can cause errors at higher speeds.

Pinched cables

When cables run through walls, ceilings, or floors, they can be pinched by furniture, caught in ceiling tile grids, or compressed by cable ties that are too tight. A pinched cable has the same problem as a kinked one: the physical deformation changes the electrical characteristics.

This is particularly common when someone runs cables under carpet, through doorways, or along the base of walls where chairs roll over them. The damage accumulates over time and may not be apparent until the cable starts causing errors.

Electromagnetic interference

Ethernet cables that run parallel to electrical power cables can pick up electromagnetic interference (EMI). The twist in the wire pairs is specifically designed to cancel out external interference, but if the cable runs alongside a high-power circuit for a long distance, the interference can exceed what the twisting can handle.

The most common scenario is cable runs through conduit that also carries power wiring, or cables that are laid directly on top of fluorescent light ballasts in a drop ceiling. The interference introduces noise on the signal, which the receiving device interprets as errors.

Cat6 and Cat6a cable are more resistant to EMI than Cat5e because of their tighter twist rates and (in Cat6a) additional shielding. But the best solution is to maintain physical separation between data and power cables, ideally at least 12 inches, and to cross power cables at 90-degree angles rather than running parallel.

Poor terminations

Every cable in your building was terminated by someone, either at the factory (for patch cables) or by an installer (for in-wall runs). A proper termination has each of the eight wires inserted fully into the correct position and making solid contact. An improper termination might have wires in the wrong order, wires not fully seated, too much untwisted wire exposed at the termination point, or the jacket not properly secured.

Poor terminations are especially common when cables were installed by someone without proper training or tools. The cable might pass a basic continuity test (all eight wires connect from end to end) but fail a performance test because the untwisted wire length at the termination exceeds the specification, introducing crosstalk.

Water damage and age

Cables in exterior walls, below-grade installations, or buildings with water intrusion issues can absorb moisture. Water in the cable changes its electrical characteristics dramatically, and once a cable has been wet, its performance is permanently degraded even after it dries.

Age alone can also degrade cable performance. The insulation on older cables can become brittle and crack, especially in environments with temperature extremes. The jacket can shrink, putting stress on the connectors. After 15 to 20 years, even a properly installed cable may not meet its original performance specifications.

How cable problems show up

The symptoms of cable problems depend on the severity and the type of failure. Here is what to watch for.

Intermittent connection drops. The device loses its network connection briefly, reconnects, then works fine for a while before dropping again. This typically indicates a marginal physical connection at a connector.

Speed negotiation failures. A device that should connect at gigabit speed instead connects at 100 megabits. This often means one or more wire pairs are not working, and the switch and device have fallen back to a speed that only requires two pairs.

Intermittent voice quality issues. Choppy audio, brief dropout during calls, or audio artifacts that come and go. The cable is introducing enough errors to cause occasional packet loss, but not enough to disrupt data applications that can retransmit.

CRC errors on switch ports. If you have a managed switch, check the port statistics. A port connected to a bad cable will show CRC (Cyclic Redundancy Check) errors, which indicate corrupted frames arriving at the switch. A healthy port should show zero or very close to zero CRC errors over an extended period.

Problems that correlate with physical events. Quality issues that happen when someone moves something on their desk, when the HVAC system kicks on (causing vibration), or when the office temperature changes. These suggest a marginal physical connection that is sensitive to movement or thermal expansion.

Testing your cables

There are two levels of cable testing, and the difference matters.

Basic cable testers ($20 to $50)

A basic cable tester checks continuity: are all eight wires connected from one end to the other, and are they in the correct order? It will catch cables with broken wires, cables that were wired in the wrong pin order, and cables with shorts between wires.

What a basic tester will not catch is performance problems. A cable can pass a continuity test with flying colors while still failing to support gigabit Ethernet reliably because of excessive crosstalk, insufficient twist rate, or impedance mismatches from poor terminations. Basic testers are good for catching obvious problems and for verifying that newly terminated cables have the wires in the right order, but they cannot tell you whether a cable will perform at its rated speed.

Cable certifiers ($2,000 to $15,000)

A cable certifier (sometimes called a cable qualifier or cable analyzer) performs a comprehensive battery of tests that measure the cable's actual electrical performance against the specifications for its rated category. It measures insertion loss, return loss, crosstalk (NEXT and FEXT), propagation delay, and cable length. At the end, it gives you a pass or fail result for a specific cable category.

A certifier will definitively tell you whether a cable meets Cat5e, Cat6, or Cat6a specifications. If a cable fails certification, the certifier usually tells you why and approximately where along the cable run the problem is.

These are expensive tools, and most offices do not own one. But low-voltage cabling contractors have them, and a contractor can certify all your cable runs for a reasonable fee, typically a few dollars per run. If you are in a building with older cabling and experiencing intermittent network problems, having the cabling certified is one of the most cost-effective diagnostic steps you can take.

When to replace your cabling

Not every cable problem requires ripping out the entire building's cabling. Here is a practical decision framework.

Cat3: always replace. Cat3 cannot support modern networking or PoE. If your data network is running on Cat3, that is your problem and new cabling is the solution. There is no workaround.

Cat5 (plain, not Cat5e): test and plan. Have the cables tested with a certifier. If they pass Cat5e specifications (many Cat5 cables actually will, especially on shorter runs), you can continue using them with confidence. If they fail, plan for replacement, prioritizing the runs that serve voice devices first.

Cat5e with specific problems: replace the problem runs. If you have mostly Cat5e cabling and specific runs are showing errors, replace those individual runs. There is no need to recable the entire building because of a few bad cables.

Multiple failures across the building: full recable. If testing reveals widespread failures, especially in a building with cabling that is 15 or more years old, a full recable is usually more cost-effective than chasing individual failures. The labor to test, diagnose, and individually replace problem cables adds up quickly, and at some point, starting fresh with new cable is cheaper and gives you a known-good foundation.

Labeling: the highest-value, lowest-cost improvement

This is not about cable quality per se, but it is about cabling, and it is the single most valuable thing you can do that costs almost nothing.

Label both ends of every cable run. The jack at the desk should have a number that matches the port on the patch panel in your network closet. If you plug a phone into jack 47 at a desk, you should be able to walk to the network closet and immediately find port 47 on the patch panel.

This sounds obvious, and yet a remarkable number of office networks have unlabeled or mislabeled cable runs. When something goes wrong, the first step in troubleshooting is figuring out which cable run the affected device is on. Without labels, that means plugging in a cable tester at the desk and having someone in the network closet test each patch panel port one by one until you find the match. That process can take 20 minutes per cable run. With labels, it takes 5 seconds.

If your cabling is not labeled, buy a label maker and a Saturday afternoon of someone's time. Walk every desk, identify which patch panel port it connects to, and label both ends consistently. Use a numbering scheme that makes sense for your office. The convention does not matter as long as it is consistent and both ends match.

While you are at it, label which switch port each patch panel port connects to. A patch cable from patch panel port 47 to switch port Gi1/0/12 means you can go from "the phone on desk 47 has a problem" to "check switch port Gi1/0/12" in seconds.

The connection to everything else in the series

Good cabling is the foundation that everything else depends on. VLANs do not help if the physical cable is dropping packets. QoS cannot prioritize traffic that never arrives because the cable corrupted it. PoE needs all four pairs working, and a cable with one bad pair will not deliver power reliably.

When you are diagnosing VoIP problems, the cabling should be on your checklist, especially for intermittent issues that defy other explanations. Running a VoIP quality test before and after cabling work gives you concrete numbers to confirm whether the new or repaired cables actually resolved the problem. It is not the most glamorous part of networking, but it is the part that makes everything above it possible.

What comes next

Now that we have covered the physical layer from switches through PoE and cabling, we move to the device that connects your entire network to the internet: your router. It is doing more than you think, and some of what it is doing is actively making your VoIP problems worse.

This is Part 7 of the Your Office Network series. Next up: Your Router Is Doing More Than You Think, covering NAT, SIP ALG, firewalls, DNS, and why your router might be the biggest VoIP troublemaker in the building.