Overview

Below is the call diagram example used as a configuration reference for the remainder of this document.

Prerequisites

Before

beginning the AD configuration, investigate and answer the following:

• The FQDN/IP of the Domain Controller
• What AD attribute will be used as key to retrieve records? msRTCSIP-Line, name, or mail are common AD attribute to set as the LDAP search criteria.
• What area of the Active Directory should be searched?

• ADSIedit showing a typical location for an AD search

• Does the SBC have a license for Active Directory?

• For details, refer to Viewing Licenses.

• Tip
  Active Directory is part of the SBC base license. The latest base licenses are available at

• Ribbon Support Portal - Download Center.

SBC Active Directory Reference

For details on configuring an entry in the Domain Controller Table, refer to Adding and Modifying Domain Controllers.

For details on configuring the Active Directory Configuration for SBC to Domain Controller interactions, refer to Configuring the SBC Edge for Active Directory.

SBC AD Configuration

The SBC must be configured for:

• Active Directory Integration
• Forked Calling
• AD-based Call Routing

Active Directory Integration for Call Routing

1. Access Settings and select Auth and Directory Services > Active Directory > Domain Controllers.
2. Enter the AD information for your network

1. .
2. Select Auth and Directory Services > Active Directory > Configuration.

3. Configure the Active Directory Configuration

1. :

   Tip
   The minimum configuration for this example document should include the attributes: msRTCSIP-Line, name, displayName, mail, telephoneNumber

   Panel
   borderStyle none
   Caption 0 Figure 1 Active Directory Configuration Image Added

Active Directory Verification

1. With the AD configuration completed, click Refresh Cache.

1. Click Display Statistics and verify that the AD queries are succeeding.

1. In the Domain Controller configuration,

1. ensure Status is Up.

2. Click the Tasks tab and click Active Directory Cache Query. In the form, pick an AD attribute from the pulldown and supply a corresponding value.

1. Note
   Queries of the msRTCSIP-Line must match precisely what appears in the Lync Line URI for the desired user, unless Normalized Cache is configured to True. If the cache is normalized, the tel: will be removed from the Lync User Line URI.

SBC AD-based Call Routing

Use the following instructions to create Call Routes and Transformation Tables that perform the call routing noted detail in the Summary section diagram.

1. Create a

1. Transformation table with an entry to search for a msRTCSIP-Line entry that matches the called number and returns the mobile number.

1. Create a new call route table, then a call route entry to the table.

2. Create

1. a second transformation table with an entry to search for a msRTCSIP-Line entry that matches the called number.

1. Add a second entry to

1. theCall Route table to send the call to the Lync Server. As before, add the transformation table above to the call route below

1. .

1. Info

1. It is often necessary to change (normalize) a number before performing an AD lookup. The vast majority of lookups require just the addition of +countrycode (i.e. +1 for the US) for a number that is already 10 digits (areacode+number). The Lync Line URI (msRTCSIP-Line) is different as it is always prepended with tel: and often postpended with ;ext=number. Since AD searches must be exact matches, the number must be corrected before the search.

1. The following are some common normalization transformations.

1. If Normalize Cache

1. is configured

1. to True, the tel: will automatically be removed from msRTCSIP-Line before the SBC caches the number.

1. Setting Normalize Cache

1. to True is recommended.

   Note
   If your Operating Mode is configured to Online, normalization should always include tel: as Normalize Cache is not available in Online mode. Online mode is not recommended.

If you are planning to employ AD lookups for Lync Line URI(msRTCSIP-Line), the searches will likely require additional number translations. See below for a few common number normalizations for msRTCSIP-Line AD lookups: 

If your Lync Line URI: looks like this:

...

Caption
0 Figure 1 Lync Line URI
Image Modified

These are two common normalizations:

...

...

...

...

Image Removed

...

...

...

Image Removed

...

...

Caption
0 Figure 1 Lync Line URI
Image Modified

 

These are two common normalizations for a 4 digit extension:

...

borderStyle	none

Caption
0

...

Table 1 Create Transformation Table 1 - Normalize Cache

...

Set to True

...

Image Removed

Input Field Type Input Field Value Output Field Type Output Field Value Match Type Called Address/Number (.*)(....) Called Address/Number +1\1\2;ext=\2 Mandatory Called Address/Number ==msRTCSIP-Line== Called Address/Number =mobile= Mandatory

...

Caption
0

...

Table 1 Create Transformation Table 2 - Normalize Cache

...

Set to False

...

Image Removed

Panel

Note
If your Operating Mode is configured to Online, normalization should always include tel: as Normalize Cache is not available in Online mode. As stated before, Online mode is not recommended.

Input Field Type Input Field Value Output Field Type Output Field Value Match Type Called Address/Number (.*)(....) Called Address/Number tel: +1\1\2;ext=\2 Mandatory Called Address/Number ==msRTCSIP-Line== Called Address/Number =mobile= Mandatory

Pagebreak

 

Additional Notes

The diagram below provides a pictorial representation for conceptualizing how data is processed through Transformation Table entries.

Panel
borderStyle none
Caption 0 Figure 1 Data Process Image Removed

 

...

Overview

Content Tools