RightFax 10.0 historical setup and architecture snapshot

RightFax 10.0 — Historical architecture, requirements, and setup snapshot

Summary

Concise snapshot of RightFax 10.0 circa 2011. Outlines core services, database model, fax board layer, optional modules, and a clean install and configuration flow for legacy reference.

Applicability / Versions

RightFax 10.0 baseline and maintenance packs; typical stacks: Windows Server 2008 and 2008 R2, SQL Server 2005 or 2008, on-prem fax boards or FoIP; optional Web applications, Integration Module, XML Generator, and Exchange connector.

Prerequisites

  • OS and updates: Windows Server 2008/2008 R2 with required IIS and .NET components.

  • Database: SQL Server 2005 or 2008, or SQL Express 2008 installed by setup; service and setup accounts with create permissions for initial DB build.

  • Middleware: MSMQ, MDAC 2.8, VC++ runtimes, Windows Installer.

  • Telephony: Supported Brooktrout/Dialogic/Eicon boards or licensed FoIP.

  • Networking/DNS: Static IP for server, SMTP relay if using notifications or InternetLink.

  • Clients: FaxUtil and print driver for Windows; optional Web Access and Outlook forms.

Steps

  1. Plan the topology
    Define one RightFax Server with WorkServer(s) for conversion and a BoardServer/DocTransport for telephony. Decide on Web apps, Integration Module, XML Generator, and Exchange connector as needed.

  2. Prepare the host
    Apply OS updates. Confirm MSMQ and MDAC. Create a service account with “log on as a service.” Add AV exclusions for RightFax paths.

  3. Install RightFax 10.0
    Run setup. Select Server, WorkServer, BoardServer, and tools. Verify services register and start; confirm EFM access.

  4. Add and validate telephony
    Install vendor drivers. In DocTransport/BoardServer, create channels, set line types and signaling. For FoIP, license channels and set failover if used.

  5. Inbound routing
    Configure DID/DNIS or DTMF; assign routing codes to users or groups in EFM; enable alternative routing methods as needed.

  6. Users and policy
    Create users or enable directory sync; set permissions, covers, billing, retention, and image paths.

  7. Clients and print-to-fax
    Deploy FaxUtil and print driver from the client installer share; validate HPFAX print path.

  8. Gateways and modules

  • Exchange connector: add RightFax Exchange Gateway and server-side connector; enable AD sync profile.

  • Integration Module: license and connect via directory scan, LPR, TCP socket, MQ, or serial.

  • XML Generator / EDC: enable EDC and XML Generator; set destination folders or lookups.

  1. Web applications
    Install Web modules on IIS and point to the RightFax server; set timeouts and delivery options.

  2. Backup and maintenance
    Back up SQL DB, images, and configuration; review purge jobs and collations.

Final validation

  • Outbound: Print a multi-page document to the RightFax printer; verify conversion in WorkServer and a successful transmit code.

  • Inbound: Call a DID to a test user; confirm delivery to the correct mailbox.

  • Board health: Use vendor diagnostics or BoardServer stats to verify channels and error counters.

Operations Notes

  • Maintain disk free space; fax processing pauses under low-space thresholds; size images at about 35 KB per page for planning.

  • Scale conversion by adding WorkServers; scale channels by adding boards or FoIP resources; remote DocTransport is supported.

  • Keep EFM exports of configuration for rollback; document purge and archive schedules.

Limits / Known Behaviors

  • Mixed client versions can show folder and UI differences; validate client features against 10.0.

  • Supported boards are limited to the vendor list for 10.0; confirm exact TR1034/Eicon SKUs.

  • Web modules and EDC require IIS prerequisites; session and delivery behaviors are configurable.

Troubleshooting

Symptom → Cause → Fix
Outbound stuck in “Converting” → WorkServer rights or filters → Run services under the service account, add AV exclusions, retry.
Inbound not routing via DID → Digits-to-collect or signaling mismatch → Adjust board digits and trunk signaling; retest.
FoIP call failures → Unlicensed or misconfigured channels → Verify SR140 licensing and FoIP settings; confirm failover profile.

Discrepancies (if any)

Feature names and dialogs vary by maintenance pack and board driver levels; verify in your specific 10.0 build.

Change Log

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

Contact Ingenium Software

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

Sources

OpenText RightFax 10.0 Administrator’s Guide — Ingenium Software internal document repository — Accessed 2025-10-13
OpenText RightFax 10.0 Installation Guide — Ingenium Software internal document repository — Accessed 2025-10-13
OpenText RightFax 10.0 Fax Board Guide — Ingenium Software internal document repository — Accessed 2025-10-13
OpenText RightFax 10.0 Integration Module Guide — Ingenium Software internal document repository — Accessed 2025-10-13
OpenText RightFax 10.0 XML Generator Guide — Ingenium Software internal document repository — Accessed 2025-10-13
OpenText RightFax 10.0 Connector for Microsoft Exchange — Ingenium Software internal document repository — Accessed 2025-10-13