Page History

...

1. In Sonus 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

...

1. To SIP (Lync) transformation

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

     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"

     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"

     Caption 0 Figure 1 Mobile Attribute Transformation Image Modified

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.

   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.

   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.

   Caption 0 Figure 1 To Mobile Image Modified

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):