● SIP/2.0 200 OK  |  RTP: flowing  |  New guides added weekly

Troubleshooting · Symptoms

Static, Hum and Crackling: Identifying the Noise

By the VoIP Cost Guide Editorial Team  |  Last updated: October 2026

Noise complaints sound vague — 'there's static on the line' — but each noise is manufactured by a specific mechanism, and the mechanism determines whether you're holding a screwdriver (analog wiring, grounding, a dying handset cord) or reading a capture (packet loss wearing an acoustic disguise). Pure IP paths do not generate analog noise; so the first question is whether the call path still contains an analog segment at all.

Listen first, with intent: steady hum, intermittent crackle, and digital-sounding chirps are three different faults that happen to share a ticket queue.

A field guide to noises

NoiseCharacterLikely sourceFirst move
Hum / buzz (steady)Constant 50/60 Hz tone under the callGround loop or induced mains hum on an analog segment (ATA, analog gateway, long unshielded runs near power)Isolate the analog segment; check grounding and cable routing vs power
Crackle / pops (intermittent)Random snaps, often when something movesFailing handset cord, oxidized jack, loose punch-down — flex the cord during a call and listenSwap cord/handset; re-terminate the jack
Static bursts tied to activityNoise when appliances, HVAC or elevators startEMI ingress on analog cabling near motors/powerRe-route or shield the analog run; move the ATA closer to the phone
Chirps, squeaks, watery artifactsDigital, warbly, tracks speechNot analog at all: packet loss + PLC, or a low-bitrate codec strugglingCapture and read loss/jitter (see the robotic-voice guide)
Noise on one phone only, all callsSame noise everywhere that phone goesThe phone/handset itselfSwap test — the fastest experiment in telephony

Why analog tails survive inside 'IP' systems

Many VoIP deployments still contain analog segments: fax and courtesy phones on ATAs, analog trunks into a gateway, overhead paging interfaces, an elevator phone. Those tails inherit every analog pathology — and their noise then gets digitized faithfully and delivered to clean IP endpoints, which is why a user on a pure IP phone can hear hum generated three devices away. The diagnostic move is subtractive: make test calls that include and exclude the analog segment (IP phone to IP phone vs IP phone to the ATA extension). Noise that exists only across the analog boundary belongs to the analog world: cables, grounding, the ATA, or the device beyond it.

Isolation sequence

  1. Characterize the noise with the table: steady, intermittent, movement-linked, or digital. Record an example (many systems can record the call) — noises described in words mutate between tellings.
  2. Scope it: one phone, one site, one call type? IP-to-IP test call vs a call crossing the analog segment — the comparison bisects the search space.
  3. For analog suspects: swap the handset cord first (the single most common crackle source), then the handset, then re-terminate the jack; check ATA grounding and reroute analog runs away from power and ballasts.
  4. For digital artifacts: leave the screwdrivers alone and capture — loss and jitter statistics will name the network fault (robotic-voice workflow).
  5. Verify on the original failing call path with the original listener; noise judgments are personal, so the reporter confirms the fix.

Frequently asked questions

Why do I hear hum only on calls to one branch office?
Because that path includes that office's analog segment or gateway — the hum is generated there and carried to you digitally. Your clean local calls already proved your side innocent; send them this guide's table and the recording.
Can a PoE switch cause hum?
Indirectly: poor power quality or a failing switch can inject noise into an ATA or phone's audio path, but classic mains hum belongs to grounding on analog runs. If hum follows one switch port across devices, test the port; if it follows the analog run, fix the run.
The crackle happens when the desk phone is touched.
That is nearly a confession: a fatigued handset cord or a cracked handset. Cords are consumables — replace at the first crackle rather than diagnosing quarterly.

Sources and further reading

Related guides

Disclaimer: This guide is educational information based on published VoIP standards and professional practice, not engineering advice for your specific system. VoIP pricing, taxes and fees change and vary by provider and location — verify current figures with providers before purchasing. If your phone system supports emergency calling, work with your provider or a qualified VoIP engineer for changes that affect E911.