If a user logs into a Cisco IP Phone model where the user does not have a configured user device profile, the login profile will not match the login device on authentication. In this scenario, the device profile default for that phone model gets loaded onto the phone, and Cisco CallManager Extension Mobility works as described here:
The system copies all device-independent configuration (that is, user hold audio hold audio source, user locale, userid, speeddials, and directory number configuration except for the setting "line setting for this device") from the user device profile to the login device.
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.
If the phone model supports Cisco IP Phone Services and they are configured, the services get copied from the user device profile.
Thanks for the information, I think you may have solved the issue as the user in question is using a 7940 EM profile, but logging into a 7960 phone. Not sure what the default profile is set to, but my guess is it's using a different softkey template than the user is expecting.
I'll try your suggestion and let you know the outcome.
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...