By Michael Chen · Published March 21, 2026 · Updated March 21, 2026 · 12 min read
Your fax machine works perfectly. Your new VoIP phone system doesn't. Transmissions fail mid-page, calls drop during the handshake, or faxes come through garbled. This is one of the most common breakdowns when businesses migrate from traditional PSTN lines to VoIP — and it has a specific fix: the VoIP fax gateway.
A VoIP fax gateway sits between your analog fax machine and your IP network, translating signals in real time so faxes travel reliably over the internet. This guide covers exactly how it works, which protocol it uses, what devices to buy, how to set one up, and when it makes more sense to skip the hardware entirely.
If you need to send faxes without the hardware complexity, mFax.to lets you send and receive faxes from any phone or browser in under 2 minutes — no gateway, no SIP configuration, no fax machine required.
What Is a VoIP Fax Gateway?
A VoIP fax gateway is a device (hardware or software) that converts analog fax signals into IP-compatible digital packets — and back again on the receiving end. It gives your traditional fax machine a way to operate over a VoIP or internet-based phone system.
The gateway acts as a real-time protocol translator. Your fax machine speaks analog T.30 over a circuit-switched PSTN line. Your VoIP network speaks SIP over packet-switched IP. Neither protocol is natively compatible with the other. The gateway bridges that gap, invisibly, so both endpoints behave as if they're on a traditional phone line.
Without a gateway, most fax-over-VoIP attempts fail — and the reasons are specific.
Why Faxes Fail Over VoIP Without a Gateway
Traditional fax uses the T.30 protocol, built for circuit-switched PSTN: a dedicated, continuous connection with no compression and consistent timing. VoIP networks are packet-switched — they break data into chunks, compress it, and route each packet independently across shared infrastructure.
Five things T.30 assumes become problems on VoIP:
| Problem | How It Breaks Fax |
|---|---|
| Codec compression | G.729 modifies audio frequencies; fax tones are frequency-sensitive and become unrecognizable |
| Packet loss | Even 1–2% packet loss disrupts T.30 timing and causes handshake failure |
| Jitter | Fax machines sync clocks to the incoming signal; variable packet delay breaks that sync |
| Latency spikes | T.30 has strict timeout windows; a packet arriving 200ms late can cause the machine to hang up |
| Echo cancellation | Network equipment can mistake fax CNG tones (1,100 Hz) for line echo and cancel them |
The result: failed transmissions, garbled pages, or random mid-fax disconnects. A VoIP fax gateway solves all five problems by switching from audio transmission to the T.38 protocol — designed specifically for fax over IP.
Works sometimes, fails sometimes?
If your fax succeeds about 60% of the time on VoIP, you're likely on G.711 passthrough — uncompressed audio without T.38. G.711 is better than G.729, but it has no error correction for fax. Any packet loss causes failure. T.38 with a proper gateway adds redundancy and error recovery that makes success consistent.
How a VoIP Fax Gateway Works
The T.38 Protocol
T.38 is the ITU-T standard for transmitting fax over IP networks. Rather than encoding fax tones as audio and hoping they survive packet routing, T.38 extracts the underlying fax data from the analog signal and transmits it as structured digital packets — closer to how email sends a document than how VoIP sends a voice call.
Our full T.38 protocol explainer covers the architecture in depth. The key points:
- No audio encoding — fax data travels as pure digital information, not compressed sound
- Built-in redundancy — each packet carries the current data plus 1–2 previous packets, enabling recovery from up to 10% packet loss
- Lower bandwidth — T.38 uses roughly 10× less bandwidth than G.711 passthrough (~10–14 kbps vs. ~64 kbps)
- Greater network tolerance — latency up to 1,000ms and jitter up to 300ms are acceptable, versus ≤30ms jitter for G.711
Signal Flow: End to End
Here is what happens when you send a fax through a VoIP fax gateway:
- Your fax machine dials the destination number and outputs an analog T.30 signal via its RJ11 port
- The gateway's FXS port receives the analog signal
- The gateway's internal fax modem demodulates the PCM audio into raw fax data
- The call begins as a standard SIP invite using G.711 audio (normal VoIP)
- When the gateway detects CNG fax tones (1,100 Hz), it sends a SIP re-INVITE proposing a switch to T.38
- The remote endpoint acknowledges with 200 OK — both sides are now in T.38 mode
- Fax data flows as T.38 UDPTL packets across the IP network
- The receiving gateway reverses the process, reconstructing the analog signal for the destination fax machine
T.38 vs G.711 Passthrough
Some VoIP setups use G.711 passthrough as a fallback — fax tones travel as uncompressed audio without switching to T.38. Here is how the two compare:
| Factor | T.38 Fax Relay | G.711 Passthrough |
|---|---|---|
| Packet loss tolerance | Up to 10% (with redundancy) | ~0% |
| Jitter tolerance | ≤300ms | ≤30ms |
| Bandwidth | ~10–14 kbps | ~64 kbps |
| Error correction | Built-in redundancy | None |
| Reliability | High | Low–Medium |
| Setup complexity | Moderate | Simple |
Use T.38 whenever possible. G.711 passthrough is a last resort for cases where T.38 negotiation fails or your VoIP provider does not support the protocol switch.
Types of VoIP Fax Gateways
ATA (Analog Telephone Adapter)
The most common type for small businesses. An ATA provides 1–2 FXS ports, connects your fax machine to a VoIP network, and registers a SIP account with your provider. Setup takes about 10 minutes via a web browser.
Best for: 1–2 fax machines, small offices
Price range: $35–$100
Examples: Grandstream HT802, Cisco ATA 191, Obihai OBi302
Multi-Port Analog Gateway
Larger rack-mountable units with 4–24 FXS and/or FXO ports. Designed for office environments with multiple analog fax machines, or for migrating an entire PBX to VoIP while keeping existing hardware.
Best for: Mid-size to enterprise offices with multiple fax lines
Price range: $150–$2,000+
Examples: Grandstream GXW4104, AudioCodes MediaPack MP114, Patton SmartNode SN4112
Software / Virtual Fax Gateway
A software component running on a PBX server (Asterisk, 3CX, FreePBX). Handles T.38 negotiation in software with no physical ATA required — useful when your endpoints are already IP-based.
Best for: All-digital environments, cloud PBX setups
Price: Included in PBX or open-source
FXS vs FXO: What the Port Labels Mean
Every gateway spec sheet uses these terms. Here is the practical difference:
| Port | Behaves Like | What Connects to It |
|---|---|---|
| FXS (Foreign Exchange Subscriber) | A phone company line — provides dial tone and ring voltage | Your analog fax machine |
| FXO (Foreign Exchange Office) | A telephone device — receives a line | PSTN/analog line from the wall |
For most fax-over-VoIP setups, you need an FXS gateway: your fax machine plugs into the FXS port, and the gateway registers a SIP account with your VoIP provider. FXO ports are used when you need to route PSTN lines into a VoIP system — a different (though sometimes combined) use case.
Top VoIP Fax Gateway Devices
Grandstream HT802 — Best Value
~$45–$65 | 2 FXS ports
The most widely deployed ATA for SMB fax. Full T.38 support, configurable adaptive jitter buffer, G.711 a-law/u-law, and a clean browser-based web interface. Reliable for standard office fax volumes and straightforward to configure. The default choice for most small business deployments.
Grandstream GXW4104 — Best for Multi-Line Offices
~$150–$200 | 4 FXS ports, rack-mountable
Scales to 4 simultaneous fax lines with the same T.38 reliability as the HT802. Enterprise build quality, SNMP monitoring support, and redundant power supply options for larger installations.
Obihai OBi302 — Best for Home/SOHO
~$70–$100 | 2 FXS ports + built-in router with QoS
The OBi302 includes a 2-port WAN/LAN router with built-in traffic prioritization — ideal if you cannot configure QoS on your main router. QoS automatically prioritizes fax and voice traffic, reducing jitter without any additional networking setup.
AudioCodes MediaPack MP114 — Best Enterprise Mid-Range
~$150–$300 | 4 FXS + 4 FXO ports
AudioCodes equipment is standard in enterprise and service-provider environments. The MP114 handles both PSTN-to-VoIP and analog fax-to-VoIP in one unit. Features include HTTPS management, detailed call logging, and proven interoperability with major SIP carriers.
Patton SmartNode SN4112 — Most Reliable
~$300–$500 | 2 FXS ports
Carrier-grade construction and the most consistent T.38 performance under demanding conditions. The standard choice for healthcare clinics, law firms, and financial institutions where fax reliability is non-negotiable. Significantly more expensive than Grandstream — justified only when failure is not an option.
Community consensus on device selection
Across 3CX, Asterisk, and VoIP-Info community forums: Patton = most reliable, most expensive. Grandstream = best value for most deployments. AudioCodes = solid enterprise middle ground. Start with the Grandstream HT802 for any small office — it handles the majority of use cases at a fraction of Patton's cost.
VoIP Fax Gateway vs Cloud Fax
A VoIP fax gateway preserves your physical fax machine while connecting it to an IP network. Cloud fax eliminates the fax machine entirely — you upload a document, the service converts and delivers it digitally, and you receive incoming faxes by email or mobile app.
| Factor | VoIP Fax Gateway | Cloud Fax (e.g., mFax.to) |
|---|---|---|
| Physical fax machine | Required | Not needed |
| Upfront hardware cost | $40–$2,000 | None |
| Monthly cost | VoIP line + SIP trunk fee | $10–$30/month |
| Transmission type | Real-time T.38 | Store-and-forward |
| Reliability | Depends on network quality | High (built-in retry logic) |
| IT expertise required | Moderate–High | None |
| HIPAA compliance | Requires BAA from VoIP provider | Requires BAA from fax service |
| Send from mobile/browser | No | Yes |
| Delivery confirmation | Basic | Comprehensive audit log |
Choose a VoIP fax gateway when you have regulatory requirements for a dedicated fax line, existing fax machine infrastructure you need to preserve, or very high fax volumes where hardware-level throughput matters.
Choose cloud fax when you want to eliminate hardware entirely, send faxes from a phone or browser, or need detailed delivery tracking without configuring network gear. mFax.to handles sending and receiving from any device — no ATA, no SIP trunk, no jitter buffer settings. Over 5 million users fax this way every day.
For the full picture on hardware-free approaches, see our guide on faxing without a landline.
How to Set Up a VoIP Fax Gateway
The following walkthrough covers standard ATA configuration. The Grandstream HT802 is used as the example, but the steps apply to most devices — Obihai, Cisco ATA, and AudioCodes all follow the same sequence.
Connect the hardware
Plug your fax machine into the LINE 1 FXS port on the ATA using a standard RJ11 cable. Connect the ATA's LAN port to your router via Ethernet. Power on the device and wait 60 seconds for it to boot.
Access the web interface
Find the ATA's IP address by checking your router's DHCP client list, or pick up a phone connected to the ATA and dial *** to hear the IP read aloud. Enter that IP in a browser. Log in (Grandstream default: admin / admin — change this password immediately).
Enter SIP account credentials
Navigate to Account 1 → General Settings. Enter your VoIP provider's SIP server hostname or IP, your SIP username, and password. Set the SIP port (typically 5060). Save and confirm the registration status shows Registered before proceeding.
Enable T.38 fax support
Go to Account 1 → Codec Settings. Enable T.38 Fax. Set T.38 maximum datagram size to 512 bytes. Configure redundancy: LS-redundancy = 3, HS-redundancy = 3. Enable ECM (Error Correction Mode) for both transmit and receive.
Set codec and disable voice features that break fax
Set G.711 u-law or a-law as the only codec for this account. Remove G.729 entirely — compressed codecs destroy fax tones. Disable Voice Activity Detection (VAD), silence suppression, and echo cancellation on fax ports. Set the jitter buffer to adaptive, 100–200ms.
Configure the fax machine itself
On the fax machine: set transmission speed to 9,600 bps (reduces sensitivity to timing issues compared to 14,400 bps). Enable ECM if available. Disable call waiting. Reduce the number of redial attempts to avoid queuing failed faxes on a congested line.
Test and verify
Send a test fax to a known working number. For a full technical verification, capture packets with Wireshark and look for this SIP sequence: INVITE → 200 OK (G.711) → re-INVITE with T.38 SDP → 200 OK → UDPTL packet stream. If the re-INVITE appears but receives no 200 OK, your provider may not support T.38 — contact them to confirm before troubleshooting further.
Disable SIP ALG on your router first
Many consumer and small-business routers enable SIP ALG (Application Layer Gateway) by default. SIP ALG rewrites SIP headers to assist NAT traversal — but it frequently corrupts the re-INVITE that switches a call from G.711 to T.38, causing silent failures. Disable SIP ALG before debugging anything else. This single step resolves a large percentage of T.38 negotiation failures.
Verifying T.38 Support from Your Provider
Not all VoIP providers support T.38. Before purchasing a gateway, confirm:
- Does the provider support T.38 on SIP trunks? (ask explicitly — "passthrough" is not the same as T.38 relay)
- Does the provider pass SIP re-INVITEs through their network without modification?
- Is there a dedicated fax DID available, or will you share a voice DID?
Major carriers that support T.38: Twilio (with explicit T.38 trunk settings), Vonage, RingCentral, Flowroute, Bandwidth. If your provider does not support T.38, G.711 passthrough is the fallback — less reliable but sometimes workable on low-loss networks.
Common VoIP Fax Gateway Problems
Even a correctly configured gateway encounters issues. Here are the most frequent causes and fixes. For a broader troubleshooting reference, see our guide on VoIP fax problems and how to fix them.
T.38 Negotiation Fails
Symptom: Call connects, fax immediately fails or hangs at the handshake
Most likely cause: SIP ALG on the router is corrupting the re-INVITE
Fix: Disable SIP ALG. Confirm your VoIP provider supports T.38. Check firewall rules — SIP traffic on port 5060 and RTP/UDPTL on ports 10000–20000 must pass through. If T.38 is unavailable from the provider, fall back to G.711 passthrough.
Intermittent Partial Pages or Garbled Output
Symptom: Some faxes succeed; others arrive with missing sections or corrupted content
Cause: Packet loss or jitter exceeding T.38 redundancy limits
Fix: Enable T.38 redundancy (LS=3, HS=3 if not already set). Run a network quality test — look for any packet loss above 0% and jitter above 30ms. Configure QoS on your router to prioritize RTP/UDPTL traffic over general internet traffic. On a shared business internet connection, this alone often resolves intermittent failures.
Fax Machine Hangs Up During Handshake
Symptom: Connection established, machine disconnects after 20–30 seconds
Cause: Speed negotiation failure or T.30 timeout exceeded
Fix: Set fax machine TX speed to 9,600 bps or 4,800 bps. Verify G.729 is not in the active codec list. Confirm echo cancellation is disabled on the ATA's fax port.
"Far End Cannot Receive at This Image Size"
Symptom: Error appears on fax machine display during send
Cause: Document dimensions exceed standard 8.5×11 or A4 fax format
Fix: Resize the document to standard dimensions before sending. Our free PDF optimizer handles this in seconds — no software installation required.
Consistent Total Failure Across All Faxes
Symptom: Every fax fails, regardless of destination
Cause: G.729 codec selected instead of G.711, or VAD/silence suppression active
Fix: Remove G.729 from the ATA codec list entirely. Confirm silence suppression is off. Verify the SIP account is registered (an unregistered account silently drops outbound calls on some ATAs).
Who Needs a VoIP Fax Gateway?
Healthcare Organizations
Over 70% of U.S. hospitals and medical practices still rely on fax for patient records, referrals, lab results, prior authorizations, and prescription routing — an estimated 9 billion fax pages transmitted annually in U.S. healthcare alone. When these organizations migrate to VoIP, a fax gateway preserves existing clinical workflows without requiring new fax numbers or process changes. Real-time T.38 transmission is inherently HIPAA-safe because documents travel point-to-point without intermediate storage on third-party servers.
See our HIPAA compliant fax guide for the full compliance framework.
Legal Firms
Many courts and government agencies still require faxed filings and accept faxed signatures as legally binding. Law firms migrating to VoIP need a fax gateway to maintain compliance with court filing rules and to preserve chain-of-transmission documentation for attorney-client communications.
Financial Services and Insurance
Banks, insurance carriers, and mortgage lenders handle loan applications, claims forms, and policy documents via fax — partly due to regulatory requirements (SOX, GLBA) and partly because legacy partner systems still expect fax. A VoIP gateway lets these organizations modernize their phone infrastructure without disrupting fax-dependent workflows.
Businesses Replacing POTS Lines with VoIP
The most common scenario: a company signs up for a cloud PBX or SIP trunking service and discovers on Day 1 that the existing fax machine no longer works reliably. A $55 ATA is usually the fastest and cheapest resolution.
How much fax volume justifies hardware?
If you send fewer than 50 fax pages per month, a cloud fax service is almost certainly cheaper and simpler than gateway hardware. mFax.to costs less than most SIP trunks, requires zero configuration, and lets you send from your phone. The VoIP gateway path makes sense when you have high volume, dedicated line requirements, or existing fax machine infrastructure worth preserving.
Cost Breakdown
| Solution | Upfront Cost | Monthly Cost | Est. Year-1 Total |
|---|---|---|---|
| ATA (Grandstream HT802) + SIP trunk | ~$55 | $10–$20/mo | ~$175–$295 |
| 4-port gateway + SIP trunks | ~$180 | $30–$60/mo | ~$540–$900 |
| Patton enterprise gateway + SIP trunk | ~$400 | $20/mo | ~$640 |
| Traditional POTS fax line (what you're replacing) | $0 | $40–$60/mo per line | $480–$720 |
| Cloud fax (mFax.to) | $0 | $10–$30/mo | $120–$360 |
Businesses replacing POTS lines with a SIP trunk plus ATA typically save 60–80% on monthly fax line costs. A $55 Grandstream HT802 pays for itself within 1–2 months of eliminated POTS fees.
The fax services market was valued at $3.31 billion in 2024 and is projected to reach $4.47 billion by 2030 — fax is not going away, and transitioning it to run over VoIP infrastructure is increasingly the default approach.
Skip the Hardware: Send Faxes from Your Phone
A VoIP fax gateway is the right answer when you have dedicated line requirements, physical fax machine infrastructure worth preserving, or real-time, high-volume compliance faxing. For the majority of small businesses and individuals, cloud fax eliminates the hardware, T.38 configuration, SIP ALG headaches, and per-port limitations entirely.
mFax.to lets you send and receive faxes from any phone, tablet, or browser. Upload a PDF, enter the fax number, send. You get a delivery confirmation, a dedicated fax number, and full send/receive history — no ATA, no SIP trunk, no Wireshark required. With over 5 million users and a 4.8-star App Store rating, it handles every use case a VoIP gateway covers, and several it cannot.
For those already dealing with a broken fax setup, our VoIP fax problems guide walks through every failure mode in detail — or mFax.to lets you skip the troubleshooting entirely.