Extension Mobility and Mismatched User Device Profiles

A user device profile (UDP) is configured, used for Extension Mobility, is created with a device type. When the user associated with the UDP logs in to a dissimilar IP phone, the default device profile and phone button template is applied. For example, if a 7961 profile is loaded on a 7941 phone, the default phone button template is applied.

In the following example, a 7975 UDP is created; the UDP contains:

  • 2 x lines (2505 and 2506)
  • 1 x speed dial

The initial configuration of the Default Device Profile uses a Phone Button Template of "Standard 7941 SCCP" (1 Line, 1 SD). Observe the behaviour when the user logs in to a 7941 IP phone. The 1st line and 1st Speed Dial are displayed on the 7941 IP Phone.

The Default Device Profile ...

Click here to read the whole article and view images

Using BAT to Subscribe Phones to Extension Mobility

The Bulk Administration Tool is a powerful weapon in any Cisco IP Telephony Engineer's arsenal. In this article we look at a step-by-step guide to enabling Extension Mobility on IP phones that have already been deployed, and are known by CUCM.

Prerequisites:

  • Phones configured in CUCM
  • Extension Mobility service enabled on at least 1 CUCM in the cluster
  • Extension Mobility service configured in CUCM

BAT allows a query to be run and services dynamically added, based on a pre-configured Phone Template. In other words, we can subscribe to Services under the Phone Template, and then reference the template with a BAT query. The first step, then, is to create a Phone Template. When using the Phone Template solely for the purpose ...

Click here to read the whole article and view images