sip-all FQDNs will not be supported starting March 1st, 2022
Aktualisiert: 10. Jan. 2022
Microsoft making some changes to Teams Direct Routing
On March 1, 2022, Microsoft will be removing support for sip-all.pstnhub.microsoft.com and sip-all.pstnhub.gov.teams.microsoft.us FQDNs from Direct Routing configuration.
Note: If you aren't using Session Border Controllers you can safely disregard this message.
How this will affect your organization:
When this change is implemented, if no actions taken and sip-all FQDN is used, users will no longer be able to make or receive calls via Direct Routing.
What you need to do to prepare:
Customers will need to use the recommended subnets (188.8.131.52/14 and 184.108.40.206/14) for any classification or ACL rules and discontinue using the sip-all FQDN when configuring Session Border Controls for the Direct Routing.
Source: Microsoft MC307310