9.5 Cisco Extension Mobility Operation

This topic describes how Cisco Unified Communications Manager Extension Mobility works, how phone-model mismatches are processed, and how CSSs and partitions are updated when Cisco Extension Mobility is used.

  • User presses the Services button on an IP phone and selects the Cisco Extension Mobility service.
  • The user is authenticated by user ID and PIN.
  • After successful authentication, Cisco Extension Mobility selects the device profile associated with the user (prompts user to choose, if multiple associations exist).
  • The IP phone configuration is updated with the configuration parameters from the device profile.
  • The phone is reset and loads the updated configuration.

When a user wants to log in to a phone, the following sequence of events occurs:

  1. The user presses the Services button on the phone and chooses the Cisco Extension Mobility service from the list of phone services that are available on the phone.
  2. The Cisco Extension Mobility service requires the user to log in by using a user ID and PIN. The user enters the required data.
  3. If the entered user ID and PIN are correct, Cisco Extension Mobility chooses the device profile that is associated with the user.
    Note

    If a user is associated with more than one device profile, all associated profiles are displayed and the user must choose the desired profile. The reasons why you would configure multiple profiles for a single user could be the need for site-specific profiles or profiles for different phone models.

  4. The Cisco Unified Communications Manager updates the phone configuration with the settings of the chosen device profile. User-specific device-level parameters, lines, and other phone buttons are updated with user-specific settings.
  5. The IP phone is reset and loads the updated configuration.

Now, the phone can be used as it would be used in the home location. Directory numbers, speed dials, MWI, and so on, are all correct, regardless of the location and the IP phone that is used.

Users can log out of Cisco Extension Mobility by pressing the Services button and choosing Logout in the Cisco Extension Mobility service. If users do not log out themselves, the system automatically logs them out after the expiration of the maximum login time (if the appropriate service parameter has been configured accordingly).

The user is also automatically logged out of a phone when the user logs into another phone and when Cisco Unified Communications Manager is configured for autologout on multiple logins. Another option is that the next user of the phone logs out a previous user so that the new user can log in and have the phone that is updated with the settings of that new user. After logout, Cisco Unified Communications Manager reconfigures the phone with the standard configuration of the IP phone or by using another device profile (as specified in the Phone Configuration window).

Issues in Environments with Different Phone Models

This section describes issues with mixed IP phone environments.

  • Device profile configuration includes phone-model information.
  • Different configuration parameters are available, depending on the phone model that is selected.
  • What if a user logs into a different phone model than the model that is configured in the device profile of the user?
    1. Default device profiles can be configured.
    2. Default device profiles contain default phone-configuration parameters for the target phone.
  • What if a user logs into a different phone model than the model that is configured in the device profile of the user?
    1. Phone button template
    2. Softkey template
    3. Default values for parameters that might not be available at the device profile of the user (if the phone model specified there supports fewer features)
    4. Does not include lines or feature buttons

When different IP phone models are used in a Cisco Unified Communications Manager cluster for which Cisco Extension Mobility is enabled, an end user may log in to an IP phone that is of a different model series than the one that is configured in the device profile of the user.

Different phones support different features. Therefore, when a user logs in to a phone that supports more features than the features supported by the model that is associated with the user, the default device profile is used to apply the parameters that the target phone supports but that are not included in the device profile of the user. The default device profile includes phone-configuration parameters such as phone button templates, softkey templates, phone services, and other phone-configuration settings. However, the profile does not include button configuration (including line buttons).

Default Device Profile and Feature Safe

This section describes the feature safe functionality of Cisco Extension Mobility.

  • The default device profile is applied only if the phone model series is different (feature safe).
  • Phones can use any phone button template that has the number of line buttons that the phone model supports:
    1. Series 794x models are equivalent and can share a Cisco Extension Mobility profile.
    2. Series 796x models are equivalent and can share a Cisco Extension Mobility profile.
    3. Series 797x models are equivalent and can share a Cisco Extension Mobility profile.
  • No administration tasks are required to activate a Cisco Extension Mobility feature safe.
  • Cisco Extension Mobility feature safe is protocol-independent.

The default device profile is applied only if the user device profile and the phone on which the user tries to log in are of a different phone-model series (for example, Cisco Unified IP Phone Series 794x, 796x, or 797x).

When the phone-model series of the physical phone and the user device profile are the same, the feature safe function allows different phone models to be used for user device profiles and physical phone models.

For example, a user with an associated device profile for a Cisco Unified IP Phone 7940 phone can log in to a Cisco Unified IP Phone 7945 phone without having the default device profile applied.

No administrative tasks are required to enable feature safe. Feature safe is independent of the used signaling protocol (SIP or SCCP).

How Cisco Extension Mobility Handles Phone-Model Differences

This section describes the phone-configuration process when Cisco Extension Mobility is used with different phone models.

When a phone-model mismatch is identified, Cisco Extension Mobility does the following:

  • Default device profile:
    1. Applies device-dependent parameters, such as phone button and softkey template, from the default device profile
  • Device profile:
    1. Copies all device-independent parameters from the device profile of the user
    2. Copies device-dependent parameters that can be applied (such as phone lines and feature buttons, if supported by the applied phone button template)
    3. Applies phone-service subscriptions from the device profile of the user (if phone services are supported at the phone that is used)

After successful authentication, if the phone-model series of the device profile does not match the phone-model series of the used phone, the following happens:

  1. Device-dependent parameters, such as phone-button template and softkey template, from the default device profile are applied to the phone.
  2. Then the system copies all device-independent configuration settings (user hold audio source, user locale, speed dials, and line configuration, except for the parameters that are specified under Line Setting for This Device) from the device profile to the login device.
  3. Next, the applicable device-dependent parameters of the device profile of the user are applied. These parameters include buttons (such as line and feature buttons) that are based on the phone-button template that has been applied from the default device profile.
  4. Finally, if supported on the login device, phone-service subscriptions from the device profile of the user are applied to the phone.
  5. If the device profile of the user does not have phone services that are configured, the system uses the phone services that are configured in the default device profile of the login device.

For example, the following events occur when a user who has a device profile for a Cisco Unified IP Phone 7960 logs into a Cisco Unified IP Phone 7905:

  1. The personal user hold audio source, user locale, speed dials (if supported by the phone-button template that is configured in the Cisco Unified IP Phone 7905 default device profile), and directory number configuration of the user are applied to the Cisco Unified IP Phone 7905.
  2. The phone-button template and the softkey template of the default device profile are applied to the Cisco Unified IP Phone 7905.
  3. The user has access to the phone services that are configured in the Cisco Unified IP Phone 7905 default device profile.
Advertisements