T38 Modem Explained: Key Features and Performance Benchmarks

T38 Modem: Setup, Compatibility, and Troubleshooting Tips

Overview

T.38 is a protocol for real-time fax transport over IP networks (FoIP). A “T38 modem” refers to hardware or software that supports T.38 to send/receive faxes reliably over VoIP by converting fax tones to packetized data.

Setup (step-by-step)

1. Verify network readiness
   • Ensure low latency (<100 ms), low jitter, and minimal packet loss (<1%).
2. Select device/software
   • Use a VoIP gateway, ATA, IP-PBX, or fax server that explicitly lists T.38 support.
3. Configure SIP trunk and phone system
   • Enable T.38 on SIP trunks and endpoints. Set negotiated codecs to allow T.38 (often alongside G.711).
4. Set T.38 parameters
   • Common settings: T.38 version (e.g., 0 or 1), max bit rate, UDP packetization, redundancy (rFax) and UDP/TCP transport—use defaults unless vendor suggests changes.
5. Network/NAT configuration
   • Open/forward required UDP ports for SIP and RTP as per vendor. For T.38, ensure NAT traversal (STUN, TURN, or SBC) is properly configured.
6. Test with sample faxes
   • Send/receive test pages, verify logs show T.38 negotiated instead of passthrough G.711 (if supported).
7. Monitor and tune
   • Monitor call quality, packet loss, and retransmissions; increase redundancy or adjust QoS if needed.

Compatibility

• Endpoints: Must support T.38 (not all ATAs, IP phones, or fax machines do).
• SIP trunk/provider: Provider must allow/advertise T.38 negotiation.
• Codecs: G.711 passthrough can work for some setups, but true T.38 is preferred for reliability.
• Network equipment: Firewalls, NATs, and SBCs must permit T.38-related traffic; some older gear may block or mishandle FoIP.
• Interoperability: Different vendors may implement T.38 options differently; check vendor compatibility notes and firmware updates.

Common Problems & Troubleshooting

• T.38 not negotiated (falls back to G.711)
  • Check that both endpoints and SIP trunk advertise T.38 in SDP. Verify SIP ALG is disabled on routers.
• Missing or garbled pages
  • Caused by packet loss or insufficient redundancy. Improve QoS, increase T.38 redundancy, or lower bit rates.
• One-way audio or no fax tone
  • Verify RTP streams and NAT traversal. Ensure correct port forwarding and STUN/TURN/SBC configuration.
• Intermittent success
  • Check for network congestion at peak times; enable traffic prioritization for SIP/RTP.
• Firewall blocking
  • Inspect logs, open necessary UDP ports, and disable deep packet inspection if it interferes with SIP/T.38.
• Vendor-specific quirks
  • Update firmware, consult interoperability matrices, and use vendor-recommended settings.

Diagnostic checklist (quick)

• Confirm both endpoints and provider advertise T.38 in SDP.
• Run network tests for latency, jitter, and packet loss.
• Disable SIP ALG on routers and enable NAT traversal solutions.
• Check device firmware and enable QoS for SIP/RTP.
• Capture SIP traces to verify SDP negotiation and T.38 session establishment.

Best practices

• Use an SBC or gateway that properly handles SIP/T.38 and NAT.
• Prefer wired network segments for fax devices and apply QoS.
• Keep firmware up to date and test interoperability before production deployment.
• Maintain a fallback workflow for critical faxes (e.g., store-and-forward email fax) if FoIP fails.

If you want, I can provide vendor-specific settings (e.g., for Grandstream, Cisco, or Sangoma) — tell me which device or provider you use.