What is T.38 Fax?

T.38 is the ITU-T recommendation for sending fax transmissions in real time over IP networks, often called “Fax over IP” (FoIP). Instead of streaming the analog fax tones over a voice codec — which exposes the brittle fax modem signal to every packet-loss event on the IP path — T.38 demodulates the fax data at the gateway, transports it as discrete IP packets with their own error handling, and remodulates it at the destination.

How T.38 works

A traditional fax machine encodes its image as analog tones on a phone line, expecting a circuit-switched path with no loss. T.38 inserts a translation layer:

1. The sending fax connects to a gateway (an ATA, a PBX trunk card, or a SIP trunk provider that supports T.38).
2. The gateway negotiates a “fax relay” session — usually triggered by detection of the V.21 fax preamble or a SIP reINVITE with image/t38 in the SDP.
3. Fax tones are demodulated into the underlying T.30 protocol data: image pages, control messages, and acknowledgements.
4. That data is packaged into T.38 IP packets (UDPTL is the most common transport, with optional FEC and redundancy).
5. The receiving gateway reverses the process and presents tones to the destination fax machine.

The IP transport between the gateways is engineered for tolerance: forward error correction and packet redundancy let T.38 survive moderate jitter and loss that would destroy a raw G.711 fax pass-through.

T.38 vs. G.711 fax pass-through

The two ways to carry fax over IP behave very differently:

• G.711 pass-through: the fax tones travel inside an ordinary G.711 voice stream. Works on a pristine network with very low jitter and zero loss. Falls apart on the public internet or any congested link.
• T.38 relay: tones are demodulated, packetised with redundancy, and reassembled. Survives realistic IP path conditions and is the standard for any production fax requirement.

A reasonable rule of thumb: if the fax path traverses the public internet or any link the operations team does not directly control, use T.38. G.711 pass-through is acceptable only on a tightly engineered managed network.

When fax still matters in 2026

Despite repeated predictions of its end, fax persists in specific verticals where compliance and legacy workflows have outlasted the technology shift:

• Healthcare: HIPAA-compliant document exchange between providers, payers, and pharmacies.
• Legal: court filings and regulated document transfer in jurisdictions where fax is the named acceptable channel.
• Government and public sector: many forms still require fax as a recognised filing method.
• Financial services: secured document exchange under specific compliance regimes.

For these workloads, T.38 is the path that survives the PSTN switch-off without breaking existing workflows.

What to evaluate in a T.38 deployment

• Carrier and trunk support: not every SIP trunking provider implements T.38 cleanly; verify with real test transmissions, not a datasheet bullet.
• End-to-end vs. partial: T.38 only helps where both ends speak it. A mid-path G.711 hop reintroduces the failure modes T.38 was meant to solve.
• UDPTL vs. TCP transport: UDPTL with FEC is the dominant deployment; TCP-T.38 exists but is less common.
• ATA compatibility: legacy fax machines connect via an analog adapter — make sure the ATA negotiates T.38 reliably on the SIP trunk in use.
• Cloud fax alternatives: for new deployments, a hosted fax service that delivers documents as email attachments or API calls often makes more sense than provisioning T.38 at all.

T.38 frequently asked questions

What does T.38 mean?

T.38 is the ITU-T recommendation number for a protocol that carries Group 3 fax transmissions in real time over IP networks. It demodulates the fax tones at the originating gateway, transports the underlying data as packets with error correction, and remodulates at the destination gateway.

What is the difference between T.38 and G.711 fax?

G.711 “pass-through” carries fax tones as ordinary audio inside the voice codec — it breaks on any meaningful packet loss or jitter. T.38 demodulates the tones into discrete data packets with FEC, surviving realistic IP network conditions. T.38 is the production-grade option.

Does T.38 work over SIP?

Yes. T.38 is typically negotiated mid-call: the SIP session starts as voice, detects the V.21 fax preamble, and either reINVITEs to switch the media format to image/t38 or hands the call to a separate FoIP-capable session. Most modern SIP trunking providers support this.

Is T.38 still needed in 2026?

Yes, in verticals where fax remains a regulated or required channel — healthcare, legal, government, and financial services. As the PSTN switch-off removes analog fax lines, T.38 is the most common way to keep existing fax workflows running over IP infrastructure.

See how DialPhone fits

DialPhone’s online fax and business phone handle fax over IP with T.38 relay end-to-end on supported trunks, plus email-and-API delivery for new workflows — so HIPAA, legal, and government fax requirements survive the PSTN switch-off without an analog line in the building.