It is a good practice to go through the Microsoft 365 Admin Center's Message Center page at least twice a week. It's now become more of a morning ritual for me, opening the news app while enjoying my cuppa & casually browse through the Message Center page from the M365 admin dashboard (Under Health).
Of course as admins you can setup to receive the notifications via work email as well.
Admins should particularly focus on the updates which are tagged as a "Major Update" or "Admin Impact". The one we will discuss today is one of those.
Announcement (28th May 2021)
Last week, Microsoft announced two new DR endpoints will be added in the Japan region to increase the capacity & service improvement.
When Will This Happen ?
Beginning in late June & should be completed by early July (2021).
Connection Points For Signaling (as of today)
There are 3 FQDNs which serve as connection points for signaling for Teams.
sip.pstnhub.microsoft.com – Global FQDN – must be tried first.
sip2.pstnhub.microsoft.com – Secondary FQDN
sip3.pstnhub.microsoft.com – Tertiary FQDN
The ordering of these FQDNs is very crucial as the Session Border Controllers (SBCs) will query the one whose proximity is the nearest & hence would provide shortest optimal path. Another important factor is, it adds resiliency or failover capability in simpler terms.
Note: If your Firewall supports DNS, a single FQDN sip-all.pstnhub.microsoft.com can be populated & it'd resolve to all these IP addresses.
52.114.148.0
52.114.132.46
52.114.75.24
52.114.76.76
52.114.7.24
52.114.14.70
52.114.16.74 (Nov, 2020 - Australia)
52.114.20.29 (Nov, 2020 - Australia)
52.114.36.156 (May, 2021 - Japan)
52.114.32.169 (May, 2021 - Japan)
Do not forget to open the relevant ports for these two IPs (Japan) in your Firewalls & add these IPs in your ACLs (Access Control Lists) to allow inbound/outbound traffic for SIP Signaling.
Connection Points For Media (as of today)
52.112.0.0/14 (IP addresses from 52.112.0.1 to 52.115.255.254).
52.120.0.0/14 (IP addresses from 52.120.0.1 to 52.123.255.254).
References
Microsoft Roadmap # - MC258632
Note - We have not discussed the DOD/GCC O365 environments in this blog post.
Comments