Call2Teams - Customer/Partner
Microsoft have released the following advice:
We're making some changes to Teams Direct Routing
On March 1, 2022, we 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.
What do you need to know
This Microsoft change doesn’t impact the platform at all and existing call flows will continue to work as expected.
Explanation of Behaviour
Microsoft are making changes to their Direct Routing infrastructure. These periodic changes are normal and advance notification has been acted upon with necessary changes applied.