Configuring SBC Edge for One Number Fax in MS Exchange Environment

Overview

This Best Practice describes One Number Fax (ONF) feature configuration for the SBC Edge (SBC) in a MS Exchange environment. This document assumes you are familiar with the following:

• MS Active Directory and MS Exchange / Unified Messaging Server
• Ribbon Edge (SBC 1000/2000)
• A third party Fax Server (i.e., RightFax, XMedius, etc.)

Topology - One Number Fax in MS Exchange Environment

 

Configure One Number Fax

The table below lists the configuration steps required for One Number Fax; each of these steps is detailed below.

Step 1 - Configure Domain Controller and Active Directory

One Number Fax may or may not use the user's facsimileTelephoneNumber attribute that is configured in Active Directory (AD). If AD integration in Call Routing is desired, the Domain Controller and Active Directory must be configured in the SBC as follows:

1. Log into the WebUI and navigate to Active Directory> Domain Controller.
   
   

2. Create an entry with your domain controller's IP or FQDN (with the Call Route DC type, relevant search scope, and an LDAP query attribute). Refer to Adding and Modifying Domain Controllers.
   
   

3. Navigate to Active Directory> Configuration and configure. Refer to Configuring the SBC Edge for Active Directory.

Step 2: Configure Transformation Tables

If AD in Call Routes is planned to be use in your deployment:

1. Log into the WebUI and navigate to Transformation.
   
   

2. Create a transformation entry to passthrough the Called Address/Number, and normalize the Redirecting Number as facsimiletelephonenumber using the AD integration.

If AD is not intended to be used in Call Routes in your deployment:

1. Log into the WebUI and navigate to Transformation.
   
   

2. Create a transformation entry to passthrough the Called Address/Number. For example, the endpoint extension numbers and the eUM Subscriber Number are 3xxx-.

3. Log into the WebUI and navigate to Transformation.
   
   

4. Create a transformation entry to passthrough the Called Address/Number.

   When a call is referred to the Fax Server by eUM, the request header does not contain an extension number. Therefore, this piece of transformation is needed for the calls going to Fax Server.

Step 3: Configure Routing Tables

Two Call route entries need to be created: one for Fax calls, and the other for Voice calls:

1. Log into the WebUI and navigate to the Call Routing Table.
   
   

2. Create the following two Call Routing Table Entries.
   
   In Fax Calls where the CNG tone will be detected, a second entry needs to be added in the table to route calls to FAX Server:

   
   

   For Voice calls, there is no need for an entry to Fax Server, therefore we create a Route Table for one entry for number transformation:

Step 4: Create Action Configuration and Action Set

1. Log in to WebUI and navigate to Call Actions.
   
   

2. Configure an Action Configuration. For details, refer to Creating and Modifying Action Configurations.

   
   

   If you plan to utilize AD in Call Route, create an Action Set including the AD. Refer to Managing Action Sets.

   
   

   If you plan NOT to utilize AD in Call Routes, create an Action Set without the AD. Refer to Managing Action Sets.

Step 5: Configure Media List

1. Log into the WebUI. on to WebUI and navigate to Media List in navigation pane.
   
   

2. Create/Modify the Media List to have T.38 Media Profile and CNG Tone Detection enabled.

Step 6: Create Signaling Group

As depicted in Topology section, three signaling groups are needed to complete configuration for PBX - SBC - Exchange - Fax Server integration:

SBC - PBX

Ensure the relevant Action Set is applied to the ISDN Signaling Group. Refer to Creating and Modifying ISDN Signaling Groups.

SBC - Exchange UM

Ensure the relevant Media List is applied to the SIP Signaling Group. Refer to Creating and Modifying ISDN Signaling Groups.

SBC - Fax Server

Ensure the relevant Media List is applied to the SIP Signaling Group. Refer to Creating and Modifying ISDN Signaling Groups.

Licensing

Ensure DS1, SIP, and the Active Directory licenses are available in your node. For details, refer to Viewing Licenses.