Source note · CUCM to Teams Phone migration
To move from non-media bypass to media bypass while confirming functionality first, Microsoft documents creating a second trunk with a different FQDN pointing at the same SBC, with different TLS SIP signalling ports, a separate Online Voice Routing policy, and that policy assigned only to identified pilot users.
Checked 2026-09-16
If you're migrating to media bypass from non-media bypass and want to confirm functionality before migrating all usage to media bypass, you can create a separate trunk and separate Online Voice Routing policy.
- Vendor
- Microsoft
- Product
- Teams Phone Direct Routing
- Subsystem
- migration technique
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-16
- Checked
- 2026-09-16
Sources
- Plan for media bypass with Direct Routing — Microsoft · tier 2 current vendor documentation · Configure separate trunks for media bypass and non-media bypass
Cite this note
APA
WarmTransfer. (2026, September 16). CUCM to Teams Phone migration: source note cucm-to-teams-phone-media-bypass-staged-migration. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-to-teams-phone-media-bypass-staged-migration
BibTeX
@misc{warmtransfer-claim-cucm-to-teams-phone-media-bypass-staged-migration,
title = {CUCM to Teams Phone migration: source note cucm-to-teams-phone-media-bypass-staged-migration},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-to-teams-phone-media-bypass-staged-migration},
note = {Source note cucm-to-teams-phone-media-bypass-staged-migration, checked 2026-09-16}
}