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 for Enterprise's migration from Skype for Business (SfB) On Premises to Microsoft Phone System (Teams). 

Network Topology - Skype for Business Server On-Premises Migration to Microsoft Phone System (Teams) Deployment

An enterprise may choose to deploy Teams Phone System services to clients using Skype for Business Server on-premises enterprise voice services. Two migrations scenarios exist: 

• Uniquely On-Premises deployment only
• Hybrid On-Premises deployment

Pre-Migration Uniquely On-Premises Deployment

All Skype for Business clients are homed to the On-Premises Skype for Business Server for voice services. No cloud-based VoIP services from Microsoft are used. A Ribbon SBC Edge device qualified for Skype for Business is deployed on the customer premises to support connectivity with the PSTN and legacy clients.

Pre-Migration Hybrid On-Premises Deployment

Skype for Business clients are homed to the Cloud PBX for voice services. No CCE is deployed; the Skype for Business Server provides services analogous to those provided by the CCE. A Ribbon SBC Edge device qualified for Skype for Business and the Skype for Business Server (deployed on premises) to support connectivity with the PSTN and legacy clients.

Post Migration - Hybrid and Uniquely On Premises Deployment

Following configuration, the Ribbon SBC Edge device offers certified Teams Phone System Direct Routing services to enterprise clients.

Step 1: Install SBC Edge

Step 2: Review Prerequisites for Microsoft Teams Direct Routing

Step 3: Configure Direct Routing from Skype for Business Server On-Premises

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 the 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 FQDN> -SipSignallingPort <SBC SIP Port> -MaxConcurrentSessions <Max Concurrent Session which SBC capable handling> -Enabled $true

   
   

4. Configure the Teams usage for the user:

   Code Block
   Get-CsOnlineUser -Identity user1@domain.com Grant-CsOnlineVoiceRoutingPolicy -PolicyName "GeneralVRP" -Identity user1@domain.com Grant-CsTeamsCallingPolicy -PolicyName AllowCalling -Identity user1@domain.com Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity user1@domain.com

   
   

Step 4: Configure TCP and TLS between SBC Edge and Skype for Business Server

For configuring TCP and TLS between the SBC Edge and Skype for Business server, there are two migration types:

• Migration from Hybrid On-Premises Deployment
• Migration from Uniquely On-Premises Deployment

See below for which migration applies to your network.

Anchor
Hybrid Hybrid

Migration from Hybrid On-Premises Deployments

These instructions apply to enterprises with a Hybrid On-Premises for Skype for Business on-premises deployment.

Using TCP between SBC and Skype for Business Server

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

For a successful migration, if the SBC is deployed with a private FQDN into Skype for Business On-Premises, do not change the SBC Hostname and Domain. Use the Public FQDN on the new SIP profile only.

Using TLS between SBC and Skype for Business Server

• For SBC Using Publicly-Owned Domain Name
  

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

If the SBC is deployed with a private FQDN in the Skype for Business Server, do not change the SBC Hostname and Domain. Use the Public FQDN on the new SIP profile only.

• For SBC Using Non-Owned Public Domain Name
  

  Note
  title Caution
  One TLS port can be attached to only one TLS profile. If your SfB deployment uses TLS 5061 as the Federated port, you must modify this Federated port to use a port other than 5061. To modify the Federated port, you must update the IP/PSTN Gateway's Listen Port of the SfB On-Premise topology and the Federated port of the SfB signaling group. If you cannot modify your SfB On-Premise topology, you can modify the port that Microsoft Teams Direct Routing uses. Make sure you update the Firewall, ACL, and Federated port of the Teams Signaling Group and Online PSTN Gateway.

  
  

Configure a domain name owned by the enterprise through the basic 

Anchor
Unique Unique

Migration from Uniquely On-Premises Deployments

These instructions apply to enterprises with a Uniquely On-Premises for Skype for Business Server deployment.

1. Enable split domain. For details, refer to: Configure Hybrid connectivity between Skype for Business Server and Office 365.

2. Move On-Premises users to Skype Online. For details, refer to: Move users between On-Premises and Cloud.

3. Follow the process related to hybrid on premises deployments as described Migrations from Hybrid On-Premises Deployments.
   

Anchor
step5 step5

Step 5: Configure SBC Edge for Microsoft Teams Direct Routing

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

Step 7: Confirm the Configuration

Validate SIP Option

1. In the WebUI, click the Settings tab.
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