An unassigned number treatment whose range includes numbers still homed on Unified CM would probably also catch outbound Teams calls to those users and apply the treatment instead of sending them to the SBC, so ranges should probably exclude numbers still on Unified CM.
inferred · Checked 2026-09-25
- Vendor
- Microsoft
- Product
- Teams Phone
- Subsystem
- unassigned number routing
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Status
- inferred
- Checked
- 2026-09-25
Sources
- Configure routing options for unassigned phone numbers — Microsoft · tier 2 current vendor documentation · Notes section, last two bullets
Cite this note
APA
WarmTransfer. (2026, September 25). Unified CM and Teams Phone coexistence during a migration: source note cucm-teams-coexistence-inf-unassigned-range-overlap. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-teams-coexistence-inf-unassigned-range-overlap
BibTeX
@misc{warmtransfer-claim-cucm-teams-coexistence-inf-unassigned-range-overlap,
title = {Unified CM and Teams Phone coexistence during a migration: source note cucm-teams-coexistence-inf-unassigned-range-overlap},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-teams-coexistence-inf-unassigned-range-overlap},
note = {Source note cucm-teams-coexistence-inf-unassigned-range-overlap, checked 2026-09-25}
}