After a Teams user puts an LMO call on hold and resumes it, the call continues via the central (proxy) SBC rather than the optimized path, because hold escalates the call to multiparty and it is by design never de-escalated.
Checked 2026-09-30
- Vendor
- Microsoft
- Product
- Microsoft Teams Phone Direct Routing
- Subsystem
- local media optimization
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-30
- Checked
- 2026-09-30
Sources
- Local Media Optimization for Direct Routing — Microsoft · tier 2 current vendor documentation · Known behaviors table, row 2
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-lmo-hold. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-media-bypass-setup-lmo-hold
BibTeX
@misc{warmtransfer-claim-teams-media-bypass-setup-lmo-hold,
title = {Setting up media bypass and local media optimization for Teams Direct Routing: source note teams-media-bypass-setup-lmo-hold},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-media-bypass-setup-lmo-hold},
note = {Source note teams-media-bypass-setup-lmo-hold, checked 2026-09-30}
}