Your Office Network: Part 6 of 10
If you have VoIP desk phones in your office, there is a good chance each one runs on a single Ethernet cable. No separate power adapter. No power strip under the desk. Just the one cable running from the phone to the wall jack, and from there back to a switch in your network closet. That cable carries both the network data and the electrical power the phone needs to operate.
This is Power over Ethernet, universally called PoE, and it is one of those technologies that works so well when it is set up correctly that nobody thinks about it. The problems start when the setup is not quite right, or when the network grows past what the original equipment was designed to support.
What PoE actually is
At its core, PoE is a way to deliver electrical power over the same copper Ethernet cable that carries network data. The switch (or a separate device called a PoE injector) puts power onto the cable. The device at the other end, your phone, your wireless access point, your security camera, draws that power to operate.
The phone does not know or care that it is receiving power from the cable rather than a wall outlet. From the phone's perspective, it boots up, connects to the network, and works. The cable handles both jobs simultaneously.
This matters for office environments because it dramatically simplifies deployment. You do not need a power outlet at every desk where a phone sits. You do not need power adapters cluttering up desks. When you add a new phone, you just run a cable. When you move a phone, you just move the cable. The phone works wherever there is a network drop, because the network drop is also the power source.
It also matters for reliability in a way that is easy to overlook. If your network switches are connected to an uninterruptible power supply in the network closet, then every PoE phone in the building inherits that backup power automatically. When the power goes out, your phones stay on as long as the UPS battery holds. No separate battery backups at each desk. No phones going dark while the computers on their own UPS keep running.
The PoE standards
Not all PoE is the same. The IEEE has defined several standards, and they differ primarily in how much power they can deliver to a device. Knowing which standard your equipment supports matters because it determines what devices you can power and how many of them.
802.3af (PoE): 15.4 watts
This is the original PoE standard, and it is sufficient for most VoIP desk phones. A typical desk phone draws somewhere between 5 and 13 watts, well within the 15.4 watts that 802.3af provides. If your phones are standard desk models (not large touchscreen phones, not conference room units), 802.3af is probably all you need on the phone side.
One important detail: the 15.4 watts is the power the switch puts onto the cable. By the time it reaches the device at the other end, some power has been lost to resistance in the cable itself. The device actually receives closer to 12.9 watts. For a desk phone drawing 6 to 10 watts, this is still plenty. But it is worth understanding that the number on the spec sheet is not quite the number the device gets.
802.3at (PoE+): 30 watts
PoE+ doubles the available power. This is what you need for devices that draw more than a basic desk phone: conference room phones with large displays and speaker arrays, wireless access points (especially modern WiFi 6 models), certain video phones, and IP cameras with pan-tilt-zoom motors.
If you are deploying wireless access points alongside your phones and powering them from the same switches, you almost certainly need switches that support 802.3at. A modern WiFi 6 access point can draw 15 to 25 watts, which exceeds what 802.3af can deliver.
802.3bt (PoE++): 60 to 90 watts
This is the most recent standard, and it provides significantly more power. Devices that need this much include high-end video conferencing units, digital signage displays, and some specialized equipment. For a standard office phone deployment, 802.3bt is overkill. You are unlikely to need it unless you are powering something beyond phones and access points.
The reason to know about 802.3bt is not because you need it today, but so you are not confused when you see it on spec sheets. If a switch vendor is advertising PoE++ support, that is a feature aimed at specific use cases, not something that makes your desk phones work better.
How the negotiation works
When a PoE device is plugged into a PoE switch port, the switch does not immediately blast full power down the cable. There is a negotiation process. The switch sends a low-voltage probe signal to detect whether the connected device is PoE-capable. If it is, the switch and the device agree on a power class, which tells the switch how much power the device needs. Only then does the switch deliver the appropriate amount of power.
This negotiation is why you can safely plug a non-PoE device into a PoE switch port. The switch probes the device, gets no PoE response, and simply does not deliver power. The port works as a normal Ethernet port. You will not damage a laptop or a printer by plugging it into a PoE switch.
The PoE budget: the problem nobody plans for
Here is where most offices get caught. Every PoE switch has a total power budget. This is the maximum amount of electrical power the switch can deliver across all of its PoE ports combined. It is a fixed number determined by the switch's internal power supply, and it is almost always less than what you would get if every port delivered maximum power simultaneously.
A 24-port PoE switch might have a power budget of 370 watts. If every port is using 802.3af to power a phone drawing 15.4 watts at maximum, the theoretical demand is 24 times 15.4, which is 369.6 watts. That is cutting it extremely close. And if any of those devices draw more than the minimum, or if you plug in a few access points that need 20 watts each, the math stops working.
What happens when the budget runs out
When a switch's PoE budget is fully allocated and you plug in one more device, the switch has to make a choice. Different switches handle this differently, and none of the options are good.
Some switches refuse to power the new device. The phone plugs in and simply does not boot. There is no error message on the phone because the phone never receives power. It sits there dark and silent. If you do not know about PoE budgets, this looks like a dead phone or a bad cable. You might spend an hour troubleshooting the cable, swapping ports, even replacing the phone, before someone thinks to check the switch's power budget.
Some switches use a priority system. When the budget is exceeded, the switch powers down the device on the lowest-priority port to free up power for the new device. This means a phone that was working perfectly fine suddenly reboots or goes dark, seemingly at random. In practice, "at random" means "when someone plugged a new device in on the other side of the office," which is not an obvious connection to make.
Some less sophisticated switches simply become unstable when overloaded. Phones reboot intermittently. Power delivery fluctuates. The symptoms look like a hardware problem with the switch itself, or like a network problem, or like the phones are defective. Diagnosing this without knowing about PoE budgets is genuinely difficult.
Real-world budget math
The good news is that most phones do not draw their maximum rated power continuously. A typical Polycom, Yealink, or Cisco desk phone draws 5 to 10 watts in normal operation. So a 24-port switch with a 370-watt budget can comfortably power 24 phones with room to spare.
The math gets tighter when you mix device types. Say you have 20 phones drawing 8 watts each (160 watts), plus 4 wireless access points drawing 20 watts each (80 watts). Total: 240 watts out of a 370-watt budget. That is fine. But add a few more access points, or upgrade to access points that draw 25 watts, and you start approaching the limit.
The rule of thumb is to add up the expected power draw of all PoE devices you plan to connect, then add 20 to 30 percent headroom. If the result exceeds your switch's PoE budget, you need either a switch with a larger power supply, a second switch, or separate PoE injectors for some devices.
PoE and cable quality
PoE requires all four pairs of wires in the Ethernet cable. Standard Ethernet data transmission at 100 megabits only uses two of the four pairs, which is why some very old or very cheap cables that are missing wire pairs can still carry data at lower speeds. But PoE uses the spare pairs (or, in some standards, shares the data pairs) to deliver power. If a cable is missing a pair, or if a pair has a break or a poor connection, PoE either will not work at all or will deliver unreliable power.
This means that cable quality matters more when PoE is in play. A cable with a marginal crimp on one connector might carry data fine but fail to deliver consistent power. A cable that works at 10 or 100 megabits because it only needs two pairs will not support PoE because PoE needs all four.
The minimum cable category for PoE is Cat5e. If your building has old Cat5 (not Cat5e) or, worse, Cat3 cabling from a legacy phone system, that cabling may not reliably support PoE. We cover cable categories and their implications in detail in the next post.
Cable length and power delivery
Ethernet cables have a maximum supported length of 100 meters (roughly 328 feet). This limit applies to both data and power, but power has an additional consideration: the longer the cable, the more power is lost to resistance in the copper wire.
On a short cable run of 10 or 20 meters, the power loss is negligible. On a run approaching 100 meters, the loss can be significant enough that a device right at the edge of a standard's power limit might not receive enough power to operate reliably. The phone might boot intermittently, reboot under load, or fail to power up at all.
If you have long cable runs and PoE devices, you may need to account for the power loss when planning your budget. Some switches report the actual power being drawn by each port, which can help you identify devices that are close to their power limit.
PoE injectors and midspan devices
Not every switch has PoE capability, and not every environment needs to replace an entire switch just to power a few devices. That is where PoE injectors come in.
A single-port PoE injector is a small box that sits between the switch and the device. The Ethernet cable from the switch plugs into one side, a cable to the phone plugs into the other side, and the injector adds power to the cable. It is a targeted solution for adding PoE to one or two devices on a non-PoE switch.
A midspan injector (sometimes called a PoE patch panel) does the same thing for multiple ports. It sits between a non-PoE switch and a patch panel, adding power to some or all of the cables passing through it. This lets you add PoE capability to an existing switch without replacing it.
Injectors and midspans work well as interim solutions or for small deployments. In larger environments, a proper PoE switch is simpler and more manageable because the switch handles both data and power through a single management interface.
Planning your PoE deployment
If you are setting up a new network or expanding an existing one, a few minutes of PoE planning prevents hours of troubleshooting later.
Step 1: Inventory your PoE devices
List every device that will draw power from the switch. This typically includes desk phones, conference phones, wireless access points, and possibly security cameras or other devices. For each one, find the power draw specification, usually in the device's datasheet.
Step 2: Add up the power
Sum the power draw of all devices. Use the typical (not maximum) power draw if your documentation distinguishes between the two. Most phones list both, and the typical draw is significantly lower than the maximum.
Step 3: Add headroom
Add 20 to 30 percent to your total. This covers fluctuations in device power draw, future additions, and the reality that devices occasionally spike above their typical draw during boot-up or firmware updates.
Step 4: Match to switch capacity
Compare your total (with headroom) to the PoE budget of the switch you are considering. If it fits with room to spare, you are set. If it is close, consider a switch with a larger power supply or plan to split the devices across two switches.
Step 5: Verify cable quality
Confirm that your cabling is Cat5e or better and that all four pairs are intact. If you have any doubt, test the cables. A cable that passes a data test but fails PoE testing has a problem with one or more wire pairs.
PoE and VLANs
If you followed the series through VLANs, you know that voice and data traffic should be on separate VLANs. PoE works seamlessly with VLANs. The power delivery is a physical-layer function that has nothing to do with VLAN tagging. A port can be configured for a voice VLAN, a data VLAN, or both, and PoE will deliver power regardless of the VLAN configuration.
This is worth mentioning because people sometimes wonder whether VLAN configuration affects PoE. It does not. The power negotiation happens before any network traffic flows.
PoE and QoS
Similarly, QoS configuration and PoE are independent. QoS handles how traffic is prioritized on the network. PoE handles how power is delivered over the cable. You configure them separately, and they do not interact. A phone receiving PoE power does not get any different QoS treatment because of that; QoS is determined by traffic markings and switch configuration, not by power delivery.
Common PoE problems and what they look like
Here is a quick reference for the PoE issues you are most likely to encounter.
Phone does not power on at all. Check whether the switch port has PoE enabled (some switches have it disabled by default). Check the PoE budget, because the switch may be out of power. Check the cable, since PoE needs all four pairs working. Try a different port to isolate whether the issue is the port, the cable, or the device.
Phone reboots randomly. This can indicate a PoE budget that is marginally exceeded, causing the switch to cycle power on lower-priority ports. It can also indicate a cable problem where one pair has an intermittent connection, causing power delivery to fluctuate. Check the switch's PoE power usage and port priority settings.
Phone boots but shows errors. Some phones display a warning if they are receiving less power than they request. This usually means the switch is providing 802.3af when the phone prefers 802.3at, or the cable run is too long and power loss is reducing the delivered wattage below the phone's requirements.
Some phones work, new phones will not boot. Classic PoE budget exhaustion. The budget was fully allocated by existing devices, and there is no power left for additional ones. Check the switch's total PoE utilization.
Phone works on one port but not another. If the phone works when plugged into a different port on the same switch, the original port may have PoE disabled, or there may be a cable problem between the original port and the wall jack. If the phone works on a different switch entirely, the first switch may have a PoE budget or hardware issue.
The connection to call quality
PoE problems do not directly cause poor call quality in the way that network congestion or jitter does. But they cause something arguably worse: complete phone outages. A phone that cannot get power is a phone that does not work at all. And intermittent PoE problems cause intermittent phone reboots, which drop active calls and make the phone temporarily unavailable.
In a troubleshooting scenario, PoE issues are easy to overlook because they look like other problems. A phone that reboots during a call looks like a firmware crash. A phone that will not boot looks like a hardware failure. Random reboots look like a network issue. Knowing that PoE budget exhaustion and cable quality can cause these symptoms saves you from chasing the wrong problem. If you are seeing intermittent phone issues and have ruled out PoE, running a VoIP quality test can help determine whether the problem is power-related (phones dropping entirely) or network-related (degraded audio on calls that stay connected).
What you should know about your own setup
If you have PoE phones, here are the questions worth answering:
- What is the total PoE budget of each switch that powers devices?
- How much of that budget is currently being used? (Most managed switches report this in their web interface.)
- How many additional PoE devices could you add before hitting the budget?
- Are your cable runs within reasonable length, and is the cabling Cat5e or better?
- Are your switches connected to a UPS, giving your phones backup power?
If you cannot answer these questions, that is normal. Most people cannot. But now you know they are worth asking.
This is Part 6 of the Your Office Network series. Next up: The Cabling in Your Walls, on why the physical cable is the most overlooked component in your network and how old or damaged cabling creates problems that are maddening to diagnose.
Share
Want to know when we publish new articles? Sign up for updates