Fax Status Transmission Errors | Citadel Sentinel IT & Cybersecurity Solutions

TransmissionKB-012

Fax Status Transmission Errors: Causes, Identification, and Fixes

RightFax transmission errors happen when a fax call connects but fails before the document is fully delivered. Some failures are normal in faxing because network conditions, remote device behavior, timing, and media negotiation can all interrupt a call. Reviewing the result code first is the fastest way to decide whether to keep troubleshooting the destination, the telephony path, or the server-side fax configuration.

Indicators

The fax shows a transmission error or error retry status in FaxUtil.
The call connects, but the fax does not complete successfully.
The same destination works from a physical fax machine but fails from RightFax.
Status codes point to communication, remote device, dialing, or protocol issues.

Resolution Steps

Confirm the Destination and Reachability

Confirm the recipient fax number, country code, dialing prefix, and any dialing rules are correct. Call the number and listen for fax tone or confirm you have reached a fax-capable endpoint. If the number is answered by voice, an IVR, or a non-fax device, the transmission may fail even though the call connects.

Read the RightFax Status and Retry State

Review the FaxUtil status code first, because it tells you whether the job is retrying or already dropped. Check retry state, Update Status, and Smart Resume when supported. Standard clues like no dial tone, communication line failure, and command timeout often separate line issues from remote-device issues.

Compare Physical Fax Versus RightFax

If the same destination succeeds from a physical fax machine but fails from RightFax, compare the Brooktrout driver version, board configuration, and SIP media settings. That difference often points to codec negotiation, protocol handoff, or the fax board profile rather than the destination number itself. Outdated Brooktrout components can fail even when a stand-alone fax machine still succeeds on the same line or SIP path.

Check Fax Speed, ECM, and Line Quality

Lower the fax speed if the line or VoIP path is marginal; 14.4k may fail while 9.6k or 4.8k succeeds. Temporarily disable ECM during troubleshooting if the provider or far-end device is sensitive to it. A fax transmission error does not mean the entire trunk is down; it may only mean the negotiation was too aggressive for the path.

Review Codec and T.38 Behavior

In Brooktrout SR140 and similar SIP fax deployments, the RTP codec list and G.711 fallback behavior can determine whether a fax succeeds over IP. The practical concern is often whether the board is advertising PCMU, PCMA, or both, and whether the SBC or provider path handles that codec list cleanly. If T.38 negotiation is unreliable, G.711 fallback may keep the fax alive, but it should remain an uncompressed codec path.

Escalate T.38 Re-INVITE Failures

If Wireshark shows a T.38 re-INVITE followed by disconnect, investigate the carrier or SBC as likely points of failure. A real-world pattern is that the number answers, the SIP session comes up, T.38 re-INVITE occurs, and the call drops during handoff. In those cases, the root cause is often the carrier or SBC media layer rather than the fax server itself.

Verify Protocol and Codec Fallbacks

Review T.38, T.38 re-INVITE, and G.711 fallback behavior in SIP environments. Some environments become stable only after limiting the advertised codec list to a single codec rather than both. If the board advertises the wrong codec mix, or if the provider only behaves correctly with PCMU or PCMA specifically, the call may connect but fail during fax negotiation or T.38 switchover.

Confirm the Response Pattern

Use the response pattern to narrow the issue. If all destinations fail, focus on service, transport, or provider configuration. If only one number fails, focus on the destination device, remote routing, or that number’s fax capability. If the pattern changes after lowering speed or changing codecs, the issue is likely in the media path rather than in RightFax document handling.

Field Note

The goal is not to eliminate every transmission error, but to identify whether the failure pattern points to the destination, the remote fax device, the Brooktrout configuration, or the SIP/SBC path.

TransmissionRightFaxBrooktroutFaxUtilT.38PCMUPCMAECMSBC