Page History

In this article, we illustrate how to configure the Sonus SBC 1000/2000 to

Call Routing Logic Overview

...

• Calling Party: PSTN phone 6228
• Called Party: Lync client with following AD profile:
  • userPrincipalName: baris@Sonus SBC 1000/2000DEMO.Sonus baris@SBCDEMO.Ribbon
  • homePhone: 3633
  • mobile: 6223
  • msRTCSIP-Line: tel:+15105743633;ext=3633
  • mail: Baris@uxdemo.net

...

...

...

Active Directory Related Setup

...

The AD query user must be a domain user. For this exercise, the following user is created in Sonus SBC 1000/2000DEMO.Sonus SBCDEMO.Ribbon domain where Lync is deployed.

• userPrincipalName: queryUser@Sonus SBC 1000/2000DEMO.Sonus queryUser@SBCDEMO.Ribbon
• dn: CN=queryUser,OU=Lync Clients,DC=Sonus SBC 1000/2000DEMOSBCDEMO,DC=SonusRibbon

Verification of Active Directory License

...

1. In the WebUI, click the Settings tab.
2. In the left navigation pane, go to System > Licensing > Current Licenses.

3. Verify that the Active Directory feature is licensed as shown below.

   Caption 0 Figure 1 Verify Active Directory License Image Removed

Domain Controller Settings

1. In the WebUI, click the Settings tab.
2. In the left navigation pane, go to Active Directory > Domain Controllers.
3. Add a domain controller.Configure the domain controller configuration items as shown below. Caption0Figure1Domain Controller Settings

   Image Removed

Active Directory Configuration

1. In the WebUI, click the Settings tab.
2. In the left navigation pane, go to Active Directory > Configuration.
3. Configure the relevant settings as shown below:

1. .

AD Query Functionality Verification

...

The query should return results similar to those shown below.

...

Telephony Routing Setup

Transformation Table Configuration

1. In the WebUI, click the Settings tab.
2. In the left navigation pane, go to Transformation.

3. Add an entry to the Transformation Table.

   Caption 0 Figure 1 Transformation Table Entry Image Removed

4. In the left navigation pane, select the Transformation Table created in the previous step.

5. Add two entries as shown below.

   Caption 0 Figure 1 Add Two Entries Image Removed

   Panel Expand Click here to see detailed information on AD-based routing via the transformation table

   :

   1. First Entry: Input Field - Called Address/Number  Output Field - User Value 1

   2. Second Entry: Input Field - User Value 1 Output Field - Called Address/Number  

       

       

      Panel
      borderStyle none

   Click here to see detailed information on AD-based routing via the transformation table

   1. Caption 0 Figure 1 AD-based Routing

   Via

   1. via Transformation Table Image Modified

    

    

Note 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.

Panel
borderStyle none
Caption 0 Figure 1 =telephoneNumber= Field Image Removed Image Added

Scenario

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.

Call Routing Table

1. In the WebUI, click the Settings tab.
2. In the left navigation pane, go to Call Routing Table > (relevant entry).

3. Select the appropriate Transformation Table in the Number/Name Transformation Tablelist box as shown below.

   Caption0Figure1Call Routing Table

   Image Removed

Verification of Call Routing using AD attributes

In order to properly verify the Sonus SBC 1000/2000 configuration, please follow these steps:

1. A PBX phone (6228) dials the Lync user's number (3633).
2. The call lands on the ISDN inbound Signaling Group on the Sonus SBC 1000/2000.
3. The call is then sent to the relevant Call Route Table Entry.
4. In the Call Route Entry, the incoming number is first transformed using the relevant call route entry (using the cached Active Directory user attributes) and is then routed to the relevant outbound Signaling Group.

You can see the AD usage in action via the WebUI log as shown below: