About this Page
- This document details how to configure the SBC for Active Directory-based call routing.
- This document explains how the SBC handles AD caching and repetative AD lookups.
Requires Sonus SBC1000/2000 Version 2.2 or later
This document assumes the user has a working knowledge of the SBC and its WebUI.
This document assumes the user has a working knowledge of Microsoft's Active Directory
Below is the call diagram example used as a configuration reference for the remainder of this document.
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?
Active Directory is part of the SBC base license. The latest base licenses are available at Sonus Download Center.
SBC Active Directory Reference
The following diagrams depict the SBC's Active Directory settings for:
- Configuring a Domain Controller
- Setting the Configuration parameters the SBC will use to interoperate with the domain controller
SBC AD Configuration
The SBC must be configured for:
- Active Directory Integration
- Forked Calling
- AD-based Call Routing
Active Directory Integration for Call Routing
Click the Settings tab in the top nagivation, then select Domain Controllersin the left-hand navigation
Enter the AD information for your network
Click Configurationin the left-hand navigation.
Configure the Active Directory Configuration as shown. Add whatever Cache Attributesyou plan to use.
The minimum configuration for this example document should include the attributes: msRTCSIP-Line, name, displayName, mail, telephoneNumber
Active Directory Verification
With the AD configuration completed, click Refresh Cache.
Click Display Statisticsand verify that the AD queries are succeeding.
In the Domain Controller configuration, check the DC Status
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.
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. Below are some common normalization transformations.
If Normalize Cache is configured to True, the tel: will automatically be removed from msRTCSIP-Line before the SBC caches the number. Setting Normalize Cache to True is recommended.
If your Lync Line URI: looks like this:
These are two common normalizations:
If your Lync Line URI: looks like this:
These are two common normalizations for a 4 digit extension:
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.
The diagram below provides a pictorial representation for conceptualizing how data is processed through Transformation Table entries.