Page History

Overview

The SBC Edge is certified to offer Microsoft Teams Direct Routing services, and used to connect any Teams client to:

• A PSTN trunk, whether based on TDM (e.g. PRI, BRI, etc.), CAS, or SIP
• 3rd-party, non-Teams-certified SIP/TDM based PBXs, analog devices, and SIP clients

These instructions detail how to connect the SBC Edge (SBC 1000/2000 and SBC SWe Lite) for Enterprise's migration from Skype for Business Cloud Connector Edition with Phone System in Office 365 (Cloud PBX) to Microsoft Phone System (Teams).

Network Topology - Skype for Business Cloud Connector Edition (CCE) with Phone System in Office 365 (Cloud PBX) Migrates to Microsoft Phone System (Teams) Deployment 

An enterprise may choose to deploy Microsoft Phone System services (Teams Direct Routing) to clients presently receiving Skype for Business Cloud Connector Edition (CCE) with Phone System in Office 365 (Cloud PBX). The instructions below detail how to migrate services from Cloud Connector Edition (CCE) to Microsoft Phone System (Teams Direct Routing) services. 

In the following example, it is assumed a Ribbon SBC Edge device qualified for Skype for Business is already deployed on the customer premises.

Before Migration - Services from Skype for Business CCE (Cloud PBX)

 After Migration - Services from Microsoft Phone System (Teams)

Step 1: Install SBC Edge

Step 2: Review Prerequisites for Microsoft Teams Direct Routing

Step 3: Configure Direct Routing from Cloud Connector Edition (CCE)

Configure Tenant

These instructions configure the Tenant to connect  (pair) the SBC to the Microsoft Direct Routing Interface.

1. Access PowerShell. Refer to the PowerShell documentation.
2. Connect to the Tenant via Powershell.

3. Configure Microsoft Phone system Voice routing. As part of this process, use the following command to create an Online PSTN Gateway that points to the SBC:

   Code Block
   New-CsOnlinePSTNGateway -Fqdn <SBC Public FQDN> -SipSignallingPort <SBC SIP Port> -MaxConcurrentSessions <Max Concurrent Session which SBC capable handling> -Enabled $true

   
   

4. Configure Teams usage for the user:

   Code Block

   #### USER CCE -> Teams Get-CsOnlineUser -Identity user1@domain.com | Select-Object -Property UserPrincipalName,EnterpriseVoiceEnabled,HostedVoiceMail,OnPremLineURI,TeamsInteropPolicy,TeamsCallingPolicy,OnlineVoiceRoutingPolicy Grant-CsVoicePolicy -PolicyName "" -Identity user1@domain.com Set-CsUserPstnSettings -HybridPSTNSite "" -Identity user1@domain.com Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity user1@domain.com Grant-CsTeamsCallingPolicy -PolicyName AllowCalling -Identity user1@domain.com Grant-CsOnlineVoiceRoutingPolicy -PolicyName "GeneralVRP" -Identity user1@domain.com

   This can be reverted at any time with the following command:

   Code Block
   #### USER Teams -> CCE Grant-CsTeamsUpgradePolicy -PolicyName SfBOnly -Identity user1@domain.com Grant-CsTeamsCallingPolicy -PolicyName "" -Identity user1@domain.com Grant-CsOnlineVoiceRoutingPolicy -PolicyName "" -Identity user1@domain.com Grant-CsVoicePolicy -PolicyName Tag:HybridVoice -Identity user1@domain.com Set-CsUserPstnSettings -HybridPSTNSite aepsite1 -Identity user1@domain.com

   
   

   Info
   Wait at least ten minutes before the call is sent to the Skype client.

   Pagebreak

Step 4: Configure TCP and TLS between SBC and CCE

This section provides details on how to configure certificates for TCP and TLS between the SBC and Cloud Connector Edition (CCE).

Using TCP between SBC and CCE

Follow instructions posted below for basic Teams configuration (Step 5).

Using TLS between SBC and CCE

 There are two types of migration from CCE To Microsoft Teams to Direct Routing:

• Big Bang Migration. Resources are re-assigned from the CCE to Direct routing. After this migration, CCE functionality is no longer available. An Enterprise may choose a big bang migration to optimize costs associated with the migration.
• Smooth Migration. Resources are not re-assigned from the CCE to Direct Routing. After this migration, CCE functionality continues to remain available for select clients. Enterprises may choose a smooth migration when some level of Direct Routing testing is still required prior to CCE shutdown.

1. Depending on the migration type, load the Root Public CA, the Public certificate, and the private key on SBC as follows:

For a "big bang" migration:

1. 1. Access the WebUI. Refer to Logging into the SBC Edge.
   2. Click on the Tasks tab.
   3. Export the certificate and private key from CCE via Tasks > Office 365 Cloud Connector Edition > Setup > CCE Public Certificate > Export on PKCS12 format.

   4. From the left side menu, import the file via Certificates > Trusted CAs > Import Trusted CA certificate.

   5. From the left side menu, import the file via Certificates > SBC Primary Certificate > Import > PKCS12 certificate and key.
      
      

For a "smooth" migration:

1. 1. Access the WebUI. Refer to Logging into the SBC Edge.
   2. Click on the Tasks tab.

   3. From the left side menu, import the CA certificate via SBC Easy Setup > Certificates >Trusted CAs > Import Trusted CA certificate.
      

   4. From the left side menu, import the new certificate via Certificates > SBC Primary Certificate > Import > PKCS12 certificate and key.
      
      

2. Exchange the root certificate between the SBC and CCE via Tasks > Office 365 > SBC Easy Setup > CCE Private Certificate > Synchronize CCE/SBC CA Certificate. For details, refer to Managing Cloud Connector Edition Private Certificates.
   
   For details on certificates, refer to: Importing an SBC Edge Primary Certificate and Managing Trusted CA Certificates.
   Do not modify the node Hostname, but use the public name of SBC in the SIP profile.

Step 5: Configure SBC Edge for Microsoft Teams Direct Routing

Step 6: Configure SBC Edge when Microsoft Teams is in Media Bypass Mode and Non-Media Bypass Mode

Step 7: Confirm the Configuration

Validate SIP Option

1. Access the WebUI. Refer to Logging into the SBC Edge.
2. In the left navigation pane, access Signaling Groups.
3. For the signaling group configured for Microsoft Teams Direct Routing, click Counters.
4. Confirm the number of Incoming and Outgoing SIP Options.
5. Confirm the number of Incoming and Outgoing 2xx responses.

Step 8: Place a Test Call