By Sarah Martinez · Published April 12, 2026 · Updated June 8, 2026 · 8 min read
Faxing over VoIP sounds simple — your phone calls work fine, so why not faxes? In practice, fax with VoIP is one of the most frustrating combinations in business communications. The technology gap between analog fax signals and digital IP networks creates reliability problems that no amount of wishful thinking can paper over.
The good news: there are proven ways to make it work. This guide explains exactly what goes wrong when you try to fax with VoIP, the three methods that actually deliver results, a step-by-step configuration checklist, and the one alternative that eliminates VoIP fax headaches entirely.
Why Faxing With VoIP Is So Difficult
Fax machines were built for the Public Switched Telephone Network (PSTN) — the traditional copper-wire phone system that provides a continuous, dedicated audio circuit for the duration of every call. No sharing, no interruptions, no compression.
VoIP works completely differently. It breaks your voice into tiny data packets, sends them across a shared internet connection, and reassembles them at the other end. For voice calls, this works brilliantly — human hearing tolerates small gaps and delays without noticing. Fax machines have no such tolerance.
There are three specific ways VoIP destroys fax signals:
Packet Loss
Even 1% packet loss — an amount so small you'd never notice on a voice call — can completely fail a fax transmission. Fax machines communicate using precise audio tones (defined by the ITU T.30 standard) and interpret any missing audio as an error that terminates the session. For a deeper look at how this plays out, see our guide on why VoIP faxing can be trouble.
Codec Compression
Most VoIP services use the G.729 codec, which compresses audio down to 8 kbps to save bandwidth. That compression shreds fax tones. Fax requires the uncompressed G.711 codec (64 kbps) to pass its signals intact. Sending fax audio through G.729 is like trying to transmit a precise musical frequency through a megaphone.
Jitter and Timing Sensitivity
VoIP packets don't always arrive in order or at consistent intervals — this variation is called jitter. Fax handshaking relies on exact timing. If packets arrive late or out of sequence, the fax machines lose synchronization and drop the call. A VoIP connection with just 20–30ms of jitter variance can consistently fail fax sessions.
The T.38 Solution
T.38 is an ITU protocol created specifically to address the PSTN-to-IP incompatibility. Instead of trying to pass raw fax audio over VoIP (which fails), T.38 converts fax tones into error-corrected data packets at the point of transmission and converts them back at the destination.
How T.38 Works
When a fax session starts on a T.38-enabled connection:
- The fax machine sends its standard analog tones
- An IP gateway (your ATA device or PBX) intercepts and converts them into T.38 data packets
- Those packets travel across the IP network with redundancy built in — lost packets can be reconstructed from duplicate data
- The gateway at the far end converts the T.38 packets back into analog fax tones for the receiving machine
T.38 essentially builds a fax-over-IP tunnel that shields the transmission from packet loss and jitter. For a technical deep dive, see our T.38 fax protocol explained guide.
T.38 Limitations
T.38 isn't a silver bullet. Its effectiveness depends on:
- Both sides supporting it — your VoIP provider, your ATA/gateway, and (for server-to-server fax) the receiving network all need T.38 support
- Consistent implementation — T.38 is implemented inconsistently across providers, causing unpredictable failures even when support is nominally present
- Network quality — T.38 tolerates more packet loss than G.711 passthrough, but extremely poor connections will still fail
Not All VoIP Providers Support T.38
Before investing in T.38-compatible hardware, confirm your VoIP carrier explicitly supports T.38 fax relay — not just "fax-capable." Many carriers support fax only on specific trunk types or charge extra for T.38 service.
Three Methods to Fax With VoIP
There are three practical approaches, each with different hardware requirements and reliability trade-offs.
| Method | Hardware Needed | Reliability | Best For |
|---|---|---|---|
| ATA + T.38 | Analog Telephone Adapter | Moderate–Good | Existing fax machine, moderate volume |
| Cloud/Online Fax | None (or smartphone) | Excellent | Any use case — simplest option |
| VoIP PBX Fax Server | PBX with fax module | Good (with T.38) | Organizations with in-house PBX |
Method 1: Analog Telephone Adapter (ATA)
An Analog Telephone Adapter connects your traditional fax machine to your VoIP network. The ATA handles the conversion between your fax machine's analog signals and the VoIP provider's IP connection. Models that support T.38 (such as the Cisco SPA112 or Grandstream HT802) handle the protocol conversion automatically.
This is the most common approach for businesses that already own fax hardware and want to continue using it after migrating to VoIP. For full setup instructions, see our VoIP fax machine guide.
Method 2: Cloud-Based Online Fax (Recommended)
The most reliable way to fax over a VoIP environment is to route faxes entirely around VoIP. Cloud fax services like mFax.to send and receive faxes over dedicated fax infrastructure — completely independent of your VoIP setup.
You send documents from a phone, browser, or email. The service handles the PSTN connection on the backend. No hardware changes, no codec headaches, no packet loss risk.
This approach also works for receiving: your dedicated fax number routes incoming faxes directly to your inbox as PDF attachments.
Method 3: VoIP PBX with Fax Server
Organizations running an on-premise PBX (such as 3CX, Asterisk, or FreePBX) can configure a dedicated fax extension with T.38 support. Incoming faxes are detected automatically and forwarded to email as PDF files. Outgoing faxes are queued through a fax server module.
This method provides good reliability when configured correctly — but requires technical expertise and ongoing maintenance. For a broader overview of how all these approaches fit together, see our guide on Fax over IP (FoIP).
How to Configure Your Fax Machine for VoIP
If you're going with the ATA route, these six settings significantly improve fax-over-VoIP reliability. Apply them in order — each one addresses a specific failure mode.
Switch to G.711 Codec
Log into your VoIP adapter or PBX settings and set the audio codec to G.711 (a-law or u-law). Disable G.729 and any other compressed codec. G.711 is uncompressed and passes fax tones intact. This single change fixes the majority of VoIP fax failures.
Reduce Fax Speed to 9600 bps
On your fax machine, lower the transmission speed (baud rate) from its default (often 14400 or 33600 bps) to 9600 bps. Apply this to both sending (Tx) and receiving (Rx). Lower speeds are more forgiving of minor network delays and significantly increase first-attempt success rates.
Disable Error Correction Mode (ECM)
ECM is enabled by default on most fax machines. Over a real phone line it improves quality — over VoIP it triggers excessive retransmission requests that compound timing problems. Turn ECM off in your fax machine settings.
Enable QoS on Your Router
Configure your router's Quality of Service (QoS) settings to prioritize VoIP traffic. This prevents fax transmissions from competing with video streams or file downloads for bandwidth. Without QoS, a Netflix session on the same network can kill a fax mid-page.
Connect Directly — No Splitters
Plug the fax machine directly into the ATA's phone port. Remove any intermediate devices — telephone splitters, answering machines, caller ID units — between the ATA and the fax machine. Each device adds signal processing that can interfere with fax tones.
Set Resolution to Standard
Change your fax machine's resolution setting from "Fine" or "Super Fine" to Standard. Higher resolutions increase the amount of data per page, which increases transmission time and failure risk over unreliable connections.
Still Failing After All Six Steps?
If faxes still fail consistently after applying all six settings, your VoIP provider's network quality may be the limiting factor — not your hardware. Check whether they explicitly support T.38 fax relay. If they don't, a cloud fax service is your most reliable path forward. See a full diagnosis guide in our VoIP fax problems article.
VoIP Fax vs. Cloud Fax: Which Is Right for You?
Not every situation calls for the same solution. Here's a straightforward decision framework:
| Scenario | Best Approach |
|---|---|
| Occasional faxing (under 20/month) | Cloud fax — simplest, no setup |
| Existing fax machine, light VoIP issues | ATA + T.38 configuration |
| High-volume or mission-critical faxing | Cloud fax or dedicated fax line |
| Healthcare / HIPAA environment | mFax Business with HIPAA compliance |
| Large organization with on-premise PBX | VoIP PBX fax server |
| Frequent failures, unreliable VoIP provider | Cloud fax immediately |
The core trade-off: ATA + VoIP fax preserves existing hardware but requires ongoing configuration and tolerates periodic failures. Cloud fax requires no hardware and delivers consistent reliability, but introduces a monthly cost.
For most businesses — especially those with healthcare, legal, or compliance faxing needs — the reliability of cloud fax outweighs the cost. For light faxing in a technically controlled environment, a well-configured ATA works fine.
Common VoIP Fax Problems and Quick Fixes
Even with the best configuration, problems appear. Here are the most frequent issues and their first-line solutions:
| Problem | Most Likely Cause | Fix |
|---|---|---|
| Fax fails to connect | VoIP voicemail stutter tone confusing fax machine | Disable stutter dial tone; connect fax before dial tone appears |
| Fax connects but drops mid-page | Packet loss or jitter spike | Check network; enable QoS; reduce baud rate to 7200 bps |
| Fax completes but destination says nothing received | Codec mismatch | Confirm G.711 is active on both ends; request G.711 passthrough from your VoIP provider |
| Works for short faxes, fails for long documents | Bandwidth or timeout | Use cloud fax for multi-page documents; reduce resolution |
| Fax works sometimes, fails unpredictably | Intermittent packet loss | Run a packet loss test on your connection; upgrade internet or switch to cloud fax |
| No dial tone on fax line | ATA misconfigured | Verify ATA has registered with VoIP provider; check for firmware updates |
For a comprehensive problem-by-problem diagnosis, see our dedicated VoIP fax problems guide.
The Simplest Path: Skip the VoIP Complexity
VoIP fax can work — but it takes effort to configure, occasional re-tuning as network conditions change, and acceptance that some transmissions will still fail. For businesses where a failed fax is a real problem (missed contract signatures, delayed medical authorizations, late IRS submissions), that's an unacceptable risk.
mFax.to routes faxes completely independently of your VoIP system. Upload a PDF, enter a fax number, and send — from your phone or browser, in under two minutes. Incoming faxes arrive as PDFs in your inbox. Five million users rely on it as their fax-from-anywhere solution.
For teams and compliance-sensitive environments, mFax Business adds HIPAA-ready infrastructure, virtual fax numbers, team accounts, and audit logs — starting at about $9/mo (billed annually). There are no rigid fixed tiers: you build your own plan with a live calculator, choosing the exact seats and pages you need and paying only for what you use.
Whether you need to fix your VoIP fax today or replace it entirely, the right setup comes down to your volume, your VoIP provider's capabilities, and how much reliability you need.