RightFax 9.0 historical setup and architecture snapshot

RightFax 9.0 — Historical architecture, requirements, and setup snapshot

Summary

Concise snapshot of RightFax 9.0 circa 2004–2006. Outlines server services, fax board layer, client options, e-mail gateways, and a clean install and configuration flow used in legacy deployments.

Applicability / Versions

RightFax 9.0 base through common service packs. Typical stacks: Windows 2000 Server or Windows Server 2003, SQL Server 2000 or RightFax embedded DB, Brooktrout/Dialogic fax boards, optional Web Access and Integration Module.

Prerequisites

  • OS and updates: Windows 2000 Server or Server 2003, current service packs, MDAC 2.8 on the RightFax host.

  • Database: SQL Server 2000 reachable with a service account, or embedded DB where permitted.

  • Rights and accounts: Local admin for install. Dedicated service account for WorkServer tasks and scheduled jobs.

  • Telephony: Provisioned analog or digital trunks. Supported fax boards (e.g., Brooktrout TR1034/TR114, Intel/Dialogic, Eicon).

  • Networking/DNS: Static IP for the RightFax server. Forward and reverse DNS. SMTP relay if using e-mail notifications or InternetLink.

  • Clients: Windows workstations with FaxUtil and the RightFax print driver.

  • Storage: Fast local volumes for \RightFax\Images and \RightFax\NF; plan growth based on retention.

Steps

  1. Plan the topology
    Define one RightFax Server with WorkServer(s) for document conversion and a BoardServer instance for telephony. Identify whether Web Access, Integration Module, or e-mail gateways will be used.

  2. Prepare the host
    Apply OS updates. Confirm MDAC 2.8. Create a domain or local service account with “Log on as a service.” Set antivirus exclusions for \RightFax paths and spool folders.

  3. Install RightFax 9.0
    Run setup. Select Server, WorkServer, BoardServer, and management tools. After install, verify services start and register in Enterprise Fax Manager (EFM).

  4. Add and validate telephony
    Install fax board drivers and vendor tools. Verify clocking and signaling. In BoardServer configuration, create channels, set line types, and enable fax tones.

  5. Inbound routing

  • DID/DNIS: Set digits-to-collect in the board config. In EFM, assign routing codes per user or group.

  • DTMF: Enable on selected channels, set terminator and min/max digits, then assign user codes.

  • Fallback/OCR: Use only for edge cases. Route to a monitored mailbox to avoid misdelivery.

  1. User and policy configuration
    In EFM, create users or enable directory sync. Set permissions, default cover sheets, billing codes, and notifications. Configure retention, image path locations, and aging/archival jobs.

  2. Clients and print-to-fax
    Deploy FaxUtil and the RightFax print driver from the client share. Confirm print-to-fax path and HPFAX queue visibility.

  3. Gateways and modules

  • Exchange/Notes: Install the appropriate connector. Configure directory synchronization, forms, and routing rules.

  • Web Access: Install the web components on IIS. Point to the RightFax server, then test login and view/send functions.

  • Integration Module (optional): Enable DocTransport and workflow elements as required by downstream systems.

  1. Notifications and outbound paths
    Configure SMTP relay and InternetLink (if licensed) for carrier delivery or status e-mailing.

  2. Backup and maintenance
    Document backup sets for images, metadata, and SQL databases. Schedule regular service restarts during a maintenance window if required by your patch policy.

Final validation

  • Outbound: Print a multi-page document to the RightFax printer, track conversion in WorkServer, confirm successful transmission.

  • Inbound: Call a DID routed to a test user. Confirm delivery to the correct mailbox.

  • Board health: Use vendor diagnostics to verify channels idle/busy states and error counters.

Operations Notes

  • Maintain free space thresholds to prevent conversion pauses.

  • Scale conversion by adding WorkServer instances. Scale channels by adding boards or FoIP resources.

  • Keep EFM exports of configuration for rollback.

  • Patch order matters: apply board firmware/drivers before RightFax hotfixes when both change signaling.

Limits / Known Behaviors

  • Mixed client versions may not display nested folders consistently.

  • DID trunks are inbound only and often require external power units.

  • OCR-based routing is unreliable at scale and should not replace DID/DTMF.

Troubleshooting

Symptom → Cause → Fix
Outbound jobs stuck in “Converting” → WorkServer permissions or filters → Run services under the service account, add AV exclusions, retry.
Inbound not routing via DID → Wrong digit length or signaling → Adjust digits-to-collect, confirm wink/immediate timing, retest.
Frequent retries or partial pages → Line quality or board clocking → Check carrier levels, set proper clock source, update board firmware.

Discrepancies (if any)

Behavior varies by fix pack and board driver level. Validate menu names and dialogs against your specific 9.0 maintenance release.

Change Log

2025-10-13: Created.
2025-10-13: Last validated.

Contact Ingenium Software

Questions or deployments:
info@ingeniumsw.com • 770-936-0600

Sources

RightFax v9.0 Installation Guide — Ingenium Software internal document repository — Accessed 2025-10-13
RightFax v9.0 Administrator’s Guide — Ingenium Software internal document repository — Accessed 2025-10-13
RightFax v9.0 Fax Board Guide — Ingenium Software internal document repository — Accessed 2025-10-13
RightFax v9.0 ReadMe — Ingenium Software internal document repository — Accessed 2025-10-13
Backing up and Restoring the RightFax 9.0 Server and Database — Ingenium Software internal document repository — Accessed 2025-10-13