Source note · Setting up CUBE as a Microsoft Teams Direct Routing SBC
The commercial and GCC Direct Routing FQDNs resolve to 52.112.0.0/14 and 52.120.0.0/14, and Microsoft says to allow signaling to and from all these ranges rather than only the addresses DNS returns.
Checked 2026-09-30
- Vendor
- Microsoft
- Product
- Microsoft Teams Phone
- Subsystem
- Direct Routing firewall
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Checked
- 2026-09-30
Sources
- Plan Direct Routing — Microsoft (Microsoft Learn) · tier 2 current vendor documentation · SIP signaling: FQDNs, IP ranges and Important note
Cite this note
APA
WarmTransfer. (2026, September 30). Setting up CUBE as a Microsoft Teams Direct Routing SBC: source note cube-teams-direct-routing-setup-signaling-ip-ranges. WarmTransfer. https://warmtransfer.net/knowledge/claims/cube-teams-direct-routing-setup-signaling-ip-ranges
BibTeX
@misc{warmtransfer-claim-cube-teams-direct-routing-setup-signaling-ip-ranges,
title = {Setting up CUBE as a Microsoft Teams Direct Routing SBC: source note cube-teams-direct-routing-setup-signaling-ip-ranges},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cube-teams-direct-routing-setup-signaling-ip-ranges},
note = {Source note cube-teams-direct-routing-setup-signaling-ip-ranges, checked 2026-09-30}
}