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:
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:
To see how SBC call routing works in general, refer to Working with Telephony Routing.
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.
Active Directory based call routing can only be preformed with an AD feature license - ensure you have this license installed:
Verify that the Active Directory feature is licensed as shown below.
Configure the domain controller configuration items as shown below.
The query should return results similar to those shown below.
Add two entries as shown below.
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.
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.
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.
Select the appropriate Transformation Table in the Number/Name Transformation Table list box as shown below.
In order to properly verify the SBC configuration, please follow these steps:
You can see the AD usage in action via the WebUI log as shown below: