Fax-Native SIP Trunking
The SIP Trunk That Actually Supports Fax
Most SIP trunks treat fax as an afterthought. Here is what a fax-capable trunk has to do, what to check on your own equipment, and where each setup breaks.
Why Fax Breaks the Moment You Move to SIP
Voice worked after the move to SIP. Then someone sent a fax. Pages cut off mid-transmission, the far end answered and nothing arrived, or the call dropped right after the T.38 re-INVITE. Your SIP provider told you to lower the baud rate, turn off ECM, and try again.
Every fax call starts as ordinary G.711 audio. When the endpoint hears fax tones and T.38 is enabled, it sends a SIP re-INVITE asking both sides to switch from RTP audio to T.38 fax relay over UDPTL, which carries the fax as data. Every device in the path has to accept that switch. If one of them doesn’t, the call stays on G.711 or fails.
The failure sits in one of three places: your equipment, your network, or your carrier. This page covers what the carrier has to do, what you control, and how each common setup breaks.
What a SIP Trunk Needs to Support Fax
Not all T.38 support is equal. Three things decide whether fax over SIP works, and most providers fail at least one.
Native T.38 on the carrier side. Ask any provider where T.38 conversion to the PSTN happens. If the answer involves “relay,” “upstream carrier,” or “our network partner,” your fax rides on a network the provider doesn’t control and can’t diagnose.
Error Correction Mode (ECM) available on every call. ECM divides each page into frames, checks each frame, and retransmits any that arrive corrupted. Without it, a page can arrive with missing or garbled sections while the call still reports success. ECM only runs when both ends negotiate it, and a gateway in the path can be configured to switch it off. Most carriers disable it to reduce processing overhead.
A carrier that can read a trace. If a fax fails, the provider should be able to tell you which T.30 phase and which ECM frame failed. “Lower the baud rate and turn off ECM” is a guess.
T38Fax runs its own T.38 stack with media gateways inside carrier networks, offers ECM on every call, and diagnoses failures from T.30 traces. We went through interoperability testing with Dialogic and are one of a small number of SIP trunk vendors certified for use with the SR140, the T.38 stack inside RightFax, HylaFAX Enterprise, and GFI FaxMaker. The architecture is covered on Power-T.38, and the full argument against pass-through is on Why T38Fax.
What Has to Be True on Your Side
T.38 and ECM enabled on the endpoint. Your fax server, ATA, or multifunction printer has to offer T.38 when it detects fax tones, and ECM has to be on. Our recommended fax machine settings cover the common machine-side options.
SIP ALG off. Routers and firewalls with SIP ALG enabled rewrite SIP signaling and break fax calls in ways that look like carrier problems. Turn it off on every device in the path. Running SIP on UDP port 5080 on your side, ours, or both helps avoid it, but some firewalls follow SIP onto non-standard ports, and equipment updates can turn ALG back on. The firewall settings guide has the details.
The right ports open. Allow SIP on UDP and TCP 5060 and 5080 to sip.t38fax.com, plus UDP 16384 to 32768 for media. Use the hostname rather than static IP addresses where you can. The full list is in T38Fax IP Addresses and Port Usage.
A PBX that passes T.38 through, if you have one. An IP-PBX between your fax device and the trunk either relays T.38 unmodified (pass-through) or terminates T.38 itself (endpoint). Know which your setup is. Settings that force the PBX to transcode or inspect the media defeat pass-through.
Where Fax Breaks, by Setup
A fax server connected directly. OpenText RightFax, HylaFAX Enterprise, GFI FaxMaker, and XM Fax (XMedius) register straight to the trunk with no PBX in the path, so there are fewer places to fail. Check that T.38 and ECM are enabled in the server’s fax-over-IP settings. We also document Biscom FAXCOM, Esker Fax, and Softlinx ReplixFax. For the server-side picture, see Enterprise Fax Servers.
A fax server or ATA behind an IP-PBX. The PBX has to relay T.38 without touching it. Route your fax numbers through the T38Fax trunk and keep voice on your existing provider. Guides: 3CX v20, 3CX, Asterisk with its design guide, FreePBX, FreeSWITCH, FusionPBX, Digium Switchvox, and Grandstream UCM (6100, 6200, 6510).
A fax machine or multifunction printer on an ATA. The ATA converts the analog fax to T.38, so its firmware, its T.38 setting, and the fax machine’s own speed and ECM settings all matter. Certified ATAs have step-by-step guides: Grandstream HT801 V2 and HT802 V2, HT812, HT814, and HT818; Cisco ATA 191-MPP and ATA 192-MPP (only the MPP variants work with third-party SIP trunks); Poly ATA 400 and 402; Obihai OBi200, OBi202, and OBi302; and the AudioCodes MediaPack MP11X. For more ports at one site, there are guides for the Grandstream GXW4004 and GXW4008 gateways. Some Toshiba and Lexmark multifunction printers speak T.38 natively and need no ATA.
A hosted or carrier platform. If your own SIP trunk customers need fax, you can relay their fax traffic to T38Fax and keep voice where it is. The platform has to pass T.38 to the trunk for every customer. Guides: NetSapiens and Telinta. The wholesale model is on Voice Service Providers.
If your device or platform isn’t listed, T.38 over SIP is the test. Bring it to the 30-day free trial and our support team will work through it with you.
Run an ECM Test Before You Switch
Over 90% of T.38 calls proceed without ECM, and most carriers turn it off to reduce processing overhead. There is a good chance your current trunk has, and you may not know it. Our free ECM self-test is an ECM test for your current SIP trunk. It sends a test fax to your number and emails you whether ECM was active on the inbound and outbound calls, usually within minutes.
If you want to see Power-T.38 on your own equipment, the free trial includes a $25 credit for testing and unlimited technical support.
Pricing is usage-based, with no setup fees or minimum term: $7 a month per trunk, $2 a month per local fax number, and usage from $0.025 a minute. See the full rates, or request a quote and we’ll estimate your monthly cost from your page volume.
Looking for your specific device? More than 80 tested devices, each with a step-by-step setup guide in our knowledge base.
Compatibility List →Comparing carriers? Why pass-through fails, what ECM does at the frame level, and how to tell a fax carrier from a voice carrier.
Why T38Fax →Frequently Asked Questions
- Yes, if the trunk and your equipment both support T.38. A fax call starts as G.711 audio. When your device detects fax tones, it sends a SIP re-INVITE to switch the call to T.38 fax relay, which carries the fax as data with built-in packet redundancy. The carrier then has to terminate that T.38 session with its own implementation. Many providers pass it to an upstream carrier instead, and fax reliability then depends on a network they don’t control. T38Fax is a dedicated fax carrier. It runs its own T.38 stack with gateways inside carrier networks and offers Error Correction Mode (ECM) on every call.
- A SIP trunk supports faxing when the carrier handles T.38 natively, offers ECM on every call, and can diagnose failures from T.30 traces. Many general-purpose voice trunks list T.38 but pass it to an upstream carrier, which is pass-through rather than support. T38Fax is a dedicated fax carrier. Its Power-T.38 trunks work with fax servers such as RightFax, HylaFAX Enterprise, and GFI FaxMaker, with IP-PBXs, and with ATAs, and the 30-day free trial lets you confirm it on your own equipment.
- Fax fails over SIP for one of three reasons: your equipment, your network, or your carrier. On your equipment, T.38 or ECM may be switched off, or a PBX may be transcoding the media instead of passing T.38 through. On your network, SIP ALG on a router or firewall rewrites SIP signaling and breaks the call, and disabling it and using UDP port 5080 often avoids the problem. At the carrier, the provider may pass T.38 to an upstream network it doesn’t control, with ECM disabled and routing that changes from call to call. The carrier is the one you can’t see into, which is why a provider that can read T.30 traces matters.
- Ask your provider where T.38 conversion happens and which upstream carrier handles the T.38 leg. Answers like ‘relay,’ ‘upstream carrier,’ or ‘our network partner’ mean pass-through. To check ECM, the setting providers most often turn off, run T38Fax’s free ECM self-test. It tests inbound and outbound ECM on your current trunk and emails the result in minutes. Over 90% of T.38 calls proceed without ECM.
- If it supports T.38 over SIP, it should. T38Fax has tested and certified more than 80 devices and platforms, including RightFax, HylaFAX Enterprise, GFI FaxMaker, 3CX, Asterisk, FreePBX, FreeSWITCH, NetSapiens, and ATAs from Grandstream, Cisco, Poly, Obihai, and AudioCodes. Each one has a setup guide in the knowledge base, and the Compatibility List has them all. If yours isn’t listed, send us the model or connect it during the 30-day free trial, and support will work through it with you.
- Disable SIP ALG on every router and firewall in the path, and allow SIP on UDP and TCP ports 5060 and 5080 to sip.t38fax.com, plus UDP 16384 to 32768 for media. T38Fax recommends SIP port 5080 on one or both sides because many ALGs only act on port 5060. Some firewalls follow SIP onto other ports, and equipment updates can turn ALG back on, so recheck after any change. Use the sip.t38fax.com hostname instead of static IP addresses where possible. The full list is in T38Fax IP Addresses and Port Usage, and the firewall settings guide covers SIP ALG.
- You can use T38Fax for fax and keep your existing voice SIP trunk for voice calls, and that is the most common configuration. T38Fax is a fax-specialized carrier, not a general-purpose voice provider. Most customers point their fax equipment at our network while their IP-PBX keeps using its existing voice provider. Some customers run all traffic through T38Fax, and that works too. Our setup guides cover both configurations for Asterisk/FreePBX, 3CX, FreeSWITCH/FusionPBX, and other common platforms.