Page History

Overview

The SBC Edge is certified to offer Microsoft Teams Direct Routing services; the SBC Edge can be 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 configure the SBC Edge (SBC 1000/2000 and SBC SWe Edge) 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.

Network Topology - SBC Edge Deployed in a Microsoft Partner Network to Connect Microsoft Teams Direct Routing for Multiple Tenants

The network diagram below shows an SBC Edge device deployed at the Microsoft partner data center, including communication between:

• Tenants and the enterprise's legacy PBX based clients, and
• Tenants and the PSTN supported by the Microsoft partner.

Pagebreak

Ribbon SBC Edge at Microsoft Partner Data Center Supporting Multiple Tenants

Microsoft offer an advanced solution called "Carrier/Derived Trunk" that allows the Partner to control specific parameters on the end-user Tenants (list of codecs, port to use, Media Bypass activation, and such). This advance solution requires the following:

• Requires all the Derived Trunks (used by end customer) being a subdomain of the Carrier Trunk.
• Requires all Derived Trunks (used by end customer) to use Carrier Wild card certificate.
• Requires all the Derived Trunk (used by end customer) being configured with the same PSTN Gateway parameter (Codec, Max Call allowed, Media Bypass, and such).

For more information, refer to: https://docs.microsoft.com/en-us/microsoftteams/direct-routing-sbc-multiple-tenants.

How Call Traffic Routes between the SBC Edge and Microsoft Teams Tenants

The network topology supported are detailed below.

Topology 1 - ITSP Aggregation for all Teams Tenants

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

  

Topology 2 - ITSP Segregation per Teams Tenant

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

 

Topology 3 - Teams Tenant Segregation

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.

Info
This topology is not detailed in this Best Practice.

Teams Tenant Segregation

 

Step 1: Install SBC Edge (if required)

Excerpt Include
Connect SBC Edge Portfolio to Microsoft Teams Direct Routing Connect SBC Edge Portfolio to Microsoft Teams Direct Routing nopanel true

Multiexcerpt include
MultiExcerptName Installation PageWithExcerpt Connect SBC Edge Portfolio to Microsoft Teams Direct Routing

Pagebreak

Step 2: Prerequisites

Include Page
_Teams_Routing_Prerequisites_New _Teams_Routing_Prerequisites_New

Wildcard Certificate

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.

SBC Edge Configuration for Microsoft Teams Direct Routing 

Info
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.

• For SBC Edge Not configured for Microsoft Teams Routing: If the SBC Edge has not been configured for Microsoft Teams Direct Routing through the Easy Configuration Wizard, configure the SBC Edge per Connect SBC Edge Portfolio to Microsoft Teams Direct Routing. Once complete, move to Step 3 below.

OR

• For SBC Edge Previously Configured for Microsoft Teams Direct Routing: Move to Step 3.

Step 3: Configure each Tenant

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

Access the WebUI

You must access the SBC Edge's WebUI to configure the items below. To access the WebUI, refer to: Logging into the SBC Edge Portfolio.

Topology 1 - Configure the SBC for ITSP Aggregation for all Teams Tenants

To implement ITSP Aggregation, the SBC configuration must contain the following:

• Call traffic from the ITSP to Microsoft Teams uses a single SIP Signaling Group to Teams Direct Routing. The destination Tenant is included in the Transformation table; each Microsoft Teams Tenant requires a dedicated Transformation Entry that matches the Microsoft Online PSTN Gateway created on the Microsoft Teams Tenant.
• Call traffic from Microsoft Teams to ITSP uses the default call route to the ITSP.

Multi Tenant Routing on SBC Edge with ITSP Aggregation

Create a Transformation entry for the call from ITSP to the new Tenant

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.

1. In the WebUI, click the Settings tab.

2. In the left navigation page, access Call Routing > Transformation.
   

3. Select the Transformation Table called From Microsoft Teams: Passthrough (the entry created in the Easy Configuration Wizard).
4. Click the () icon.

5. Configure the parameters as shown below. Leave all other parameters as default.

6. 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

   
   

   Transformation Entry Tenant 2 - Example

   

   
   

Topology 2 - Configure the SBC for ITSP Segregation per Teams Tenant

To implement ITSP Segregation, the SBC configuration must contain the following:

• Call traffic from the ITSP to Microsoft Teams uses the single SIP Signaling Group to Teams Direct Routing. The destination Tenant is used in the Transformation table. Each Microsoft Teams Tenant requires a dedicated Transformation Entry that matches the Microsoft Online PSTN Gateway created on the Microsoft Teams Tenant.
• Call traffic from Microsoft Teams to the SBC Edge is aggregated onto the single SIP Signaling Group for all Tenants. The Call Routing Table associated with this SIP Signaling Group is configured to distribute the traffic to a specific ITSP, based on the original tenant (SIP: R-URI Domain).

Multi Tenant Routing on SBC Edge with ITSP Segregation

Info

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: Creating and Modifying SIP Signaling Groups Creating and Modifying Entries in SIP Server Tables Creating and Modifying Entries to Call Routing Tables Creating and Modifying Entries to Transformation Tables

Create a Transformation entry for the call from ITSP to the new Tenant

1. In the WebUI, click the Settings tab.

2. In the left navigation page, access Call Routing > Transformation.
   

3. Click on the Transformation Table > From SIP Trunk 2: Passthrough (the entry created when you added your ITSP 2 configuration).
4. Click the () icon.

5. Configure the parameters as shown below. Leave all other parameters as default.

6. 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
   

   

   
   

Create a New Transformation Table for the call from the new Tenant to ITSP 2

1. In the WebUI, click the Settings tab.
2. In the left navigation page, access Call Routing > Transformation.
   

3. Click the () icon at the top left corner to add a new Transformation Table.
   

4. 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

   

5. From the left navigation pane, click on the Transformation > From Microsoft Phone System Tenant 2 To ITSP 2 (the entry created in the last step).
6. Click the () icon.

7. Configure the parameters as shown below. Leave all other parameters as default.

8. 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
   

   

   
   

Add New Routing Table Entry for the Call from the new Tenant to ITSP 2

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:

1. In the WebUI, click the Settings tab.

2. From the left navigation pane, click on the Call Routing table. Click on the From Microsoft Teams Call Routing Table.  

3. Click the () icon to add an entry.
   

4. 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.

5. 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

   

   
   

Step 4: Confirm SBC Edge Links to Microsoft Teams

Multiexcerpt include
MultiExcerptName ConfirmLinks PageWithExcerpt Connect SBC Edge Portfolio to Microsoft Teams Direct Routing

Pagebreak

Step 5: Place a Test Call

Multiexcerpt include
MultiExcerptName TestCall PageWithExcerpt Connect SBC Edge Portfolio to Microsoft Teams Direct Routing