Microsoft's media bypass planning page lists both 52.112.0.0/14 and 52.120.0.0/14 in its Media Processor and Transport Relay summary and as the subnets the pstnhub signaling FQDNs resolve to, but its Transport Relay and Media Processor port-requirement sections for Microsoft 365, Office 365 and GCC list 52.112.0.0/14 only.
Checked 2026-09-30
- Vendor
- Microsoft
- Product
- Microsoft Teams Phone Direct Routing
- Subsystem
- firewall
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Checked
- 2026-09-30
Sources
- Plan for media bypass with Direct Routing — Microsoft · tier 2 current vendor documentation · Use of Media Processors and Transport Relays, 'The IP ranges are'; SIP Signaling: FQDNs; Requirements for using Transport Relays; Requirements for using media processors
Cite this note
APA
WarmTransfer. (2026, September 30). Setting up media bypass and local media optimization for Teams Direct Routing: source note teams-media-bypass-setup-mb-range-52-120. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-media-bypass-setup-mb-range-52-120
BibTeX
@misc{warmtransfer-claim-teams-media-bypass-setup-mb-range-52-120,
title = {Setting up media bypass and local media optimization for Teams Direct Routing: source note teams-media-bypass-setup-mb-range-52-120},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-media-bypass-setup-mb-range-52-120},
note = {Source note teams-media-bypass-setup-mb-range-52-120, checked 2026-09-30}
}