You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Not supported by SBC SWe Lite in this release.

In This Section...

Overview — Configure the
Unable to show "metadata-from": No such page "_space_variables"
 for On-Premise PBX Integration With Skype for Business

This Best Practice describes how to configure the

Unable to show "metadata-from": No such page "_space_variables"
 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
Unable to show "metadata-from": No such page "_space_variables"
, 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
    Unable to show "metadata-from": No such page "_space_variables"
    '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

Unable to show "metadata-from": No such page "_space_variables"

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 
Unable to show "metadata-from": No such page "_space_variables"
 

Configure the 
Unable to show "metadata-from": No such page "_space_variables"
 Host Name, Domain Suffix, and DNS IP Address

  1.  Login to the
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Node Level Settings.
  2. Configure the
    Unable to show "metadata-from": No such page "_space_variables"
     host name, domain suffix, and the DNS IP address:

Configure Node-level Settings


Verifying Certificates on the 
Unable to show "metadata-from": No such page "_space_variables"

  1. Login to the
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Security > SBC Certificates.
  2. Verify that the Trusted CA Certificate and Sonus Certificates are installed:

Certificates

 

 

The following section describes

Unable to show "metadata-from": No such page "_space_variables"
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 

Unable to show "metadata-from": No such page "_space_variables"
, the 
Unable to show "metadata-from": No such page "_space_variables"
 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

Unable to show "metadata-from": No such page "_space_variables"
's FXS endpoints, and that the goal is to associate these endpoints with
Unable to show "metadata-from": No such page "_space_variables"
's Contact Registrant Table and register them with Skype for Business through the
Unable to show "metadata-from": No such page "_space_variables"
.

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
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to SIP > Contact Registrant Table.
  2. Create a new table.
  3. Create Contact Registrant Table entries as shown below. Make sure that highlighted values are correspondingly entered with the SIP and tel: URI values in SFB database.

Create Contact Registrant Table Entries


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

SfB Control Panel

 

Creating a CAS FXS Profile
  1.  Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to CAS >CAS Signaling Profiles.
  2. Create an FXS profile as shown below:

Creating a CAS FXS Profile

 

Creating an FXS to SfB Transformation Table
  1.  Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Transformation.
  2. Create a Transformation Table with a desired number transformation entry as shown below.

This transformation table entry will translate the 11-digit 15101221201 called number from FXS endpoints to +15101221201.


Transformation Table

 

Creating an FXS to SfB Call Routing Table
  1. Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Call Routing Table.
  2. Create a table as shown below.

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

Call Routing Table

Creating a CAS FXS Signaling Group
  1. Login to the
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Signaling Groups.
  2. Create a CAS FXS Signaling Group by applying the above call route and fxs profile as shown below.

In this 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 a CAS FSX Signaling Group

 

Creating an
Unable to show "metadata-from": No such page "_space_variables"
 to FXS Transformation Table
  1. Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Transformation.
  2. Create a Transformation Table with a desired number transformation entry as shown below.

This transformation table entry will translate tel: URI number +15101221201 called number from

Unable to show "metadata-from": No such page "_space_variables"
to a 4-digit extension number that was used in CAS signaling group numbers such as 120.


Creating an SBC to FXS Transformation Table

Creating an SfB to FXS Call Routing Table
  1.  Login to the
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Call Routing Table.
  2. Create a table as shown below.

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


Creating an SFB to FXS Call Routing Table


Creating a Mediation Crypto Profile
  1. Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Media > Media Crypto Profiles.
  2. Create a Mediation Crypto profile as shown below.

Creating a Media Crypto Profile

Creating a Mediation List
  1. Login to the
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Media > Media List.
  2. Create a Mediation List as shown below. Make sure to apply the Crypto Profile because it is needed by SFB calls.

Creating a Mediation List


 Creating a SIP Signaling Profile
  1. Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to SIP > SIP Profiles.
  2. Create a SIP Profile as shown below.

Creating a SIP Signaling Profile

 

 Creating a SIP Server Table
  1.  Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to SIP > SIP Server Tables.
  2. Create a SIP Server Table as shown below.

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 Server Table


Creating a SIP Signaling Group

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.


Creating a SIP Signaling Group

o365 with AD

This section assumes that projected OnPrem users are

Unable to show "metadata-from": No such page "_space_variables"
's FXS endpoints and the goal is associate them with Active Directoryusers and to register them with Skype for Business through the
Unable to show "metadata-from": No such page "_space_variables"
.

Creating a CAS FXS Profile
  1. Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to CAS >CAS Signaling Profiles.
  2. Create an FXS profile as shown below.

Creating a CAS FXS Profile

 

Creating an FXS to SfB Transformation Table
  1. Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
    C WebUI and navigate to Transformation.
  2. Create a Transformation Table with a desired number transformation entry as shown below.

This transformation table entry will translate 11 digit 15101221201 called number from FXS endpoints to +15101221201.


Creating an FXS to SFB Transformation Table

 

Creating an FXS to SfB Call Routing Table
  1. Login to 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Call Routing Table.
  2. Create a table as shown below

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


Creating an FXS to SFB Call Routing Table

 

Creating an FXS Signaling Group
  1. Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Signaling Groups.
  2. Create a CAS FXS Signaling Group by applying the above call route and FXS profile as shown below.

In this Signaling Group, 4 digit numbers are 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 FXS Signaling Group

Creating an
Unable to show "metadata-from": No such page "_space_variables"
 to FXS Transformation Table
  1.  Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Transformation.
  2. Create a Transformation Table with a desired number transformation entry as shown below.

This transformation table entry will translate tel: URI number +15101221201 called number from the

Unable to show "metadata-from": No such page "_space_variables"
to a 4-digit extension number that was used in CAS signaling group numbers such as 1201.


Creating an SBC to FXS Transformation Table


  

Creating an SfB to FXS Call Routing Table
  1.  Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Call Routing Table.
  2. Create a call routing table as shown below.

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


Creating an SFB to FXS Call Routing Table


Creating a Mediation Crypto Profile
  1.  Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Media > Media Crypto Profiles.
  2. Create a Mediation Crypto Profile as shown below:

 

OnPrem: Mediation Crypto


Creating a Mediation List
  1.  Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Media > Media List.
  2. Create a Mediation List as shown below. Make sure to apply the Crypto Profile because it is needed by SfB calls.

Creating a Mediation List

Creating a SIP Signaling Profile
  1.  Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to SIP > SIP Profiles.
  2. Create a SIP Profile as shown below.

Creating a SIP Signaling Profile

 

Creating a SIP Server Table
  1. Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to SIP > SIP Server Tables
  2. Create a SIP Server Table as shown below.

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


Creating a SIP Server Table

 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.

Domain Controller and Active Directory

 

In this case, we use the pager attribute to query and to register the user with it. Make sure to have 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.


Creating a SIP Signaling Group

o365 with CRT and AD

This section assumes that candidate OnPrem users are the

Unable to show "metadata-from": No such page "_space_variables"
's FXS endpoints. The goal is to associate some of them with the
Unable to show "metadata-from": No such page "_space_variables"
's Contact Registrant Table, others with the Active Directory users, and then register them with Skype for Business via
Unable to show "metadata-from": No such page "_space_variables"
.


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 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to SIP > Contact Registrant Table.
  2. Create a new table.
  3. Create the relevant Contact Registrant Table Entries as shown below; make sure that highlighted values are accordingly entered with the SIP and tel: URI values in SFB database.

 

Creating Contact Registrant Table Entries

 


The sequence and user name, number, and URI association should be similar to the following:

Contact Registrant Table - Result


Creating a CAS FXS Profile
  1.  Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to CAS >CAS Signaling Profiles.
  2. Create an FXS profile as shown below.

 

Creating a CAS FXS Profile


Creating an FXS to SfB Transformation Table 
  1. Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Transformation.
  2. Create a Transformation Table with a desired number transformation entry as shown below.

 

This transformation table entry will translate 11 digit 15101221201 called number from FXS endpoints to +15101221201.


Creating an FXS to SFB Transformation Table

 

 

 

Creating an FXS to SfB Call Routing Table
  1. Login to 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Call Routing Table.
  2. Create a table as shown below

 

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

 

Creating an FXS to SFB Call Routing Table


Creating an FXS Signaling Group
  1. Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Signaling Groups.
  2. Create a CAS FXS Signaling Group by applying the above call route and FXS profile as shown below.

In this Signaling Group, 4 digit numbers are 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 FXS Signaling Group

 

Creating an
Unable to show "metadata-from": No such page "_space_variables"
 to FXS Transformation Table
  1.  Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Transformation.
  2. Create a Transformation Table with a desired number transformation entry as shown below.

This transformation table entry will translate tel: URI number +15101221201 called number from the

Unable to show "metadata-from": No such page "_space_variables"
to a 4-digit extension number that was used in CAS signaling group numbers such as 1201.


Creating an SBC to FXS Transformation Table

Creating an SfB to FXS Call Routing Table
  1.  Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Call Routing Table.
  2. Create a call routing table as shown below.

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


Creating an SFB to FXS Call Routing Table


Creating a Mediation Crypto Profile
  1.  Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Media > Media Crypto Profiles.
  2. Create a Mediation Crypto Profile as shown below:

OnPrem: Mediation Crypto

 


Creating a Mediation List
  1.  Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to Media > Media List.
  2. Create a Mediation List as shown below. Make sure to apply the Crypto Profile because it is needed by SfB calls.

Creating a Mediation List

 

Creating a SIP Signaling Profile
  1.  Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to SIP > SIP Profiles.
  2. Create a SIP Profile as shown below.

Creating a SIP Signaling Profile


Creating a SIP Server Table
  1. Login to the 
    Unable to show "metadata-from": No such page "_space_variables"
     WebUI and navigate to SIP > SIP Server Tables
  2. Create a SIP Server Table as shown below.

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


Creating a SIP Server Table

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.

Search Scope and Relevant AD 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 with interop mode as Office 365 w/AD PBX and AD attribute as pager (for this exercise).

Creating a SIP Signaling Group


Enabling ICE Support for MS SfB EDGE Server Integration

If the Skype for Business Front End Pool is integrated with an EDGE Server, the 

Unable to show "metadata-from": No such page "_space_variables"
 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 as shown below.
  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 as shown below.
  3. Node Level SIP Settings that is configured with the EDGE SIP Server table (from the previous step) as EDGE Server Destination settings as shown below.
  4. Front End Pool SIP Signaling Group configured with ICE Support settings as enabled as shown below:

 

Enabling ICE Support

 

 


 



 

  • No labels