Microsoft's monitoring pages describe no dedicated indicator of whether a given call was bypassed, so the practical evidence of the media path is on the SBC: the negotiated remote media address (client, Transport Relay or Media Processor range) and, with LMO, the X-MS headers received.
inferred · Checked 2026-09-30
- Vendor
- Microsoft
- Product
- Microsoft Teams Phone Direct Routing
- Subsystem
- verification
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Status
- inferred
- Checked
- 2026-09-30
Sources
- Monitor Direct Routing — Microsoft · tier 2 current vendor documentation · Whole page (no media-bypass indicator described); combined with ms-learn-dr-health-dashboard and ms-learn-dr-media-bypass port/range tables
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-inf-verify-at-sbc. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-media-bypass-setup-inf-verify-at-sbc
BibTeX
@misc{warmtransfer-claim-teams-media-bypass-setup-inf-verify-at-sbc,
title = {Setting up media bypass and local media optimization for Teams Direct Routing: source note teams-media-bypass-setup-inf-verify-at-sbc},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-media-bypass-setup-inf-verify-at-sbc},
note = {Source note teams-media-bypass-setup-inf-verify-at-sbc, checked 2026-09-30}
}