VoIP faxing is fundamentally unreliable — and not because of bad luck. Fax was built for a continuous analog circuit; VoIP is a packet network that destroys the very signal fax depends on. Here's the full technical story.
Frequently Asked Questions
Why does fax not work well over VoIP?
Fax was designed for circuit-switched phone lines that provide a continuous, lossless audio channel. VoIP breaks audio into packets on a shared network — introducing packet loss, jitter, and compression that corrupt the precise analog tones fax machines depend on to communicate.
What is the T.30 protocol and why does it matter for VoIP fax?
T.30 is the ITU standard that governs every Group 3 fax session. It uses a rigid handshake with precise timing requirements (75 ±20ms between signals, hard timeouts under 35 seconds). VoIP's variable latency and packet loss routinely violate these requirements, causing the session to abort.
Does T.38 fix VoIP fax problems?
T.38 helps significantly by converting fax tones into fax-aware data packets instead of raw audio. But it requires both ends of the call to support it, which many carriers still do not. Even with T.38, sustained packet loss can still cause failures — and interoperability between different vendors' implementations is inconsistent.
How reliable is VoIP faxing compared to traditional POTS?
Traditional analog (POTS) fax fails roughly 5% of the time. VoIP fax without optimization fails at 15–20% under normal conditions — and single-page success rates as low as 80% have been observed. Cloud fax services like [mFax](https://mfax.to) bypass VoIP entirely and deliver a 98% success rate using dedicated fax infrastructure.
What codecs work for VoIP faxing?
Only G.711 (uncompressed PCM) is viable for carrying fax audio over VoIP. G.729 compresses audio to 8 kbps — physically incapable of carrying a 9,600 bps fax signal without fatal distortion. You must also disable Voice Activity Detection, echo cancellation, and Comfort Noise Generation.