FAX over VoIP fails intermittently — T.38/G.711 & ECM flow control fix

Joe B.

Expert ★★★★★ 27,853 satisfied customers

Specialities: VoIP, SIP trunks, Fax over IP (FoIP), ATAs, Routers/Firewalls, Business MFPs

FAX over VoIP fails intermittently — T.38 vs G.711 pass-through, ECM, jitter & flow control tuning

Technician

Hey! Let’s track down why your fax over VoIP is failing randomly.
Quick questions so we hit the right settings: Are you using an ATA (fax adapter) or a fax-capable MFP on a SIP trunk? Does your provider support T.38, or are you running G.711 pass-through? And when it fails, do you see partial pages, communication error, or ECM retries exceeded on the fax?

Customer

We’ve got a Ricoh MFP and a couple of classic fax machines on Grandstream ATAs, all over a hosted VoIP provider. Some faxes go through, others fail at random — usually mid-page or on page 2–3. Error codes mention “communication error” or “ECM failed.”

Technician

Got it — that’s classic FAX over IP (FoIP) behavior when signaling, codec, and error correction don’t agree.
In a VoIP environment:

• Using G.711 instead of T.38 fax relay makes fax audio sensitive to jitter, latency, and packet loss.
• Misconfigured or half-supported T.38 (bad re-INVITE, wrong UDPTL settings) causes drops mid-transmission.
• Aggressive ECM (Error Correction Mode), high baud rates, and busy line echo cancellers make “borderline” links fail intermittently.

We’ll stabilize this by standardizing T.38 or clean G.711 pass-through, tuning ECM, lowering fax speed, and fixing jitter buffer & QoS so your faxes stop randomly dying.

Customer

Our VoIP provider says they “support T.38,” but I’m not sure if calls actually switch. How do we check if it’s using T.38 or just G.711?

Technician

Step 1 — Confirm if T.38 is really active
On your ATA/MFP or PBX:

• Check that T.38 is enabled with your provider’s recommended settings (version, redundancy, UDP/UDPTL).
• Look at call logs or status during fax: a proper setup shows a re-INVITE to T.38 after CNG/CED tones.
• If there’s no switch and media stays G.711, you’re on fax pass-through, which must be tuned carefully.

If the provider “supports T.38” only on paper or in one direction, we may be better forcing reliable G.711 fax over VoIP with the right flow control instead of half-broken T.38.

Customer

Some numbers work fine, others fail on long faxes. Where do ECM and fax speed come in? We’ve mostly left defaults.

Technician

Step 2 — Tune ECM & baud rate for VoIP realities

• Set fax speed to 9600 or 14400 bps instead of max 33.6K. Slower is more stable on packet networks.
• Try with ECM ON first when using clean T.38 — it corrects occasional lost packets.
• If you’re stuck on noisy G.711 pass-through, test with ECM OFF plus reduced speed; endless ECM retries cause many mid-fax failures.
• Disable V.34 super G3 on legacy lines if calls drop early.

These “unsexy” tweaks — speed, ECM, flow control — are often what stop intermittent FoIP failures.

Customer

We also run data and calls over the same fiber. Could network quality be killing faxes even though voice calls sound okay?

Technician

100%. Fax tones are less forgiving than human ears.
Step 3 — Stabilize the path: jitter, QoS & ALG

• Target: <150 ms latency, <1% packet loss, stable jitter. Spikes break long fax pages.
• Enable proper QoS: prioritize SIP/RTP/UDPTL and/or ATA VLAN so big uploads don’t starve fax packets.
• Disable SIP ALG or buggy firewall “VoIP helpers” that mangle T.38 re-INVITEs.
• Use wired connections only; never put ATAs or fax MFPs behind Wi-Fi extenders.

Once the media path is clean, your T.38/G.711 fax sessions stop dropping “for no reason”.

Customer

We’re on a hosted PBX with Cisco and Grandstream ATAs. Any concrete settings you recommend so we can test a stable profile?

Technician

Step 4 — Known-good baseline for many ATAs (always confirm with your SIP provider):

• Enable T.38 fax relay with redundancy (2–3) if fully supported end-to-end.
• If T.38 is flaky, force G.711 µ-law / A-law only for fax ports — no compressed codecs, no VAD, no comfort noise.
• Set fax baud to 9600–14400, disable V.34 if issues persist.
• Start with ECM ON for T.38; if using G.711 and seeing frequent retries, test with ECM off.
• Increase jitter buffer moderately (e.g., 100–200 ms fixed) for fax ports.

We can walk through your exact ATA menus live and apply a VoIP fax stable profile instead of guessing.

Customer

Some partners say they receive blank pages or only the first page. How do we confirm it’s not our MFP hardware?

Technician

Step 5 — Separate device issues from VoIP issues

• Run an internal fax (MFP ↔ ATA/line in same office) if supported.
• Fax to a known reliable test number (many providers offer loopback / confirmation services).
• If local analog tests are clean but VoIP faxes fail intermittently, the problem is upstream: codec, T.38, or path.
• If failures occur even on local analog, clean the scanner, test another machine, or swap ATA ports/cables.

This isolates whether we need MFP service or pure FoIP tuning.

Customer

After dropping the speed and fixing codecs, success rate is way better. Any final checks before we roll this across all lines?

Technician

Final checklist:

• Use a single standardized fax profile on all ATAs/MFPs (codec, T.38/G.711 choice, speed, ECM).
• Confirm your SIP provider officially supports T.38 end-to-end or gives documented fax-over-G.711 guidance.
• Lock fax ports to wired LAN, with QoS marking and no SIP ALG.
• Log a few real-world faxes daily — make sure intermittent failures are gone, not just reduced.

Once those are in place, your fax over VoIP should be as predictable as legacy POTS, without mystery drops. If you’d like, we can review your config live.

Customer

Perfect. Faxes are now going through consistently and the accounting team stopped complaining. Thanks for the detailed tweaks.

Technician

Summary: To fix FAX over VoIP failing intermittently, verify real T.38 support or clean G.711 pass-through, tune ECM and fax speed, disable bad codecs/VAD, stabilize jitter and QoS, and standardize ATA/MFP settings. Need a VoIP fax expert to sanity-check your SIP trunk and adapters? Open the chat.

Quick answer: the accepted fix

Accepted fix when fax over VoIP fails intermittently: use a supported T.38 fax relay or locked G.711 pass-through, disable compressed codecs and VAD, lower fax speed to 9600–14400, tune ECM, fix jitter/QoS, and standardize ATA/MFP settings across all lines.

FAQ

Step-by-step: stabilize fax over VoIP

1. Confirm with your SIP provider: T.38 fully supported or use G.711-only fax pass-through.
2. On ATAs/MFPs: enable T.38 or lock G.711, disable compressed codecs, VAD, and comfort noise for fax ports.
3. Set fax speed to 9600–14400 bps; adjust ECM based on line quality (on for good T.38, off if G.711 is marginal).
4. Optimize network: wired-only, QoS for VoIP, disable SIP ALG, monitor jitter/packet loss.
5. Test multiple destinations and standardize the working profile across all fax lines.

Note for mixed environments & fax servers

1. For fax servers / eFax / FoIP gateways, follow vendor T.38 and SDP guidelines strictly.
2. In hybrid setups (analog lines + SIP trunks), keep fax routes predictable; avoid unnecessary media transcoding.
3. For compliance or high-volume faxing, consider a dedicated fax service or SIP trunk optimized for T.38.

Sources

• ITU-T T.38 — Procedures for real-time Group 3 facsimile communication over IP networks
• Grandstream — Fax over VoIP configuration guidance

Matt ● replies in < 1 min

Technician Expert

⭐⭐⭐⭐⭐ Trusted by 27,000+ customers

Alex · Expert's Assistant

Start Chat

5 Tech Support Specialists are online right now.