Page History

...

Overview

Microsoft Teams Direct Routing allows a direct connection between a supported, customer-provided SBC and the Microsoft Cloud in which services are provided to Teams calling clients. Microsoft has certified the SBC 1000/2000 for use with Teams Direct Routing. Perform the steps that follow to identify and investigate integration issues.

...

1. In the WebUI, click the Settings tab.
2. In the left navigation pane, click Signaling Groups.
3. For the signaling group configured for Microsoft Teams Direct Routing, click Counters.
4. Check for an increasing message count in Outgoing Options.If the number is not increasing, check the following:
   1. Confirm that the DNS server is properly configured and reachable.
   2. Confirm setup for Logial Interfaces (Node interfaces > Logical Interfaces), and the Default route in Protocols > IP > Static Routes.
   3. Confirm that the SBC certificate is valid.
5. Check for an increasing message count in Incoming 2xx. If the number is not increasing, check the following:
   1. Confirm that the SBC certificate is valid.
   2. Confirm firmware capability for the following software:
      

      1. Spacevars
         0 product

          7.0.2 or later, SBC Edge 8.0 or later for SBC 1000 and SBC 2000

      2. Spacevars
         0 product

          7.0.3 or later for 

         Spacevars
         0 series3

   3. Confirm that the firewall is properly configured to allow incoming SIP TLS messages.
   4. Confirm the ACL is using the proper IP address.
   5. Confirm that the SIP profile is properly configured. 
6. Check for an increasing message count in Incoming Options. If the number is not increasing, check the following:
   1. Confirm the firewall is properly configured to allow incoming SIP TLS message
   2. Confirm the federated IP is configured with sipwith sip-all.pstnhub.microsoft.com or with IP addresses from the following two subnets:
      1. 52.112.0.0, with netmask 255.252.0.0
      2. 52.120.0.0, with netmask 255.252.0.0
      For more information, refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan#microsoft-365-office-365-and-office-365-gcc-environments.
   3. Confirm the FQDN used in the SIP Profile > FQDN in the Contact Header field is the same FQDN that is defined in the Tenant.
      

   4. Confirm the FQDN used in the SIP Profile > FQDN in the Contact Header field resolves to the SBC public IP address. 

      Note

      For Microsoft Teams, the Signaling Group facing the Teams server must be configured as Spacevars 0 product 1 bold  FQDN or Static (if there is more than one signaling group connected to Teams Direct Routing). The FQDN in Contact Header should be the same FQDN used in Office 365 Tenant Online Gateway. If the IP Address of the SBC is configured in the Contact Header instead of the FQDN of the SBC, a Forbidden message is received.

       

   5. Confirm a Static Route (Protocols >  IP > Static Route) is configured to reach the Microsoft Public Server from your Public IP.

7. Check the message count in Outgoing 2xx. If the number is increasing, changes you made during validation have resolved the integration issue(s).
   

   Caption
   0 Figure 1 Check SIP Signaling Group Mesage Counters

   
   

...

Easy Configuration for Microsoft Teams uses SILK Narrowband  

...

Available SinceRelease8.1.5By default, Easy Configuration in the the

Spacevars
0 series3

configures SILK Narrowband for SILK. The best use of SILK Wideband is configured with another Wideband codec. Using SILK Wideband to G.711 does not increase voice quality and will diminish call capacity. 

...

For a Teams client located inside the corporate network: Place a call to the Carrier access on the Downstream SBC. If the call has media optimization, the Proxy SBC's Monitor screen displays DA; this indicates the media is direct between the Teams client and the Downstream SBC (see below). If the Proxy SBC's Monitor screen displays B, the Proxy SBC proxies the media and the media is not optimized.

Available_since
Type Available Since Release 8.1.5

 

Caption
0 Figure 1 Proxy SBC's Monitor Screen Displays DA

...

1. On the laptop running the Teams Client:
   1. Access  http://www.myipaddress.com/what-is-my-ip-address/ and take note of the Teams Client Public IP.
      
      

   2. Start a Command terminal, type the following command, and take note of the Teams Client internal IPv4 Address and Subnet Mask.

      
      

      Code Block
      ipconfig

      
      

2. Connect Office 365 Tenant via Powershell.
   
   

   1. Verify the Public IP address displayed earlier is listed when you type the following Office 365 Powershell command:

      Code Block
      Get-CsTenantTrustedIPAddress

      
      

   2. Verify the internal IPv4 Address and Subnet Mask displayed earlier is listed when you type the following Office 365 Powershell command:

      Code Block
      Get-CsTenantNetworkSite

      
      

TLS 1.2 Ciphers 

Available_since
Release 11.0.1

To avoid any service impact, ensure your SBC Edge platforms are configured to support TLS 1.2 and connect using one of the following cipher suites for the Direct Routing SIP interface:

• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 i.e. ECDHE-RSA-AES256-GCM-SHA384
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 i.e. ECDHE-RSA-AES128-GCM-SHA256
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 i.e. ECDHE-RSA-AES256-SHA384
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 i.e. ECDHE-RSA-AES128-SHA256

For more information, refer to MC297438.

"Replaces" Header

Available_since
Release 11.0.1

MS Teams Direct Routing will stop processing inbound SIP Requests which have "Replaces" headers. This change is automatically done by the SBC Edge software upgrade. No configuration changes are needed. For more information, refer to MC299922.

Pagebreak