Summary 

Applicability / Versions 

Prerequisites

• Server OS: Windows NT 4.0 or Windows 2000

• Storage: Plan at least 500 MB for fax images; processing pauses when free space is very low

• Telephony: Supported analog or digital fax boards; DID/DNIS or POTS trunks provisioned

• Client print path: Clients print to the HPFAX queue on the server; PCL5 driver present on workstations

• Gateways: Exchange or Notes accounts and permissions per gateway guides

Steps

1. Understand 8.0 components
   RightFax 8.0 used a central server with services including Server, WorkServer(s), BoardServer(s), RPC Server, Database module, and Queue Handler. Optional modules handled e-mail and integrations.

2. Install fax boards
   Install Brooktrout/Dialogic drivers and utilities. Configure channels and DID where available. Verify signaling and clocking with vendor tools. Start the RightFax BoardServer and confirm channel states.

3. Install server software
   Install RightFax 8.0 on the fax server. Verify Server, WorkServer, and BoardServer modules register and start. Confirm print queues are created and visible.

4. Configure inbound routing

• DID/DNIS: Set digits to collect on the fax board; assign routing codes to users in Enterprise Fax Manager

• DTMF: Enable per-channel; set terminator, digit ranges, and timeouts; assign user DTMF codes

• OCR routing: Use as backup; route to a central mailbox if naming collisions are likely

5. Install client software
   Deploy FaxUtil, Enterprise Fax Manager, print driver, and optional Outlook/Notes extensions from the RightFax client installer share. Confirm clients can print to HPFAX.

6. Deploy e-mail gateways
   Exchange: Install the RightFax connector for Exchange 5.5/2000. Configure directory sync and forms.
   Lotus Notes: Install gateway databases. Choose the integration level (full, minimal, none). Enable required agents and synchronization.

7. Optional web and add-on modules
   Install the Web Client on Microsoft web services and point it at the RightFax server. For certified delivery or secure workflows, install the SecureDocs module and configure required IIS sites. Enable InternetLink if used for outbound carrier services.

Final validation 

Validation

• Outbound: Submit a multi-page document via FaxUtil; verify conversion and a successful result code

• Inbound: Verify DID/DNIS or DTMF routing to the correct user mailbox

• Hardware: Use board vendor diagnostics or RightFax board tools to confirm channels idle/active states

Operations Notes

• Maintain a healthy disk floor to avoid conversion pauses; plan archiving and retention

• Scale by adding WorkServers for conversion and remote BoardServers for channel capacity and resilience

• HPFAX queue is required for the print-to-fax path

Limits / Known Behaviors

• Nested client folders in 8.x may not appear to older clients

• DID trunks are inbound-only and typically require external power; never connect loop-start lines to DID ports

• OCR routing reads printed text only and is not ideal at scale

Troubleshooting

Symptom → Cause → Fix

Outbound faxes stuck in queue → WorkServer or BoardServer not executing tasks → Verify services, test channels, restart modules

Inbound faxes not routing by DID → Digit length or signaling mismatch → Correct digits-to-collect and trunk signaling, then retest

DTMF routing fails → Terminator or digit ranges misaligned → Adjust terminator, min/max digits, and tone wait timers

Discrepancies (if any) 

Change Log

2025-10-13: Created.

2025-10-13: Last validated.

Contact Ingenium Software

Sources