Skip to end of metadata
Go to start of metadata

Not supported by SBC SWe Lite in this release.

In This Section...

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
  • Sonus Edge (SBC 1000/2000)
  • A third party Fax Server (i.e., RightFax, XMedius, etc.)

This document assumes the SBC is already configured with Exchange UM Server. See Best Practices - Upstream Deployment in PSTN - UX - eUM Server Setup.

Figure : 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.

Table : One Number Fax - Configuration through the WebUI

WebUI OptionWhat to Configure
Domain Controller and Active Directory
  • Domain Controller Configuration for AD query
  • AD Configuration for attributes (i.e: facsimileTelephoneNumber)
Action Configuration and Set
  • Action Configuration for One Number Fax call
  • Action Set Configuration for ONF call determination and logic
Transformation Tables
  • Transformation table for DIGIT dialing
  • Transformation table for AD normalization
  • Transformation table for non-digit dialing

 

Media List
  • Media List Configuration with T.38 and CNG Tone Detection
Signaling Group
  • ISDN Signaling Group with Action Set
Routing Tables
  • Routing Table for FAX calls
  • Routing Table for VOICE calls
Licensing
  • ISDN, DSP, and SIP licenses required for SBC - Exchange UM integration
  • One Number Fax feature is not controlled by license

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), as shown below:

    Figure : Create Domain Controller

     

    Navigate to Active Directory> Configuration and configure it as shown below:

    Figure : Configure AD

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.

    Figure : Create Transformation Entry - AD in Call Route

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 as shown below.

    NOTE: In the example below, the endpoint extension numbers and the eUM Subscriber Number are 3xxx-.

     

    Figure : Create Transformation Entry - Endpoint Extension and eUM Subscriber

  3. Log into the WebUI and navigate to Transformation.

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

    NOTE: 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.

     

    Figure : Create Transformation Entry - Fax Server by eUM

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:

    Figure : Create Fax Entry

     


    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:

    Figure : Create Voice Entry

Step 4: Create Action Configuration and Action Set

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

  2. Configure an Action Configuration as shown below:

    Figure : Configure Action Configuration Table


    If you plan to utilize AD in Call Route, create an Action Set as shown below:

    Figure : Use AD in Call Route

     

    If you plan NOT to utilize AD in Call Routes, create an Action Set as shown below:

    Figure : AD Not Used in Call Route

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 as shown below:

    Figure : Media List Configuration

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 as shown below:

Figure : Configure SBC - PBX

 

SBC - Exchange UM

Ensure the relevant Media List is applied to the SIP Signaling Group as shown below:

Figure : Configure SBC - Exchange UM

SBC - Fax Server

Ensure the relevant Media List is applied to the SIP Signaling Group as shown below:

Figure : Configure SBC - Fax Server

 

Licensing

Ensure DS1, SIP, and the Active Directory licenses are available in your node as shown below:

Figure : Licensing