Page History

This article describes the steps necessary to configure the Sonus SBC 1000/2000

In this example we use a PSTN - Sonus SBC 2000 - Lync/SBA environment, and we want to route all calls from PSTN to Lync clients to a Lync user, and we want them forked to the same Lync user's mobile and IP phone numbers using attributes from the user's AD record.

...

A PBX phone 6222 dials the Lync/SBA user's extension number 1005, resulting in the call landing on the inbound ISDN Signaling Group on Sonus the SBC 1000/2000. The call is then routed using the relevant Call Route Table triggering the relevant sequence of events:

...

Verify the Call Forking License

1. In Sonus the SBC 1000/2000 WebUI, click the Settings Tab.
2. In the left navigation pane, go to System > Licensing > Current Licenses.
3. Verify that Call Forking Feature is licensed as shown below.

Verify Lync/SBA Configuration and AD Integration

Before you begin, make sure the Sonus SBC 1000/2000 is configured and integrated with Lync/SBA as described in Call Routing Based on Active Directory User Attributes. In addition to this, verify the Sonus SBC 1000/2000 Active Directory settings:

...

• Calling Party: PSTN phone 6222
• Called Party: Lync client with following AD profile:
  • userPrincipalName: SBAagent1@Sonus SBC 1000/2000DEMOSBAagent1@SBCDEMO.Sonus
  • ipPhone: 9911
  • mobile: 6228
  • msRTCSIP-Line: tel:+15102461005

...

SBC

...

Configuration

In this section, we provide a step-by-step configuration walk-through enabling the use of Call Forking on the Sonus SBC 1000/2000:

Transformation Table Configuration

...

1. To SIP (Lync) transformation

   • Configure the "Calling Address/Number" and "Called Address/Number" translations

     Panel
     borderStyle none
     Caption 0 Figure 1 SIP Transformation Image Modified

2. To ipPhone attribute transformation:
   • Configure the "Called Address/Number" translations to normalize it to a "User Value" of AD attribute format (msRTCSIP-Line)

   • Configure the "User Value" translation to another AD attribute format "ipPhone"

     Panel
     borderStyle none
     Caption 0 Figure 1 ipPhone Attribute Transformation Image Modified

3. To mobile attribute transformation:
   • Configure the "Called Address/Number" translations to normalize it to a "User Value" of AD attribute format (msRTCSIP-Line)

   • Configure the "User Value" translation to another AD attribute format "mobile"

     Panel
     borderStyle none
     Caption 0 Figure 1 Mobile Attribute Transformation Image Modified

     Pagebreak

Call Routing Table

We create three entries in a Call Route used for ISDN to Lync calls, as shown below:

1. ISDN to Lync/SBA client route entry
   Note that Fork Call is set to Enabled, so for a particular call will continue.

   Panel
   borderStyle none
   Caption 0 Figure 1 SBA: ISDN to SIP Image Modified

2. ISDN to Lync/SBA client's ipPhone route entry
   Note that Fork Call is set to Enabled, so routing for a particular call will continue.

   Panel
   borderStyle none
   Caption 0 Figure 1 To ipPhone Image Modified

3. ISDN to Lync/SBA client's mobile device route entry
   Note that Fork Call is set to Disabled, so routing for a particular call will stop at this entry.

   Panel
   borderStyle none
   Caption 0 Figure 1 To Mobile Image Modified

   Pagebreak

    

Inbound ISDN Signaling Group

The ISDN signaling group for inbound calls is configured to use the relevant Call Routing Table (configured in the previous section):