Static, Buzzing, or Humming on Calls

When Your Phones Sound Bad: Part 11 of 12

Static, buzzing, or a persistent hum on phone calls is a different kind of problem from the packet loss and jitter issues that cause choppy or robotic audio. Where choppiness comes from network conditions, static and buzzing usually come from the analog parts of the path: the handset or headset, a power supply, an ATA or analog wiring, or the gateway's interface to the phone network. The audio isn't cutting out or breaking up. There's a constant unwanted noise layered over (or underneath) the conversation.

The character of the noise is actually diagnostic. A steady hum at a consistent pitch is different from random crackling, which is different from a buzz that fluctuates. Each type points to different causes.

Steady hum or drone

A constant hum, especially one at a low pitch, is almost always a ground loop or electrical interference issue.

Ground loops. A ground loop occurs when there are multiple paths to electrical ground in a system, creating a loop that acts like an antenna for hum. In a VoIP context, this almost always involves analog interconnects: an analog phone adapter (ATA) connected to both the network and an analog phone with its own grounding, a headset amplifier or external speaker with its own power supply, or analog trunk wiring at a gateway. It is rarely the Ethernet side. Ethernet ports are transformer-isolated, and PoE rides on those same isolated magnetics, so the data connection itself does not normally complete a ground loop. Treat "PoE ground loop" as a last-resort diagnosis that needs actual electrical evidence, not a starting assumption.

The classic test for a ground loop is to disconnect everything from the phone except the Ethernet cable and see if the hum goes away. Then reconnect devices one at a time. When the hum returns, you've found the device creating the loop.

If the hum is on a phone connected to an ATA (an adapter that connects a traditional analog phone to a VoIP system), the analog phone or the wiring between the ATA and the phone is the likely source. Analog phone connections are susceptible to electromagnetic pickup from nearby power cables, fluorescent lights, and other electrical equipment. Moving the ATA and its wiring away from power sources, or replacing the analog phone with an IP phone that doesn't need the ATA, often resolves the issue.

Power supply noise. If the phone is powered by an external power adapter rather than PoE, a failing or low quality power adapter can introduce electrical noise into the phone's audio circuitry. Try a different power adapter of the same rating. If the hum goes away, the original adapter was the culprit.

Electromagnetic interference (EMI). Phones placed near transformers, uninterruptible power supplies (UPS), fluorescent lighting ballasts, or large electrical equipment can pick up electromagnetic interference. This is more common with analog connections (ATAs and analog phones) than with digital IP phones, but even IP phones can be affected if the interference is strong enough to affect the phone's audio processing hardware.

Try moving the phone to a different location, at least a few feet from the suspected source of interference. If the hum stops or changes significantly, EMI is the cause.

Random crackling or static

Crackling and static that come and go, especially in bursts, are typically caused by an intermittent physical connection. The first question is which side of the phone the fault sits on. True analog crackle, the continuous frying texture layered under the voice, points at the analog parts: a handset cord, a headset connector, a failing speaker, or the phone-side wiring of an ATA. Faults on the Ethernet side sound different. A bad cable or port corrupts and drops packets, and the phone's packet loss concealment renders that as clicks, brief gaps, or robotic-sounding audio rather than continuous static, and the loss is visible in the stream's RTCP statistics (RFC 3550) and in a VoIP quality test. Keep that distinction in mind as you work through the checks below.

Bad Ethernet cable. A damaged Ethernet cable causes errors at the physical layer that drop frames; on a call, that manifests as the clicks, gaps, and garbled passages just described rather than analog-style static. The cable might have a damaged connector, a kink, an internal break in one of the wire pairs, or water damage. These problems can be intermittent, appearing when the cable is moved or when temperature changes cause expansion and contraction.

Replace the Ethernet cable between the phone and the switch. Use a known good cable and see if the crackling stops. If the phone connects through a wall jack, test by running a temporary cable directly from the switch to the phone, bypassing the wall jack and the in wall cabling. If the direct cable works, the problem is in the wall cabling or the jack.

Failing switch port. A switch port with a failing transceiver can cause link errors and packet loss that appear as dropouts and clicks. If replacing the cable doesn't help, try moving the phone's cable to a different port on the switch. If the artifacts stop, the original port may be faulty.

PoE issues. If the phone is powered by PoE and the switch's PoE delivery is unstable (due to a failing PoE controller, an overloaded PoE budget, or a cable that's marginal for PoE delivery), the phone can experience power fluctuations. Those typically show up as link flaps, reboots, or brief dropouts; only in marginal cases does the phone's own power or audio circuitry turn them into audible noise. Check the switch's PoE utilization and the power consumption of the affected port.

Standard 802.3af (PoE) and 802.3at (PoE+) can deliver power over just two of the four pairs in an Ethernet cable, which is sufficient for most VoIP phones. However, the specific PoE mode matters. "Mode A" PoE delivers power over the data pairs (pairs used for 10/100 Ethernet), while "Mode B" PoE delivers power over the spare pairs that 10/100 Ethernet does not use for data. If your switch uses Mode B and a spare pair is damaged, PoE will fail even though data works fine on the two data pairs. Only 802.3bt (PoE++, Type 3 and Type 4) requires all four pairs, but that standard is uncommon for typical VoIP phones. In practice, a cable that works for data at 100 Mbps (which only needs two pairs) can still fail for PoE if the pairs used for power delivery are damaged. This is a common gotcha with older cabling where unused pairs were never tested.

Buzzing that changes or fluctuates

A buzz that fluctuates in intensity, comes and goes, or changes character when you move the phone or touch a cable is almost always an intermittent contact point, and which cable reacts tells you which domain the fault is in. If the buzz responds to the handset or headset cord, an ATA's phone-side wiring, or an external audio accessory, it's an analog contact problem. If it seems to track the Ethernet cable, remember that the transport there is digital: an intermittent data contact produces dropouts and clicks, not a shifting buzz, so a buzz that follows the Ethernet cable usually points at the phone's own jack or power path rather than the data signal.

Check the physical connections on both sides. Reseat every connector. Check for corrosion on contacts, especially in environments with high humidity. Look for cables that are bent sharply at connector points or run across areas where they get stepped on or pinched by furniture.

In older buildings, cabling might be run near or through the same conduit as electrical wiring, and it's worth being precise about what that can and cannot do to a call. Audio crosses an Ethernet cable as digital packets, so induced 50/60 Hz noise doesn't bleed into the conversation as hum the way it does on an analog pair; what strong interference can do, especially on damaged or poorly terminated cable, is corrupt frames, which surfaces as packet loss and dropouts. Analog runs are the opposite: an ATA-to-phone pair routed alongside power wiring will happily pick up audible hum. Rerouting cable away from power lines, replacing damaged runs, or using shielded cable where the environment demands it helps in both cases.

Noise on all calls versus specific phones

If every phone in the office has the same noise issue, look for a shared element in the audio path rather than reaching for a network-wide grounding theory: the trunk gateway, the PBX or a shared media resource, or the provider's side of the calls. Because Ethernet ports are transformer-isolated, a building-wide ground loop propagating over the data network is an unlikely diagnosis without measurable electrical evidence of a wiring fault. If the noise is present even on internal phone-to-phone calls, suspect the PBX or media server; if it appears only on external calls, suspect the gateway or trunk (see below).

If only one phone has the noise, the problem is specific to that phone, its cable, its switch port, or its immediate environment. The troubleshooting approach is to isolate: swap the phone with a known good phone to determine if the noise follows the phone (hardware issue) or stays at the location (cable, port, or environmental issue).

Noise on external calls only

If noise appears only on calls to external numbers (especially to landlines), the issue might be at the gateway between VoIP and the PSTN. The gateway converts between digital VoIP audio and the analog or digital signals of the traditional phone network. A poorly configured gateway, a failing line card, or an issue on the PSTN side of the gateway can introduce noise into the audio path.

This is typically on the trunk provider's side and needs to be reported to them with specific call examples. If the noise is only on calls to a specific number or area, the issue might be on the far end carrier's network rather than your trunk provider's.

Noise from the phone hardware

Phones contain speakers and microphones that can develop issues over time. A phone with a speaker that's developing a fault might produce crackling or distortion. A phone with debris in the microphone port might produce a muffled buzz when the user speaks. A phone with a loose component might produce intermittent noise when the phone is bumped.

If the noise is consistent across all calls on a specific phone and you've ruled out cable, switch port, and environmental causes, the phone itself might be failing. Test with a different phone at the same location. If the noise goes away with the replacement phone, the original phone needs to be replaced.

Headset noise

If the noise is only present when a user is on a headset and not when using the handset, the headset is the issue. Wireless headsets, particularly Bluetooth, can introduce noise from interference with other wireless devices. Wired headsets with a damaged cord or a loose connector can produce crackling. USB headsets with driver issues can produce buzzing.

Test with a different headset. If the noise goes away, the original headset is the problem. For wireless headsets, moving the base station away from other wireless devices (WiFi access points, Bluetooth devices) can reduce interference.

Next up: Fax Over IP: Why Faxing Over VoIP Is Unreliable and What to Do About It, the one use case that VoIP was never designed for.