Source note · CUCM to Teams Phone migration
Firewalls must allow Direct Routing signalling traffic to and from all Microsoft Teams IP ranges, not only the addresses returned by a DNS query for the SIP proxy FQDNs.
Checked 2026-09-21
- Vendor
- Microsoft
- Product
- Teams Phone
- Subsystem
- direct-routing-network
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-21
- Checked
- 2026-09-21
Sources
- Plan Direct Routing — Microsoft (Microsoft Learn) · tier 2 current vendor documentation · SIP signaling: FQDNs, Important callout after the IP range list
Cite this note
APA
WarmTransfer. (2026, September 21). CUCM to Teams Phone migration: source note cucm-to-teams-phone-firewall-all-ranges. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-to-teams-phone-firewall-all-ranges
BibTeX
@misc{warmtransfer-claim-cucm-to-teams-phone-firewall-all-ranges,
title = {CUCM to Teams Phone migration: source note cucm-to-teams-phone-firewall-all-ranges},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-to-teams-phone-firewall-all-ranges},
note = {Source note cucm-to-teams-phone-firewall-all-ranges, checked 2026-09-21}
}