VoIP background noise: why calls pick it up and how to fix it

Background noise on a VoIP call is removed at one of three software layers: the softphone's own noise switch, the operating system's microphone chain, or a dedicated AI filter installed as a virtual device. This guide tells you which layer to use, in which order, for which noise — with each app's actual capabilities checked against vendor documentation on 2026-09-20.

Where the noise actually enters

Noise reaches a business call from exactly three directions, and the fix is different for each — so diagnose before you install anything.

1. Your side (near end). Your microphone hears the keyboard, the street, the dog, the open-plan office, and the softphone transmits all of it. This is the direction you control completely, and it's what the rest of this page fixes. It's also the direction that damages you professionally: you're the noisy one on the customer's speaker.

2. Their side (far end). The caller's noise arrives already mixed into their voice. You cannot reach their microphone, but you can filter what your speaker plays — more on that below.

3. The line itself. Crackle, robotic stutter, underwater warble and dropouts are not acoustic noise at all — they're network artifacts: packet loss, jitter, or a codec having a bad day. No noise remover fixes these. If your "noise" appears only mid-call and sounds digital rather than environmental, read our plain-language guide to VoIP codecs and noise before touching mic settings.

Layer 1 — the switch your softphone already ships

Always start here: it's free, it's one click, and vendors have quietly gotten good at it. The catch is that "built in" means wildly different things across business phone apps. Here is the state of the six we track, from each vendor's own documentation:

Two honest observations about that table. First, the built-ins that exist are genuinely worth using — they cost nothing and they pay us nothing, and for steady noise in a reasonably quiet room they're often the whole fix. Second, the pattern of gaps is consistent: web clients, mobile apps and older versions are where built-in noise reduction quietly doesn't apply. If your team lives in a browser tab or on version-frozen desktops, assume you have less protection than the marketing page implies.

Layer 2 — the OS microphone chain

The operating system touches your audio before any softphone does, and three of its habits create "mystery noise" that no in-app switch fixes:

• Wrong input device. The softphone is on the laptop's internal mic array — which hears the whole room — while you talk into a headset. The single most common cause of a suddenly-noisy line after a reboot or dock change.
• Input level too hot. A gain slider near maximum amplifies the room along with your voice, then the codec compresses the mess together. Backing input level down to the middle of the range is a two-minute improvement.
• OS "enhancements" fighting the app. Platform-level processing stacked under an app's own processing can produce pumping, warble, or a voice that fades mid-word. One layer should own the job — see our note on double suppression.

The full walk-through — device pickers, levels, boost, AGC, and the settings that reset themselves — is in the softphone mic settings guide.

Layer 3 — a dedicated AI filter as a virtual device

When the app has no switch (3CX, most SIP softphones, Vonage's VBC app) or the switch can't cope (voices, barking, clattering dishes), the working pattern is a virtual audio device: software that installs as "Krisp Microphone" / "Krisp Speaker," removes noise in real time, and passes clean audio to whatever app you point at it. Because the filtering happens at the device level, the softphone doesn't need to support anything — if it has a microphone picker, it works.

1. Your microphone
2. Virtual device: noise removed here
3. Any softphone with a mic picker

Krisp is the tool we point to for this job, for documented reasons rather than vibes: its help center publishes setup guides for RingCentral and Vonage Business specifically; its own site describes the exact virtual-device pattern above; and its noise models are the same technology Vonage chose to embed in its contact-center product. Pricing, the fine print on the free tier, and the softphone-specific setup order are all in Krisp for VoIP calls.

One rule when you add a layer-3 tool: turn the app's own suppression off. Two filters guessing at the same audio make each other worse — Aircall's docs warn about exactly this, and Dialpad's auto-disable behavior exists for the same reason.

The twenty-minute fix, in order

1. Name the noise. Steady (fan, hum, hiss)? Intermittent (keyboard, voices, dog)? Digital (crackle, stutter)? Steady is easy, intermittent needs AI, digital means network — different page.
2. Confirm the input device. In the softphone's audio settings, make sure the mic selected is the one near your mouth, not the laptop array. Do the same check in the OS.
3. Set the level, kill the boost. Input gain to roughly the middle; microphone boost off unless you're inaudible without it. Details in the mic settings guide.
4. Flip the app's built-in switch. Find your app in the table above and follow its guide to the exact menu. If the built-in solves it, stop here — you're done for free.
5. Test against your real noise. Record a snippet or call a colleague while typing, with the fan on, with the door open. The built-ins pass quiet-room tests easily and fail real rooms.
6. Add the virtual-device layer if it failed. Install the AI filter, select its virtual mic in the softphone, and switch the app's own suppression off so exactly one filter owns the call.
7. Re-test the same way. Same typing, same fan, same door. If voices still leak through, check you're filtering the right direction — mic for what they hear, speaker for what you hear.
8. Write down what you changed. Softphone updates and OS updates both reset audio settings more often than any vendor admits. Thirty seconds of notes saves the next hour of re-diagnosis.

When the noise is coming from the caller

You can't fix their microphone, but you have two real options. First, a virtual-device filter that processes the speaker direction — Krisp's speaker-side noise removal cleans what you hear, which is a sanity-saver for anyone taking calls from warehouses, cars and kitchens all day. Second, if you run a support or sales floor on a contact-center platform, inbound cleanup may already be a checkbox: Vonage Contact Center's Krisp-powered feature filters both the agent and caller directions, per Vonage's 2024 announcement. For an individual taking ordinary business calls, speaker-side filtering is the practical answer.

Why phone calls make noise sound worse than meetings do

A surprising amount of "my VoIP calls are noisy" is really "my VoIP calls are narrowband." When a call leaves your phone system for a landline or mobile network, it often gets squeezed through G.711 — an 8 kHz-sampled codec standardized in 1972 — and every hiss and rumble your mic sends gets baked into that thin, telephone-sounding channel where the ear notices it more. Wideband codecs like Opus and G.722 are kinder, but you don't control which leg of the call uses what. The practical conclusion: clean audio before it hits the codec. That's the entire argument for layers 1–3 living on your machine, and the codec guide explains the rest without math.

What noise removal honestly can't do

Worth stating plainly, because vendors rarely do:

• It can't repair network damage. Packet loss and jitter artifacts aren't noise; a filter can't restore audio that never arrived.
• It can't unclip a distorted mic. If your input level is slammed, the distortion is part of the "voice" as far as any filter is concerned. Fix gain first.
• It can't make a bad room sound treated. Heavy reverb confuses suppression models; they remove noise, not echo-y room character.
• It processes your call audio. Any noise filter — built-in or added — sits in the path of a live conversation. If your calls carry confidential material, read the vendor's processing and privacy documentation before deploying, especially org-wide.

The layer-3 tool for softphones

Krisp installs as a virtual mic and speaker and works with any softphone that has a device picker — 3CX, Zoiper, VBC, the lot. Its help center documents RingCentral and Vonage setups specifically. 7-day free trial, no card required; paid plans from $8/month billed annually ($16 month-to-month), checked 2026-09-20.

Try Krisp free for 7 days → Sponsored line: subscribe through this button and Krisp may pay LineSide a commission. It never changes what we write; steps 1–5 above are free and come first.

Questions we actually get

Do I need noise cancellation if I already use a headset?

Often yes. A close-talking headset mic reduces room pickup but doesn't eliminate it — keyboards and nearby voices survive. And if the headset does its own noise processing, make sure it isn't stacked with an app filter doing the same job; one layer should own it.

Why did my calls suddenly get noisy when nothing changed?

Something changed. The usual suspects, in order: an OS or app update reset your input device to the laptop mic; a dock or USB re-enumeration swapped devices; an update re-enabled OS enhancements; or a version update moved/renamed the noise toggle. Re-run steps 2–4 above.

Is built-in suppression good enough for customer-facing calls?

In a controlled room, frequently yes — Dialpad's and RingCentral's built-ins are real AI suppression, not token filters. In an uncontrolled room (home with kids, café, open floor), the built-ins fail on exactly the noises that matter most: other voices. Test against your real environment before your customers do it for you.

Will noise suppression make me sound robotic?

Over-aggressive or stacked suppression can — the classic symptoms are word endings clipping off and a "underwater" tail on your voice. The fix is almost always running one good filter instead of two mediocre ones, and keeping input gain sane.

What's the one free change with the biggest payoff?

Selecting the correct microphone in both the OS and the softphone. It outperforms every setting tweak on this page when the app was silently listening to the wrong device — which is more common than anyone likes to admit.

Every per-app claim above is sourced and dated in the individual guides: RingCentral, Dialpad, 3CX, Vonage, Aircall, Zoiper. If a vendor changes something, the guide's checked-date tells you how stale we are.