This topic describes the configuration elements that the Cisco Unified Communications Manager Extension Mobility uses.
|Configuration Element Name||Configuration Element Function|
|Phone||Stores configuration of physical phones. Configuration parameters include device-specific phone parameters (such as device CSS, location, or MRGL), user-specific phone parameters (such as user MOH audio source, DND, or softkey template), and (user-specific) button configuration (such as lines or speed dials).|
|End user||The end user is associated with one or more device profiles. The user ID and the PIN are used to log in to a phone with Cisco Extension Mobility.|
|Device profile||Stores user-specific phone configuration in logical profiles. Configuration parameters include user-specific phone and button (lines, speed dials, etc.) parameters. The parameters of the device profile are applied to a physical phone after a user logs into the phone using Cisco Extension Mobility.|
|Phone service||Cisco Extension Mobility is implemented as a phone service. Hardware phones and device profiles need to be subscribed to the service.|
|Default device profile||Stores the default device-configuration parameters that should be applied when the phone model of the device profile of a user is different than the phone model of the phone on which the user logs in. A default device profile is automatically created for every phone model that has Cisco Extension Mobility activated.|
The figure lists the configuration elements that are related to Cisco Extension Mobility and describes their function. The configuration elements that are introduced with Cisco Extension Mobility are the device profile and the default device profile.
The device profile is configured with all the user-specific settings that are found at the device level of an IP phone (user MOH audio source, phone-button templates, softkey templates, user locales, DND and privacy settings, and phone service subscriptions) and all phone buttons (lines, speed dials, and so on). One or more device profiles are applied to an end user, in the End User Configuration window.
The default device profile stores default device-configuration parameters that Cisco Extension Mobility applies when there is a mismatch of the phone-model series on which the user logs in and the phone-model series that is configured in the device profile of the user. The default device profile exists once per phone-model type and per protocol (SIP and SCCP). All of the parameters that cannot be applied from the device profile of the user are taken from the default device profile.
For example, a user is associated with a device profile for a Cisco Unified IP Phone 7945 that runs SCCP. If this user logs in to a Cisco Unified IP Phone 7965 that runs SIP, some features (configuration parameters) that exist on the target phone are not configurable on the Cisco Unified IP Phone 7945 device profile. In this case, the configuration parameters that are unavailable on the device profile of the user are taken from the default device profile of the Cisco Unified IP Phone 7945 SCCP.
If a device profile includes more parameters than the target phone supports, the additional settings are ignored when the target phone with the user-specific settings is reconfigured.
The default device profile is not applied if a device profile of a user and the phone on which the user tries to log in are of the same phone-model series; for example, Cisco Unified IP Phone 7960, 7961, or 7965.
The Cisco Unified Communications Manager automatically creates a default device profile for a specific phone model and protocol, as soon as Cisco Extension Mobility is enabled on any phone-configuration page for this phone model.
Relationship of Cisco Extension Mobility Configuration Elements
The figure shows how the Cisco Extension Mobility configuration elements relate to each other.
As the figure shows, an end user is associated with one or more device profiles. For each possible IP phone model and protocol (SCCP and SIP), a default device profile can be configured. Because Cisco Extension Mobility is implemented as a Cisco IP phone service, all phones that should support Cisco Extension Mobility must be subscribed to the Cisco Extension Mobility phone service, to allow a user to log in to the phone. In addition, each device profile must be subscribed to the Cisco Extension Mobility phone service; this subscription is required to allow a user to log out of a phone.