On a model mismatch, Unified CM applies the device profile default for the login phone's model for the phone button template, softkey template and, where supported, the add-on module.
Checked 2026-09-24
The system uses the device profile default for that phone model for phone template and softkey template configuration and, if the phone can support addon modules, for the addon module.
- Vendor
- Cisco
- Product
- Cisco Unified Communications Manager
- Subsystem
- extension-mobility
- Deployment
- on-premises
- Region
- not restricted
- Release range
- Release 15 and SUs, current as of 2026-09-24
- Checked
- 2026-09-24
Sources
- Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Extension Mobility — Cisco Systems · tier 2 current vendor documentation · Extension Mobility Overview (login to a phone model that differs from the user device profile)
Cite this note
APA
WarmTransfer. (2026, September 24). Unified CM Extension Mobility and cross-cluster Extension Mobility: source note cucm-extension-mobility-model-mismatch-default-profile. WarmTransfer. https://warmtransfer.net/knowledge/claims/cucm-extension-mobility-model-mismatch-default-profile
BibTeX
@misc{warmtransfer-claim-cucm-extension-mobility-model-mismatch-default-profile,
title = {Unified CM Extension Mobility and cross-cluster Extension Mobility: source note cucm-extension-mobility-model-mismatch-default-profile},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/cucm-extension-mobility-model-mismatch-default-profile},
note = {Source note cucm-extension-mobility-model-mismatch-default-profile, checked 2026-09-24}
}