Overview

This article explains how to configure a RightFax dialing rule to route faxes back into the RightFax server when they match user Inbound Routing Digits (also called Routing Codes or DID/DNIS).  This allows internal fax numbers to be delivered as inbound faxes to specific RightFax users instead of being sent over telephony lines.

The key mechanism is the Receive into Fax Server dialing rule destination, which delivers the fax internally to the RightFax server for routing to the appropriate user.

Applies To

Verified Major Releases:

·         RightFax 10.6 (including 10.6 FP3)

·         RightFax 16.x series (16.2, 16.4, 16.6 including EP6)

·         RightFax 20.x

·         RightFax 21.x

·         RightFax CE 22.x

·         RightFax CE 23.x

·         OpenText Fax 24.x

Note on OpenText Fax 25.x:  While these releases exist, publicly accessible documentation for 25.x was not available to verify exact UI labels and navigation paths.  The general concepts below apply, but confirm specific steps against your 25.x Administrator Guide before production implementation.

Prerequisites

1.  Administrative Access:  You have administrative access to RightFax Enterprise Fax Manager or RightFax Web Admin Console

2.  User Routing Digits Configured:  Each target user has Inbound Routing Digits configured in their user profile (appears as Routing code (DID/DNIS) in most RightFax versions)

3.  Number Pattern Understanding:  You know which portion of dialed internal numbers should map to user routing digits (e.g., last 4 digits)

4.  Licensing:  Dialing rule features are enabled on your RightFax server

How Internal Fax Delivery Works

When a dialing rule uses Receive into Fax Server as its destination:

1. RightFax intercepts the outbound fax before it reaches telephony

2. Routes it to the specified RightFax server

3. Delivers it as an inbound fax

4. Matches the resulting fax number against user routing codes

5. If matched: delivers to that user's inbox

6. If not matched: delivers to the Default user ID configured on the server

Critical Success Factor:  The final fax number after dialing rule processing must exactly match a user's routing code.  This typically requires number adjustments (see Step 4).

Configuration Steps

#### Step 1: Verify User Inbound Routing Digits

1. Open user properties for each target RightFax user

2. Locate the Routing code (DID/DNIS) field (terminology varies slightly by version)

3. Confirm each user has the routing code you intend to match

4. Document these values for testing

Example:  If users have 4-digit routing codes like "1234", "5678", your dialing rule adjustments must deliver exactly these 4 digits.

#### Step 2: Create the Dialing Rule

Navigation (version-dependent):

·         Enterprise Fax Manager:  Navigate to the server's Dialing Rules node

·         Admin Console:  Configuration > Dialing Rules

·         Click New to create a new dialing rule

Rule Configuration:

1. Rule Name:  Enter descriptive name (e.g., "Internal Fax Routing")

2. Pattern Match:  Configure the pattern to match internal fax numbers

·         Use digits and wildcard question marks: `206-???-????`

·         Match the format users dial for internal faxes

3. Direction:  Set to apply to outbound faxes (before they reach telephony)

1. In the dialing rule destination settings, select Receive into Fax Server

2. Select the destination RightFax server (can be local server or remote server on network)

3. Optional:  Enable TTI (Transmit Terminal Identifier) if you want header information on internally routed faxes

Version-Specific Notes:

·         RightFax 10.6 FP3 - 12.1:  May show as "Call back" option with server address/hostname fields

·         RightFax 20.2 and later:  Shows as "Route to Server" or "Receive into Fax Server" with server selection list

Step 4: Configure Number Adjustments (CRITICAL STEP)

This is the most important configuration for successful internal routing.  The delivered number must exactly match user routing codes.

Example Scenario:

·         Users dial: `503-555-1234` (10 digits)

·         User routing codes: `1234` (4 digits)

·         Required adjustment:  Remove first 6 digits

Configuration:

1. Open the Number Adjustments settings in the dialing rule

2. Configure adjustments to strip prefixes/area codes

3. Result must equal the user's routing code exactly

Common Adjustments:

·         Remove area code (3 digits)

·         Remove site/office codes

·         Remove trunk access digits (9, 8, etc.)

·         Remove formatting characters (dashes, spaces)

Step 5: Save and Test

1. Save and activate the dialing rule

2. Send a test fax to an internal number covered by the rule

3. Verify the fax appears in the intended user's inbox as an inbound fax

If Testing Fails:

·         Fax goes over telephony:  Dialing rule pattern didn't match - check pattern against exact dialed format

·         Fax routes to Default user:  Final number didn't match any routing code - verify Step 1 and Step 4 adjustments

·         Unexpected behavior:  Check dialing rule priority order (rules evaluate in sequence)

Important Considerations

Loop Prevention:

If configuring multiple servers with "Receive into Fax Server" rules, ensure you don't create routing loops where faxes bounce between servers.  RightFax will send the fax after 10 loops, but this wastes resources and delays delivery.

Server Connectivity:

Destination servers must be reachable on the network.  Verify server names and network paths.

Rule Priority:

Dialing rules evaluate in order.  Place internal routing rules at appropriate priority to ensure they evaluate before other rules.

Troubleshooting Guide

Version-Specific Implementation Notes

Due to UI evolution across the 10.6 - 25.x version range, exact field names, menu paths, and dialog boxes vary.  For production implementation:

1. Consult your version-specific Administrator Guide

2. Test thoroughly in non-production environment

3. Document your exact configuration

4. Capture screenshots for internal reference

5. Contact OpenText Support for configuration verification if needed

Scope: FaxCore and etherFAX

This procedure is specific to RightFax dialing rules and routing codes.  FaxCore and etherFAX have their own internal routing mechanisms that should be documented separately using vendor-specific administration guides.

Related Articles

• Blocking a Single Outbound Fax Number in RightFax Using a Dialing Rule

• Blocking Outbound Fax Numbers in RightFax Using Destination Tables

• RightFax - TCP/IP Ports Required for Client and Server Communication

Related Topics (Planned)

• Configuring User Inbound Routing Digits DID/DNIS

• Dialing Rule Priority and Evaluation