In this article, we illustrate how to configure the SBC Edge (SBC) to query the User attributes stored in the SBC 1000/2000's Active Directory Cache in order to route calls to a user's mobile phone:

Call Routing Logic Overview

In this example, a call arrives from PSTN on a TDM port associated with an ISDN Signaling Group (SG), the SG points to a Call Routing Table which in turn specifies a Transformation Table.

The Transformation Table contains two entries, the first transformation strips the last four digits from the Called Number and appends them to a string tel:+1510774 for which the first part constitutes of a valid AD msRTCSIP-Line Active Directory user attribute entry. The second entry takes an msRTCSIP-Line entry and outputs the corresponding mobile phone number to the Destination Signaling Group.

For the purpose of this example the parties to the call and their relevant attributes are:

  • Calling Party: PSTN phone 6228
  • Called Party: Lync client with following AD profile:
    • userPrincipalName: baris@SBCDEMO.Sonus
    • homePhone: 3633
    • mobile: 6223
    • msRTCSIP-Line: tel:+15105743633;ext=3633
    • mail: Baris@uxdemo.net

(tick)

To see how SBC call routing works in general, refer to Working with Telephony Routing.

Active Directory Related Setup

AD Query User

In order to perform a successful query of either the AD cache or to query AD directly, a valid domain user must be specified in the Active Directory Configuration panel (see AD config section below, User Name field).

The AD query user must be a domain user. For this exercise, the following user is created in SBCDEMO.Sonus domain where Lync is deployed.

  • userPrincipalName: queryUser@SBCDEMO.Sonus
  • dn: CN=queryUser,OU=Lync Clients,DC=SBCDEMO,DC=Sonus

Verification of Active Directory License

Active Directory based call routing can only be preformed with an AD feature license - ensure you have this license installed:

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to System > Licensing > Current Licenses.

  3. Verify that the Active Directory feature is licensed as shown below.

    Verify Active Directory License

     

Domain Controller Settings

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to Active Directory > Domain Controllers.
  3. Add a domain controller.

    1. Configure the domain controller configuration items as shown below.

      Domain Controller Settings

Active Directory Configuration

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to Active Directory > Configuration.
  3. Configure the relevant settings as shown below:

Active Directory Configuration

AD Query Functionality Verification

  1. In the WebUI, click the Diagnostics tab.
  2. In the left navigation pane, go to Tools > Query AD Cache.
    In the Active Directory Cache Query page:
  3. Select userPrincipalName from the Property to Match list box.
  4. Enter the Lync user's userPrincipalName (i.e:James Smith) in the Value to Match field.
  5. Click OK.

The query should return results similar to those shown below.

AD Query Functionality Verification

 

 

Telephony Routing Setup

Transformation Table Configuration

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to Transformation.

  3. Add an entry to the Transformation Table.

    Transformation Table Entry

     

  4. In the left navigation pane, select the Transformation Table created in the previous step.

  5. Add two entries as shown below.

    Add Two Entries

     

     

    AD-based Routing via Transformation Table

     

     

Include tel: in a msRTCSIP-Line AD search if the SBC's Active Directory Configuration Operating Mode is configured to either Online, or Updates with the Normalization Cache set to False. Do not include tel: if the Normalization Cache is set to True. See Configuring SBC for Active Directory for more information.

AD Wild Cards

SBC supports the use of wild cards. This means that you can do partial matching in AD fields. The following is an example of how the =telephoneNumber= field is used to forward an inbound call to the user's new extension.

=telephoneNumber= Field

Scenario
Someone dials extension 3633, the four digits are added to the Area Code and prefix as well as the wildcard character, the result (User Value 1) is used in an AD query against the =telephoneNumber= field. The contents of the first =telephoneNumber= field containing the match string is then parsed for the last four digits, which are output from the transformation.

Call Routing Table

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to Call Routing Table > (relevant entry).

  3. Select the appropriate Transformation Table in the Number/Name Transformation Table list box as shown below.

    Call Routing Table

Verification of Call Routing using AD attributes

In order to properly verify the SBC configuration, please follow these steps:

  1. A PBX phone (6228) dials the Lync user's number (3633).
  2. The call lands on the ISDN inbound Signaling Group on the SBC.
  3. The call is then sent to the relevant Call Route Table Entry.
  4. In the Call Route Entry, the incoming number is first transformed using the relevant call route entry (using the cached Active Directory user attributes) and is then routed to the relevant outbound Signaling Group.

You can see the AD usage in action via the WebUI log as shown below:

AD Usage