Faxing Over the Internet: Why Fax Is Hard on VoIP, and T.38

Fax is a 1970s protocol in which two machines whistle at each other with precise timing and negotiate down to whatever both can sustain. On the analog network it was superbly reliable, which is why regulated industries built workflows on it. Then telephony moved to packets, and fax became the awkward passenger: it was engineered around assumptions, constant timing, zero loss, no compression artifacts, that packet networks explicitly do not guarantee.

Why voice survives what fax cannot

A voice call losing a packet drops 20 milliseconds of audio; humans do not notice. A fax losing a packet corrupts data mid-page, and the machines' 1970s error handling responds by retraining, slowing down, or failing the page. Jitter that a voice call absorbs invisibly desynchronizes fax modems entirely. So the same connection can carry flawless voice and unreliable fax, which is roughly the most confusing possible symptom for a business that "already fixed" its network.

T.38: teaching the network to speak fax

T.38 fax relay solves this by ending the pretense. Instead of carrying fax tones as audio, the gateway at each end terminates the fax protocol locally, converts pages to data, and sends that data with retransmission across the IP leg, then re-whistles it to the far machine. Each fax machine believes it is talking analog to a nearby, perfectly behaved peer. When both ends of the path support T.38, fax over IP becomes reliable; when one end does not and the call falls back to fax-as-audio ("G.711 passthrough"), reliability depends on pristine network conditions end to end, which nobody can promise across the public internet.

The practical hierarchy for businesses that must fax

• Cloud fax (best for most): skip the machine entirely. Faxes send and receive as email or browser documents; the provider handles the telephony horror on carrier-grade infrastructure and gives you a searchable archive. This is what regulated industries increasingly use, HIPAA-grade services exist for exactly that reason.
• Machine + ATA with T.38 (when the machine must stay): keep the physical workflow, with an ATA configured for T.38 through a provider that supports it. Reliable when configured properly.
• Machine over plain VoIP audio (avoid): works until it does not, usually on the longest, most important fax of the month.

Why fax refuses to die

Legal and healthcare workflows treat a fax confirmation page as evidence of delivery, counterparties standardized on it decades ago, and a fax number is a stable interface everyone already has. The realistic goal for most businesses is not eliminating fax but containing it: one reliable, archivable channel instead of a machine of mysteries by the copier.

Cannon VoIP's cloud eFax works from email or the portal: email a document from an address or domain you allow and it goes out as a fax, and you are told whether it was delivered. Received faxes land in the same inbox as voicemail and texts and open as a PDF in one click, failed faxes come with a plain-English reason, and the monthly allowance has a usage meter; faxing never stops at the limit. Each fax line can email received faxes as a PDF to the people you choose, and faxes are kept for a year, or seven years if you choose. A fax machine that must stay can connect through an on-site adapter.