Doc Transport Service
Not Starting

This is the most commonly missed cause. In the Brooktrout SDK Configuration Utility, navigate to the SIP transport settings for the configured board. There are explicit toggles to enable TCP transport and enable UDP transport. If your SIP trunk uses TCP (common in enterprise SBC deployments) and TCP is set to disabled in the Brooktrout config, the service will not start. The same applies for UDP. Verify the correct protocol is enabled and matches your SIP infrastructure. This setting is distinct from Windows Firewall rules. The port can be open at the OS level and the service will still fail if the Brooktrout protocol toggle is off.

Brooktrout driver files and the Doc Transport executable must be included in AV/EDR exclusions. If exclusions were applied post-installation, a quarantine event during an earlier startup attempt may have flagged components. Check the AV quarantine log and restore any flagged Brooktrout or RightFax Doc Transport files, then retry the service start.

The Doc Transport requires network access to the SIP gateway or Session Border Controller. Required ports typically include:

• SIP signaling: UDP/TCP 5060 (or 5061 for TLS-SIP)
• RTP media: UDP 10000-20000 (range varies by Brooktrout configuration)

Verify these ports are permitted outbound from the RightFax server in both Windows Firewall and any network-layer firewall between the server and the SBC.

Confirm the RightFax server can reach the SIP gateway or SBC by IP and that the gateway is accepting registrations. A SIP trunk that has expired or a gateway that has been reconfigured (IP change, authentication change) will cause the Doc Transport to fail initialization. Test connectivity using a SIP test tool or by reviewing SBC logs for registration attempts from the RightFax server IP.

RightFax maintains detailed logs in the configured log directory. The Doc Transport log and Brooktrout log will contain the specific error at the point of service failure. Common entries include port binding failures, SIP registration rejections, license validation errors, and Brooktrout driver initialization codes. These logs are the fastest path to a definitive root cause when the checklist steps above have not resolved the issue.

The RightFax services run under a service account that must have appropriate local permissions on the server. If a password change has occurred on the service account, or if a group policy change has modified local rights (particularly "Log on as a service"), the Doc Transport will fail to start. Verify the service account credentials and local security policy assignments in the Windows Services configuration and Local Security Policy.