...
Below is the call diagram example used as a configuration reference for the remainder of this document.
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Call Diagram Example |
---|
| Image Modified |
|
Panel |
---|
Step | Action |
---|
1 | PSTN call arrives at SBC. SBC processes corresponding SG, Call Route & Transformation Table | | Call Route/Transformation Table queries the AD cache. The called number is checked against all msRTCSIP-Line records per the Input portion of the transformation entry. | 2 | James' msRTCSIP-Line entry matches the called number, +15105743501. James' mobile number is returned from the AD cache. A call is placed to James' mobile, +14085551212. | | All of James' AD records are recorded into a record set. This record set is used for all subsequent AD queries for this call. | 3a | In forking the call to Lync, the next Call Route entry/Transformation Table is executed. The record set (not the AD cache) is searched to see if the called number matches the msRTCSIP-Line. This type of check is performed simply to ascertain if the called number belongs to a Lync user. If it matches, the same number that was searched is returned and the call request is forwarded to the Lync Server. | 3b | The Lync Server processes the INVITE, sending it out to James' Lync client |
|
...
- 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?
Panel |
---|
|
Caption |
---|
| Image Added |
|
Image Removed
ADSIedit showing a typical location for an AD search
- Does the SBC have a license for Active Directory?
Panel |
---|
|
Caption |
---|
| Image Added |
|
Image Removed
Tip |
---|
Active Directory is part of the SBC base license. The latest base licenses are available at Sonus Download Center. |
...
- Configuring a Domain Controller
- Setting the Configuration parameters the SBC will use to interoperate with the domain controller
Image Removed |
...
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Configuration for Individual Domain Controllers |
---|
|
|
...
| Image Added |
|
Image Removed |
...
Global Configuration for SBC-to-DC Interactions |
| Image Added |
|
SBC AD Configuration
The SBC must be configured for:
...
Click the Settings tab in the top nagivation, then select Domain Controllersin the left-hand navigation
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Domain Controllers |
---|
| Image Modified |
|
Enter the AD information for your network
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Enter AD Information |
---|
| Image Modified |
|
Click Configurationin the left-hand navigation.
Panel |
---|
|
Caption |
---|
| Image Modified |
|
Configure the Active Directory Configuration as shown. Add whatever Cache Attributesyou plan to use.
Tip |
---|
The minimum configuration for this example document should include the attributes: msRTCSIP-Line, name, displayName, mail, telephoneNumber |
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Active Directory Configuration |
---|
| Image Modified |
|
Active Directory Verification
With the AD configuration completed, click Refresh Cache.
Panel |
---|
|
Caption |
---|
| Image Modified |
|
Click Display Statisticsand verify that the AD queries are succeeding.
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Display Statistics |
---|
| Image Modified |
|
In the Domain Controller configuration, check the DC Status
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Domain Controllers Table |
---|
| Image Modified |
|
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Domain Controller Status |
---|
| Image Modified |
|
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 |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Active Directory Cache Query |
---|
| Image Modified |
|
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. |
...
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.
Panel |
---|
|
Caption |
---|
| Image Added |
|
Image Removed
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).
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Create Call Route Table |
---|
| Image Added |
|
Image Removed
3. Create a second transformation table with an entry to search for a msRTCSIP-Line entry that matches the called number.
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Create Transformation Table |
---|
| Image Added |
|
Image Removed
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.
Panel |
---|
|
Caption |
---|
| Image Added |
|
Image Removed
5. Your call route table should look like this:
Panel |
---|
|
Caption |
---|
| Image Added |
|
Image Removed
Section |
---|
Column |
---|
Info |
---|
Expand |
---|
| If you are planning to employ AD lookups for Lync Line URI (msRTCSIP-Line), your searches will likely require additional number translations. Click here to view some common number normalizations for msRTCSIP-Line AD lookups. |
---|
| If you are planning to employ AD lookups for Lync Line URI (msRTCSIP-Line), your searches will likely require additional number translations. Click here to view some common number normalizations for msRTCSIP-Line AD lookups. |
---|
| 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. Tip |
---|
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: Panel |
---|
| Caption |
---|
| Image Modified |
|
These are two common normalizations: Image Removed with Panel |
---|
| Caption |
---|
0 | Figure |
---|
1 | Normalize Cache set to True |
---|
|
| Image Removed | Image Added |
| with Normalize Cache set to False |
| Image Added |
|
If your Lync Line URI: looks like this: Panel |
---|
| Caption |
---|
| Image Modified |
|
These are two common normalizations for a 4 digit extension: Image Removed with Panel |
---|
| Caption |
---|
0 | Figure |
---|
1 | Normalize Cache set to True |
---|
|
| Image Removed | Image Added |
| with Normalize Cache set to False |
| Image Added |
|
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. |
|
|
|
|
...
The diagram below provides a pictorial representation for conceptualizing how data is processed through Transformation Table entries.
Panel |
---|
|
Caption |
---|
| Image Modified |
|