Configuring Microsoft Teams

Microsoft Teams Direct Routing Configuration.

Consult the Microsoft documentation for detailed information on Direct Routing interface configuration guidelines, including the RFC standards and the syntax of SIP messages.

Obtain IP Address and FQDN

Requirements for configuring the SBC in support of Teams Direct Routing include:

Domain Name

For the SBC 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:

1. On the Microsoft Teams Tenant side, execute Get-CsTenant.
2. Review the output. 
3. Verify that the Domain Name configured is listed in the Domains and DomainUrlMap attributes for the Tenant. If the Domain Name is incorrect or missing, the SBC will not pair with Microsoft Teams.

Users may be from any SIP domain registered for the tenant. For example, you can configure user user@example.com with the SBC FQDN name sbc2.examplevoice.com, as long as both names are registered for the tenant.

Caption
0 Table 1 Domain Name Examples 3 Table 2 - Domain Name Examples
Domain Name Use for SBC FQDN FQDN names - Examples IPv4 Address rbbn.com Valid names: sbc1.rbbn.com 203.0.113.100  rbbnvoice.com Valid names: sbc2.rbbnvoice.com emea.rbbnvoice.com apac.rbbnvoice.com Invalid name: sbc2.emea.rbbnvoice.com (Requires registering domain name emea.rbbnvoice.com in “Domains” first) -

Configure Domain Names - Example

Obtain a Certificate

Public Certificate

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.
• Refer to Domain Name in Table 2 for certificate Common name formats.

Configure and Generate Certificates on the SBC

Microsoft Teams Direct Routing allows only TLS connections from the SBC for SIP traffic with a certificate signed by one of the trusted certification authorities.

Request a certificate for the SBC External interface and configure it based on the example using GlobalSign as follows:

• Generate a Certificate Signing Request (CSR) and obtain the certificate from a supported Certification Authority.
• Import the Public CA Root/Intermediate Certificate on the SBC.
• Import the Microsoft CA Certificate on the SBC.
• Import the SBC Certificate.

 The certificate is obtained through the Certificate Signing Request (instructions below). The Trusted Root and Intermediary Signing Certificates are obtained from your certification authority.

Configure Office 365 Tenant Voice Routing

A Tenant is used within the Microsoft environment as a single independent enterprise that has subscribed to Office 365 services; through this tenant, administrators can manage projects, users, and roles. Access the Tenant configuration and configure as detailed below. (For details on accessing the Tenant, refer to Microsoft Teams Documentation).

1. Create Online PSTN Gateway that points to the SBC:
   1. Enter the SBC FQDN (Example below: sbc1.rbbn.com). The FQDN must be configured for the Tenant in both the Domains and the DomainUrlMap fields.
   2. Enter the SBC SIP Port (Example below - SipPort5061).
      
      

       2. Configure Teams usage for the user:
                   a. Enter the User Identity (find example below - user1@domain.com)

Configure media bypass with Direct Routing

Media bypass enables you to shorten the path of media traffic and reduce the number of hops in transit for better performance. With media bypass, media is kept between the Session Border Controller (SBC) and the client instead of sending it via the Microsoft Phone System. To configure media bypass, the SBC and the client must be in the same location or network. (for details on Media-Bypass, refer Plan for media bypass with Direct Routing).

Media bypass can be enabled/disabled on the trunk.