Summary

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

Before Beginning...

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 SBC Edge 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. Click the Settings tab in the top nagivationnavigation, then select Domain ControllersControllers in the left-hand navigation

   Panel
   borderStyle none
   Caption 0 Figure 1 Domain Controllers

2. Enter the AD information for your network

   Panel
   borderStyle none
   Caption 0 Figure 1 Enter AD Information

3. Click Configuration Configuration in the left-hand navigation.

   Panel
   borderStyle none
   Caption 0 Figure 1 Configuration

4. Configure the Active Directory Configuration as shown. Add whatever Cache AttributesAttributes you plan to use.

   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

   Pagebreak

Active Directory Verification

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

   Panel
   borderStyle none
   Caption 0 Figure 1 Refresh Cache

2. Click Display StatisticsStatistics and verify that the AD queries are succeeding.

   Panel
   borderStyle none
   Caption 0 Figure 1 Display Statistics

3. In the Domain Controller configuration, check the DC Status

   Panel
   borderStyle none
   Caption 0 Figure 1 Domain Controllers Table

   Panel
   borderStyle none
   Caption 0 Figure 1 Domain Controller Status

    

    

4. Select the Tasks tab in the top navigation and click Active Directory Cache Query. In the form, pick an AD attribute from the pulldown and supply a corresponding value.

   Panel
   borderStyle none
   Caption 0 Figure 1 Active Directory Cache Query

   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 transformation table with an entry to search for a msRTCSIP-Line entry that matches the called number and returns the mobile number.

2. Create a new call route table, then a call route entry to the table. In the example, the Calls to Mobile transformation table (above) is added to the call route (below).

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

4. Add a second entry to your Call Route table to send the call to the Lync Server. As before, add the transformation table above to the call route below.

5. Your call route table should look like this:

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.

The following are some common normalization transformations.

If your Lync Line URI: looks like this:

These are two common normalizations:

These are two common normalizations for a 4 digit extension:

Additional Notes

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