In this section:
The SBC Edge is certified to offer Microsoft Teams Direct Routing services; the SBC Edge can be used to connect any Teams client to:
These instructions detail how to configure the SBC Edge (SBC 1000/2000 and SBC SWe Lite) deployed with a Microsoft partner (sells telephony services delivered to Microsoft Teams) to connect Microsoft Teams Direct Routing services for multiple independent enterprise customers (Tenants). A Tenant is used within the Microsoft environment as a single independent enterprise that has subscribed to Office 365 services; through this Tenant, administrators manage projects, users, and roles. Refer to Configure a Session Border Controller for multiple Tenants for Microsoft partner requirements in support of multiple Tenants.
The network diagram below shows an SBC Edge device deployed at the Microsoft partner data center, including communication between:
Ribbon SBC Edge at Microsoft Partner Data Center Supporting Multiple Tenants
For more information, refer to: https://docs.microsoft.com/en-us/microsoftteams/direct-routing-sbc-multiple-tenants.
The network topology supported are detailed below.
This network topology is referred to as "Microsoft Teams Direct Routing Carrier." This topology enables the partner to offer Microsoft Teams external calling capability to the end customer. Usually the partner owns the ITSP contract. For lower cost routing, the partner can choose to have more than one ITSP; routing is then decided based on destination, time of the day, and such.
Routing Summary for ITSP Aggregation
This network topology is referred to as "Teams Direct Routing Bring your Own Trunk." This topology enables the partner to offer the SBC management to the end customer. Usually the end customer owns the ITSP contract; only a specific Tenant can use the associated ITSP.
ITSP Segregation per Teams Tenant
This network topology splits the inbound Teams traffic. For example, it can be useful to limit the number of sessions allowed per Teams Tenant from the SBC side or use a different certificate per Tenant. This topology requires an SBC configuration that limits the number of Tenants that can be supported on the SBC. Since this implementation requires one signaling port per Tenant, it does not support the Carrier/Derived Trunk capability.
This topology is not detailed in this Best Practice.
Teams Tenant Segregation
These instructions assume the SBC Edge product (SBC SWe Lite, SBC 1000/2000) is installed and running. If the product is not installed, refer to the links below. Installation Requirements On KVM: Installing SBC SWe Lite on KVM HypervisorProduct Installation SBC SWe Lite SBC 1000 Installing the SBC 1000 Hardware SBC 2000
Consult the Microsoft documentation for detailed information on Direct Routing interface configuration guidelines, including the RFC standards and the syntax of SIP messages.
Ensure you are running the latest version of SBC software:
Requirements for configuring the SBC Edge in support of Teams Direct Routing include:
SBC Edge Requirements
Requirement | How it is Used |
---|---|
Public IP address of NAT device (must be Static)* Private IP address of the SBC | Required for SBC Behind the NAT deployment. |
Public IP address of SBC | Required for SBC with Public IP deployment. |
Public FQDN | The Public FQDN must point to the Public IP Address. |
*NAT translates a public IP address to a Private IP address.
For the SBC Edge to pair with Microsoft Teams, the SBC FQDN domain name must match a name registered in both the Domains and DomainUrlMap fields of the Tenant. Verify the correct domain name is configured for the Tenant as follows:
Users may be from any SIP domain registered for the tenant. For example, you can configure user user@SonusMS01.com with the SBC FQDN name sbc1.hybridvoice.org, as long as both names are registered for the tenant.
Domain Name Examples
Domain Name* | Use for SBC FQDN? | FQDN Names - Examples |
---|---|---|
SonusMS01.com | Valid names:
| |
hybridvoice.org | Valid names:
Non-Valid name: sbc1.europe.hybridvoice.org (requires registering domain name europe. hybridvoice.org in “Domains” first) |
*Do not use the *.onmicrosoft.com tenant for the domain name.
Configure Domain Names - Example
The Certificate must be issued by one of the supported certification authorities (CAs). Wildcard certificates are supported.
Refer to Microsoft documentation for the supported CAs.
Ribbon recommends the deployment of the SBC Edge product behind a firewall, within the DMZ, regardless of the assignment of a public IP to the SBC in question. Refer to SBC Edge Security Hardening Checklist for more information about the SBC and firewalls.
This section lists the ports, protocols and services for firewalls that are in the path of the SBC connecting to Teams Direct Routing.
Microsoft Teams Direct Routing in support of multiple Tenants requires wildcard certificate support to protect the Microsoft partner's SBC FQDN and Tenant's SBC FQDN (that is, SAN=myMicrosoftPartner.com, SAN=*.myMicrosoftPartner.com). The SBC Edge products fully support wildcard certificates.
These instructions assume the SBC Edge has been configured for Microsoft Teams Direct Routing through the Easy Configuration wizard. For details on Easy Configuration, refer to: Working with SBC Easy Configuration.
OR
The SBC Easy Configuration wizard configures the SBC Edge for one Tenant; additional Tenants subscribed to Microsoft Office 365 services (Microsoft Teams Direct Routing) must be configured manually with the configuration items below. For documentation purposes, the following terms are used in the configuration examples.
Configuration Used in This Document
Configuration | Example used in this document |
---|---|
SBC FQDN for Microsoft partner | myMicrosoftPartner.com |
SBC FQDN for Tenant | tenant2.myMicrosoftPartner.com |
Microsoft description | Microsoft Phone System |
Tenant Name | Microsoft Phone System Tenant 2 |
You must access the SBC Edge's WebUI to configure the items below. To access the WebUI, refer to: Logging into the SBC Edge.
To implement ITSP Aggregation, the SBC configuration must contain the following:
Multi Tenant Routing on SBC Edge with ITSP Aggregation
In the SBC, configure a Transformation table entry for Teams Direct Routing (Entry #2 on previous diagram). This entry will match the input of the new end customer number and configure the proper Teams Tenant output.
In the left navigation page, access Call Routing > Transformation.
Configure the parameters as shown below. Leave all other parameters as default.
Click OK.
Transformation Entry Tenant 2 Configuration - Example
Parameter | Example Value |
---|---|
Description | To Microsoft Phone System Tenant 2 (example name) |
Match Type | Optional |
Input Type | Called Address/Number |
Input Value | <Enter Tenant 2 Phone Number > (\+151048512\d{2}) |
Output Type | SIP: Contact Domain |
Output Value | tenant2.myMicrosoftPartner.com |
Transformaton Entry Tenant 2 - Example
To implement ITSP Segregation, the SBC configuration must contain the following:
Multi Tenant Routing on SBC Edge with ITSP Segregation
The instructions below require that you have created the SIP Signaling Group, SIP Server Table, Call Routing Table, and Transformation Table for the new ITSP. For details, refer to the following:
In the left navigation page, access Call Routing > Transformation.
Configure the parameters as shown below. Leave all other parameters as default.
Click OK.
Transformation Entry Tenant 2 Configuration - Example
Parameter | Example Value |
---|---|
Description | From ITSP 2 To Microsoft Phone System Tenant 2 (example name) |
Match Type | Optional |
Input Type | Called Address/Number |
Input Value | (.*) |
Output Type | SIP: Contact Domain |
Output Value | tenant2.myMicrosoftPartner.com |
Transformation Entry Tenant 2 - Example
Click the
Configure the parameters as shown below and click OK. For details on parameter definitions, refer to Creating and Modifying Transformation Tables.
Transformation Table - Example Values
Parameter | Example Value |
---|---|
Row ID | Assigned by the system |
Description | From Microsoft Phone System Tenant 2 To ITSP 2 |
Create Transformation Table
Configure the parameters as shown below. Leave all other parameters as default.
Click OK.
Transformation Entry Tenant 1 Configuration - Example
Parameter | Example Value |
---|---|
Description | To ITSP 2 (example name) |
Match Type | Mandatory |
Input Type | SIP: R-URI Domain |
Input Value | (tenant2.myMicrosoftPartner.com):5061 |
Output Type | SIP: R-URI Domain |
Output Value | \1 |
Transformation Entry Tenant 2 - Example
The Easy Configuration process (used for initial configuration) creates the first connection to Teams Direct Routing. This configuration also creates two Call Routing Tables for transporting calls between the SBC's SIP Trunk and Microsoft Teams:
From SIP Trunk. Calls from SIP Trunk to Teams.
From Microsoft Team. Calls from Teams to SIP Trunk.
For calls to be routed from an individual Tenant to the proper ITSP, an entry must be added to the From Microsoft Teams Routing table (this Routing Table was created as part of Easy Configuration) for each Tenant. Add an entry in the From Microsoft Teams Call Routing table for each Tenant as follows:
From the left navigation pane, click on the Call Routing table. Click on the From Microsoft Teams Call Routing Table.
Configure the parameters as shown below. Leave all other parameters as default. For details on parameter definitions, refer to Creating and Modifying Entries to Call Routing Tables.
Click OK.
Call Routing Entry - Example Values
Parameter | Example Value |
---|---|
Description | To ITSP 2 |
Number/Name Transformation Table | From Microsoft Phone System Tenant 2 To ITSP 2 |
Destination Signaling Groups | ITSP 2 (from the previous steps) |
Create Call Routing Entry - Example
For troubleshooting steps, refer to Best Practice - Troubleshoot Issues with Microsoft Teams Direct Routing.
Place a test call as follows: Access the WebUI. Refer to Logging into the SBC Edge. In the WebUI, click the Diagnostics tab. In the left navigation pane, click Test a Call. Configure the parameters as shown below. Click OK. Place a Test Call - Parameters Parameter Value Destination Number Number assigned to a Teams user. Origination/Calling Number Number assigned to a Local user. Call Routing Table The routing table that handles the call from Microsoft Teams. Test a Call - Configuration Place a Test Call - Example The test call is now complete. For troubleshooting steps, refer to Best Practice - Troubleshoot Issues with Microsoft Teams Direct Routing.