Ribbon Documentation Portal will be unavailable Thursday February 2nd 2023 between 2:00 PM EST ~ 12:00 PM. More Info
Page tree
Skip to end of metadata
Go to start of metadata

Required Actions for Upcoming Changes to Microsoft Teams Direct Routing


Note

Software updates to Ribbon SBCs are available for customers with a current RibbonCare maintenance and support contract. Please contact your Ribbon sales representative or Ribbon partner if not in place.

Background:

Microsoft plans to make changes to Microsoft Teams Direct Routing signaling behavior in the first and second quarters of 2022. This bulletin provides an impact assessment of these changes for Ribbon Session Border Controllers (SBCs) as well as any actions required to platform configurations and/or software upgrades. Be aware, depending on the platform, you may need to take specific actions to assure uninterrupted service.

Analysis:

Ribbon has multiple SBC platforms to protect service providers and enterprises using Microsoft Direct Routing for Microsoft Teams including:

  • Edge SBCs
    • Includes Ribbon’s SBC Software Edition Edge (formerly SBC SWe Lite) and Cloud Native Edge (SBC CNe Edge),
    • SBC 1000 and SBC 2000
  • Intelligent Edge hardware
    • Includes EdgeMarc appliances
  • Core SBCs
    • Includes the SBC Software Edition (SBC SWe), SBC 5400 and SBC 7000
  • Ribbon Connect “as a Service” offers
    • Please refer to this Bulletin-21-00029973 = RIBBON CONNECT Direct Routing as a Service - Response to Microsoft Changes MC299922, MC299923, and MC307310

Please review the table below to understand whether changes are required to your Ribbon platform(s). 

As Microsoft is implementing changes to Direct Routing signaling in Q1 of 2022, it is critical that you make any required changes to your Ribbon platform(s) in a timely manner.

Note that the implementation dates provided in the table reflect the dates provided by Microsoft at the time this bulletin was written. Use the Microsoft link provided to review Microsoft’s latest implementation dates.

In configurations that include multiple Ribbon SBCs, please note that the changes below apply to the SBC (proxy SBC) that interfaces directly with Microsoft Teams. The downstream SBCs are not impacted by these changes. 

Software and Configuration Changes

The following table summarizes the impact assessment against each one of the above-mentioned platforms:

Microsoft ChangeMicrosoft's Announced Implementation Date*Required Ribbon Platform Changes
Edge SBCIntelligent EdgeCore SBC
MC299923: Direct Routing SIP interface will only trust certificates that are signed by Certificate Authorities (CAs) that are part of the
Microsoft Trusted Root Certificate Program.
February 1, 2022*NoneNoneNone
MC297438: TLS1.2 enforcement for Direct Routing SIP interfaceFebruary 1, 2022* (previously January 3, 2022)NoneNoneNone
MC307310: Microsoft's updated SIP signaling FQDN range to include IP subnet range and no longer use
sip-all.pstnhub.microsoft.com
June 1, 2022* (previously March 1, 2022)Yes¹. Suggested
software upgrade to 9.0.7
Availability
targeted for Feb 4, 2022
Yes². Software
upgrade to VOS
16.3.1. Availability
targeted for Feb 21, 2022

None.

Follow Ribbon
Microsoft
Teams guide

MC299922: Direct Routing will stop processing SIP requests which have
‘Replaces’ headers.
April 5, 2022*Yes. Software
upgrade to 9.0.7
Availability targeted for Feb 4, 2022
NoneNone

*Microsoft may unilaterally change implementation dates, please refer to the Microsoft link provided for each of the changes to confirm implementation timelines. 

¹Customers can manually make configuration changes to the existing software releases to support federated IP addresses for Microsoft Teams SIP trunks. However, you cannot use the platform’s configuration wizard to make changes or set up new trunks. A software upgrade is required to update the platform’s built-in configuration wizard.

²Software change is required to update the trusted list in the Microsoft Teams Routing Group configuration of the EdgeMarc to the recommended IP range Microsoft recommends.

Documentation Changes

The following table summarizes the impact assessment to documentation for the above-mentioned platforms:

Microsoft ChangeRequired Documentation Changes

Edge SBCIntelligent EdgeCore SBC
MC299923: Direct Routing SIP interface will only trust certificates that are signed by Certificate Authorities (CAs) that are part of the Microsoft Trusted Root Certificate Program.Yes. Documentation
updated to link Microsoft recommendation
Yes. Documentation
updated to link Microsoft
recommendation
None
MC297438: TLS1.2 enforcement for Direct Routing SIP interfaceNoneNoneNone

MC307310: Microsoft's updated SIP signaling FQDN range to include IP subnet range and no longer use
sip-all.pstnhub.microsoft.com

Yes. Follow Ribbon Microsoft Teams guide ³Yes. Follow Ribbon Microsoft Teams guide³

None

Follow Ribbon Microsoft Teams guide

MC299922: Direct Routing will stop processing SIP requests which have ‘Replaces’ headers.Yes. Follow Ribbon Microsoft Teams guide³NoneNone

³Documentation will be updated along with the software changes.

Recommendations:

Ribbon recommends reviewing the above tables to incorporate changes to continue uninterrupted service.

In connection with the above changes recently announced by Microsoft regarding changes to the Teams signaling logic, please note that Ribbon products should be covered by non-interrupted RibbonCare support which includes access to SW patches/updates/upgrades.

In cases where Customer has allowed RibbonCare support to lapse, Ribbon offers for fee a return to RibbonCare Support entitlement. Please contact your Ribbon authorized partner for details.