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 is then changed (Device > Device Settings > Default Device Profile >> 7941) so that the Phone Button Template uses 2 Lines 0 SD. On the next occassion that the user logs into the same 7941 IP Phone, 2 Lines will be shown, and the Speed Dial is lost.
It is observed, then, that a mismatch in UDP versus IP Phone will always use the Default Device profile to determine phone button template.
7975 User Device Profile with 2 Lines 1 SD configured
Default Display on 7941 IP Phone for UDP w/ 2 Line 1 SD
Changing Default Device Profile of 7941
Effect of Changing the Default Device Profile
