In this section:

Not supported by SBC SWe Lite in this release.

Overview — Configure the SBC Edge for On-Premise PBX Integration With Skype for Business

This Best Practice describes how to configure the SBC Edge for On-Premise (OnPrem) PBX integration with Skype For Business (SfB) when the Skype for Business Front End Pool is configured in Trusted Application mode. You must be familiar with configuring SBC Edge, MSFT Active Directory, DNS, and Skype For Business in order to perform these steps.

Configuration Steps

Configuration for this feature involves specific settings in the following entities:

  • DNS Server for creating an alias with SBC Edge's FQDN.
  • Skype for Business Management Shell to create a Trusted Application Pool and a Trusted Application ID.
  • Active Directory to create users in Domain Controller for the OnPrem endpoints, and the Skype for Business Control Panel to enable relevant AD users for SfB.
  • Configure all remaining settings for SFB integration.

Configure the DNS Server

Login to DNS using domain admin credentials and create an alias for SBC Edge

Create an Alias

Configure the SfB Management Shell

  1. Login to the Skype for Business Front End Server.
  2. Launch Skype for Business Server management shell.
  3. Type the following commands to create a Trusted Application Pool and Trusted Application ID:

Trusted App Pool: New-CsTrustedApplicationPool -Identity sbc1k122.sfb.tst -Registrar cspool.sfb.tst -Site 1

Trusted App ID: New-CsTrustedApplication -ApplicationId sbc1k122.sfb.tst -TrustedApplicationPoolFqdn sbc1k122.sfb.tst -Port 5061

Type the following command to enable CS Topology so that above configuration items can take effect in SfB topology:

Enable-CsTopology

Commands and Output

Configure the Active Directory and the SfB Control Panel

  1. Login to the Active Directory domain controller machine with domain admin credentials.
  2. Create AD users.
  3. Login to the Skype for Business front-end server.
  4. Launch the SfB Control Panel.
  5. Enable AD users to be enterprise-enabled SfB users on SfB Control Panel:

Enable AD Users

 

Configure the SBC Edge 

Configure the SBC Edge Host Name, Domain Suffix, and DNS IP Address

  1.  Login to the SBC Edge WebUI and navigate to Node Level Settings.
  2. Configure the SBC Edge host name, domain suffix, and the DNS IP address:

 

Verifying Certificates on the SBC Edge

  1. Login to the SBC Edge WebUI and navigate to Security > SBC Certificates.
  2. Verify that the Trusted CA Certificate and Ribbon Certificates are installed.

 

The following section describes SBC Edge analog FXS endpoints with Skype for Business in this setup:

Network Diagram: SBC Analog FXS Endpoints With Skype for Business

Determining Configuration Based on Inter-Op Mode

 After completing the basic configuration on the SBC Edge, the SBC Edge can be further integrated in one of three different modes. Click the link that applies to your integration:

  1. o365 with Contact Registrant Table (CRT)
  2. o365 with AD
  3. o365 with CRT and AD

o365 with CRT

This section assumes that projected OnPrem users are SBC Edge's FXS endpoints, and that the goal is to associate these endpoints with SBC Edge's Contact Registrant Table and register them with Skype for Business through the SBC Edge.

Creating Contact Registrant Table Entries

Create entries for OnPrem users (in this example they are associated to FXS endpoints). These entries must match with the Skype for Business users' SIP and tel: URI values. 

  1. Login to the SBC Edge WebUI and navigate to SIP > Contact Registrant Table.
  2. Create a new table.
  3. Create Contact Registrant Table entries. Ensure the Address of Record URI and SIP Contacts correspond to the entries with the SIP and tel: URI values in SFB database.

 

The user name, number, and URI association in the CRT must match the corresponding entries in the SfB Control Panel:

 Creating a CAS FXS Profile
  1.  Login to the SBC Edge WebUI and navigate to CAS >CAS Signaling Profiles.
  2. Create an FXS profile with configuration as shown below:

Creating a CAS FXS Profile

 

Creating an FXS to SfB Transformation Table
  1.  Login to the SBC Edge WebUI and navigate to Transformation.
  2. Create a Transformation Table with a desired number transformation entry. For example: a transformation table entry that will translate the 11-digit 15101221201 called number from FXS endpoints to +15101221201.
Creating an FXS to SfB Call Routing Table
  1. Login to the SBC Edge WebUI and navigate to Call Routing Table.
  2. Create a route between an FXS to SfB.  For details on call routing, refer to Creating and Modifying Entries to Call Routing Tables.

This Route Table entry will use the above transformation table entry and route this call to SIP Signaling group.

Creating a CAS FXS Signaling Group
  1. Login to the SBC Edge WebUI and navigate to Signaling Groups.
  2. Create a CAS FXS Signaling Group by applying the above call route and FXS profile. For details on Signaling Groups, refer to Creating and Modifying SIP Signaling Groups.

For example, in a Signaling Group, 4-digit numbers are defined in association of the OnPrem user's tel: URI numbers. For simplicity, 4-digit extensions of the tel: URI is used, such as 1201 for tel:+15101221201.

Creating an SBC Edge to FXS Transformation Table
  1. Login to the SBC Edge WebUI and navigate to Transformation.
  2. Create a Transformation Table with a desired number transformation entry.

For example, a transformation table entry will translate tel: URI number +15101221201 called number from SBC Edge to a 4-digit extension number that was used in CAS signaling group numbers such as 120.

Creating an SfB to FXS Call Routing Table
  1. Login to the SBC Edge WebUI and navigate to Call Routing Table.
  2. Create a Call  Routing Table that includes the Number/Name Translation Table created above.

This Route Table entry will use the preceding transformation table entry and route this call to FXS Signaling group.

Creating a Mediation Crypto Profile
  1. Login to the SBC Edge WebUI and navigate to Media > Media Crypto Profiles.
  2. Create a Mediation Crypto profile. For details, refer to Managing SDES-SRTP Profiles.
Creating a Mediation List
  1. Login to the SBC Edge WebUI and navigate to Media > Media List.
  2. Create a Mediation List. Ensure to apply the Crypto Profile because it is needed by SFB calls.
Creating a SIP Signaling Profile
  1. Login to the SBC Edge WebUI and navigate to SIP > SIP Profiles.
  2. Create a SIP Profile. For details, refer to Creating and Modifying SIP Profiles.
 Creating a SIP Server Table
  1.  Login to the SBC Edge WebUI and navigate to SIP > SIP Server Tables. Refer to Creating and Modifying Entries in SIP Server Tables.
  2. Create a SIP Server Table.

The earlier Contact Registrant Table is applied to the Server Table. This will allow CRT entries to register with Skype For Business.

Creating a SIP Signaling Group
  1. Apply the previously created SIP Profile, Media List, Call Routing Table, and SIP Server Table entries to this Signaling Group. In addition, set the inter-op mode as Office 365, and ensure that the Office 365 FQDN matches the dns suffix used in SfB user's profile.

o365 with AD

This section assumes that projected OnPrem users are SBC Edge's FXS endpoints and the goal is associate them with Active Directory users and to register them with Skype for Business through the SBC Edge.

Creating a CAS FXS Profile
  1. Login to the SBC Edge WebUI and navigate to CAS >CAS Signaling Profiles.
  2. Create an FXS profile. Refer to Creating and Modifying CAS Signaling Groups.
Creating an FXS to SfB Transformation Table
  1. Login to the SBC EdgeC WebUI and navigate to Transformation.
  2. Create a Transformation Table with a desired number transformation entry. For example, a transformation table entry can translate 11 digit 15101221201 called number from FXS endpoints to +15101221201.
Creating an FXS to SfB Call Routing Table
  1. Login to SBC Edge WebUI and navigate to Call Routing Table.
  2. Create a routing table. Ensure the Number/Name Tranformation Table created in the earlier step is added.

This Route Table entry will use the preceding transformation table entry and route this call to SIP Signaling group.

Creating an FXS Signaling Group
  1. Login to the SBC Edge WebUI and navigate to Signaling Groups.
  2. Create a CAS FXS Signaling Group by applying the above call route and FXS profile.

For example, in the Signaling Group, 4 digit numbers can be defined in association with the OnPrem user's tel: URI numbers. For the simplicity, 4 digit extensions of the tel: URI is used such as, 1201 for tel:+15101221201.

Creating an SBC Edge to FXS Transformation Table
  1.  Login to the SBC Edge WebUI and navigate to Transformation.
  2. Create a Transformation Table with a desired number transformation entry. For example, this transformation table entry can translate tel: URI number +15101221201 called number from the SBC Edge to a 4-digit extension number that was used in CAS signaling group numbers such as 1201.
Creating an SfB to FXS Call Routing Table
  1.  Login to the SBC Edge WebUI and navigate to Call Routing Table.
  2. Create a call routing table. Ensure the Number/Name Translation Table created previously is selected.

This Routing Table entry will use the preceding transformation table entry and route this call to FXS Signaling group.

Creating a Mediation Crypto Profile
  1.  Login to the SBC Edge WebUI and navigate to Media > Media Crypto Profiles.
  2. Create a Mediation Crypto Profile.
 Creating a Mediation List
  1.  Login to the SBC Edge WebUI and navigate to Media > Media List.
  2. Create a Mediation List. Make sure to apply the Crypto Profile because it is needed by SfB calls.
Creating a SIP Signaling Profile
  1.  Login to the SBC Edge WebUI and navigate to SIP > SIP Profiles.
  2. Create a SIP Profile. Refer to Creating and Modifying SIP Profiles.
Creating a SIP Server Table
  1. Login to the SBC Edge WebUI and navigate to SIP > SIP Server Tables.
  2. Create a SIP Server Table. Refer to Creating and Modifying Entries in SIP Server Tables.

The existing Contact Registrant Table is applied to the Server Table. This will allow CRT entries to register with Skype for Business.

Domain Controller and Active Directory

 If inter-op Mode is planned to be used as o365 w/AD PBX, the following configuration pieces must be completed:

  1. Domain Controller with relevant search scope for the OnPrem Users.
  2. Active Directory Configuration with relevant user attributes.

 

Two types of domain controllers are required: Call Route and On Premises.

  • Call Route. Supplies call routing information.
  • On Premises. Notifies AD that it will be looking up On Premise; this enables the user to enter data to narrow the search scope, and allows the proper user records to be retrieved quickly from the AD server.

 

In this case, the pager attribute is used  to query and to register the user with it. Ensure the AD user created with the pager attribute as shown below:

Pager Attribute set

Creating a SIP Signaling Group

Note that previously created SIP Profile, Media List, Call Routing Table, and the SIP Server Table entries are applied to this Signaling Group. In addition, the inter-op mode is set as Office 365 w/AD PBX, AD Attribute as pager, and the Office 365 FQDN is matching with the dns suffix that is used in SFB user's profile.

o365 with CRT and AD

This section assumes that candidate OnPrem users are the SBC Edge's FXS endpoints. The goal is to associate some of them with the SBC Edge's Contact Registrant Table, others with the Active Directory users, and then register them with Skype for Business via SBC Edge.

Creating Contact Registrant Table Entries

Create entries for OnPrem users (in this example they are associated with FXS endpoints) that must match with the Skype for Business users' SIP and tel: URI values.

  1.  Login to the SBC Edge WebUI and navigate to SIP > Contact Registrant Table.
  2. Create a new table.
  3. Create the relevant Contact Registrant Table Entries. Ensure the Address of Record URI and SIP Contacts match the SIP and tel: URI values in SFB database.
Creating a CAS FXS Profile
  1.  Login to the SBC Edge WebUI and navigate to CAS >CAS Signaling Profiles.
  2. Create an FXS profile. Refer to Creating and Modifying CAS Signaling Groups.
Creating an FXS to SfB Transformation Table 
  1. Login to the SBC Edge WebUI and navigate to Transformation.
  2. Create a Transformation Table with a desired number transformation entry.

 

For example, the transformation table entry can translate an 11 digit 15101221201 called number from FXS endpoints to +15101221201.

Creating an FXS to SfB Call Routing Table
  1. Login to SBC Edge WebUI and navigate to Call Routing Table.
  2. Create a Call Routing Table. Refer to Creating and Modifying Entries to Call Routing Tables.

 

This Route Table entry will use the preceding transformation table entry and route this call to SIP Signaling group.

 Creating an FXS Signaling Group
  1. Login to the SBC Edge WebUI and navigate to Signaling Groups.
  2. Create a CAS FXS Signaling Group by applying the above call route and FXS profile.

For example, in this Signaling Group, 4 digit numbers can be defined in association with the OnPrem user's tel: URI numbers. For the simplicity, 4 digit extensions of the tel: URI is used such as, 1201 for tel:+15101221201.

Creating an SBC Edge to FXS Transformation Table
  1.  Login to the SBC Edge WebUI and navigate to Transformation.
  2. Create a Transformation Table with a desired number transformation entry.

For example, this transformation table entry cantranslate tel: URI number +15101221201 called number from the SBC Edge to a 4-digit extension number that was used in CAS signaling group numbers such as 1201.

Creating an SfB to FXS Call Routing Table
  1.  Login to the SBC Edge WebUI and navigate to Call Routing Table.
  2. Create a call routing table.

This Routing Table entry will use the preceding transformation table entry and route this call to FXS Signaling group.

Creating a Mediation Crypto Profile
  1. Login to the SBC Edge WebUI and navigate to Media > Media Crypto Profiles.
  2. Create a Mediation Crypto Profile. For details, refer to Creating and Modifying SDES-SRTP Profiles.
Creating a Mediation List
  1.  Login to the SBC Edge WebUI and navigate to Media > Media List.
  2. Create a Mediation List. Make sure to apply the Crypto Profile because it is needed by SfB calls.
Creating a SIP Signaling Profile
  1.  Login to the SBC Edge WebUI and navigate to SIP > SIP Profiles.
  2. Create a SIP Profile.
Creating a SIP Server Table
  1. Login to the SBC Edge WebUI and navigate to SIP > SIP Server Tables.
  2. Create a SIP Server Table.

The existing Contact Registrant Table is applied to the Server Table. This will allow CRT entries to register with Skype for Business.

Domain Controller and AD

If inter-op Mode will be used as o365 with AD PBX, the following configuration steps must be completed.

  1. Domain Controller with relevant search scope for the OnPrem users.
  2. Active Directory Configuration with relevant user attributes.

In this case, the pager attribute is used to query and register the user. Make sure to have the AD user created with the pager attribute as shown below:

Pager Attribute

 

 

Configuring a SIP Signaling Group

Note that previously created SIP Profile, Media List, Call Routing Table, and the SIP Server Table entries are applied to this Signaling Group. In addition, the inter-op mode is set as Office 365 w/AD PBX, AD Attribute as pager, and the Office 365 FQDN is matching with the dns suffix that is used in SfB user's profile.

 

Signaling Group is configured with interop mode as Office 365 w/AD PBX and AD attribute as pager (for this exercise).

Enabling ICE Support for MS SfB EDGE Server Integration

If the Skype for Business Front End Pool is integrated with an EDGE Server, the SBC Edge must be configured with the following settings to support calls to/from SfB clients behind the EDGE Server:

  1. Remote Authorization Table Entry with the Realm of SfB's domain suffix, a valid domain user, and its credentials.
  2. SIP Server Table with the FQDN of the EDGE Server, Port 5062, protocol as TLS, the TLS profile that is used for SfB Front End Pool integration, and the Remote Authorization Table entry that is created in the previous step.
  3. Node Level SIP Settings that is configured with the EDGE SIP Server table (from the previous step) as EDGE Server Destination settings.
  4. Front End Pool SIP Signaling Group configured with ICE Support settings.