This article introduces MS Teams Direct Routing and Ribbon SBC Core, and describes the prerequisites for configuration.
About Teams Direct Routing
MS Teams Direct Routing allows connecting SBC Core, or a customer-provided SBC, to a Microsoft Phone System. You can connect the SBC to almost any telephony trunk, or connect it with third-party PSTN equipment.
About Ribbon SBC Core
Ribbon's Session Border Controllers (SBCs) provide robust security, simplified interoperability, advanced session management, and carrier-grade reliability for enterprises and service providers. Ribbon's SBCs offer powerful deployment flexibility that meets or exceeds the demanding levels of security and service quality for applications such as SIP trunking, Unified Communications, Network-Network Interconnection, VoLTE, VoWiFi, and RCS.
The Ribbon SBC Core supports MS Teams on the SBC 5110/5210/5400, SBC 7000, as well as the SBC SWe on KVM, VMware, Xen hypervisors or a private/public cloud.
Validated Ribbon SBC Version
Microsoft successfully conducted validation tests with Ribbon SBC Core versions V6.2 and V7.2. Other firmware versions may run successfully; however, Microsoft did not test such versions. For an updated list, refer
Before starting configuration, ensure that the following prerequisites are fulfilled:
- To enable direct routing, a Microsoft Phone System license is installed in MS Teams. For more information on Microsoft's licensing requirements, refer to
- Signaling Encryption and Media Encryption licenses are installed on the SBC.
- For multi-tenant MS Teams deployment, Advance ERE or PSX Access licenses are installed on the SBC. Basic ERE is sufficient for single-tenant MS Teams deployment.
The SBC performs a failover to another Office 365 site when the primary data center site is down. Currently, Microsoft Office 365 uses the following sites.
The following figure illustrates the configuration.
For information on infrastructure prerequisites, refer to the section "Infrastructure requirements" of Microsoft's document
- Session Border Controller (SBC)
- Telephony trunks connected to the SBC
- Office 365 tenant
- User registrar
- Public IP address for the SBC
- Fully Qualified Domain Name (FQDN) for the SBC
- Public DNS entry for the SBC
- Public trusted certificate for the SBC
- Connection points for Direct Routing
- Firewall IP addresses and ports for Direct Routing media
- Media Transport Profile
- Firewall IP addresses and ports for Microsoft Teams media
- Microsoft – For a list of Ribbon SBC products supported for MS Teams, refer to the following page on Microsoft's website -
- Ribbon – For more information, refer to the following page on Ribbon's website -
The following table describes the available routing options, based on the SBC with MS Teams deployment scenario:
Ribbon recommends using Basic ERE only for single-tenant deployments, and A-ERE or PSX for scalable multi-tenant MS Teams configuration.
To handle traffic for all MS Teams tenants configured on the SBC, this configuration uses a single IP Trunk Group, referred to as a Carrier Trunk, between MS Teams and the SBC.
To enforce CAC on a per-tenant basis, configure dummy trunk groups for each tenant.