Source note · Troubleshooting Teams Direct Routing
For Microsoft 365, Office 365 and GCC, the SBC connects to the Microsoft SIP proxy on TLS port 5061. The signaling FQDNs resolve into 52.112.0.0/14 and 52.120.0.0/14 (IPv6 2603:1063:400::/40). Microsoft says to allow all these ranges in the firewall, not only the addresses DNS returns.
Checked 2026-09-25
- Vendor
- Microsoft
- Product
- Microsoft Teams Phone Direct Routing
- Subsystem
- sip-signaling
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- Plan Direct Routing — Microsoft (Microsoft Learn) · tier 2 current vendor documentation · SIP signaling: FQDNs (Important box); SIP signaling ports
Cite this note
APA
WarmTransfer. (2026, September 25). Troubleshooting Teams Direct Routing: source note teams-direct-routing-troubleshooting-signaling-fw. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-direct-routing-troubleshooting-signaling-fw
BibTeX
@misc{warmtransfer-claim-teams-direct-routing-troubleshooting-signaling-fw,
title = {Troubleshooting Teams Direct Routing: source note teams-direct-routing-troubleshooting-signaling-fw},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-direct-routing-troubleshooting-signaling-fw},
note = {Source note teams-direct-routing-troubleshooting-signaling-fw, checked 2026-09-25}
}