Skip to main content
8x8 Voice for Microsoft Teams: Microsoft Direct Routing Change Announcements
8x8 Support

8x8 Voice for Microsoft Teams: Microsoft Direct Routing Change Announcements

 

Overview

Microsoft recently made announcements regarding specific changes that it plans to make in 2022 to the way its Direct Routing service operates:

  • Direct Routing will stop processing SIP requests which have Replaces headers
  • Trusted Certificate Authorities for Direct Routing are changing
  • sip-all FQDNs will not be supported starting March 1st, 2022

In short, these proposed changes will not affect the 8x8 Voice For Microsoft Teams platform. Please see below for further details.

Applies To

  • 8x8 Voice for Microsoft Teams
  • Direct Routing

Announced Changes and Expected Impact

"Direct Routing will stop processing SIP requests which have Replaces headers"

What you need to know

This Microsoft change does not impact the 8x8 Voice for Microsoft Teams platform at all, and existing call flows will continue to work as expected.

What does this mean?

Replaces headers are used on an INVITE such that a new INVITE (call) can take over/replace an existing call. There are scenarios where INVITEs are sent in to the platform and a Replaces is used (e.g. some transfer scenarios or conference scenarios). These will continue to work the way they current do, which is the packet goes all the way through to the core SBC, at that point there is a configuration setting to ‘Handle Locally’. That basically means that the core SBC will handle the header/INVITE, and nothing will be sent upstream to Microsoft. The core SBC will handle closing off the old call and joining up the new one.

"Trusted Certificate Authorities for Direct Routing are changing"

What you need to know

This Microsoft change does not impact the 8x8 Voice for Microsoft Teams platform at all, and existing call flows will continue to work as expected.

What does this mean?

When Voice for Teams interfaces with Microsoft's Direct Routing endpoint, all SIP communication is carried out over a secure TLS connection. This connection uses publicly trusted certificates, trusted both by the Voice for Teams platform and by Microsoft. This allows encrypted traffic to be trusted and decrypted by Microsoft.

Certificates are issued in a tree structure, and it's common practice to amend the list of root certificate authorities that are considered trusted. Microsoft is giving notice of altering the list in this announcement.

"sip-all FQDNs will not be supported starting March 1st, 2022"

Microsoft recently announced that: "From March 1, 2022, it is removing support for sip-all.pstnhub.microsoft.com and sip-all.pstnhub.gov.teams.microsoft.us FQDNs from Direct Routing configuration. Users may no longer be able to make or receive calls via Direct Routing when this change is implemented if no actions are taken and these FQDNs are still used."

What you need to know

This Microsoft change does not impact the 8x8 Voice for Microsoft Teams platform at all, and existing call flows will continue to work as expected.

  • Was this article helpful?