Extension Mobility Questions Regarding Device Type

[Jason Amick]

I have read over some of the Cisco documentation on Extension mobility but an still unclear on what the device type refers to.  For example, if a user has a device profile configured with a device type of 7962 would they be able to login successful via EM to another device such as a cisco 8811 or 8945? The reason I ask is that one of our departments that leverage extension mobility had new phones ordered and some of the users have multiple lines (up to 5) configured so I would expect that if one of the users that have a device type of 7962 with 5 lines went to login to an 8945 phone then the 5th line would not show up as the 8945 only supports 4 line appearances.  Please let me know if you need additional information or if I am being unclear, Thanks for any help you can provide.

[Jitender Bhandari]

Hi Jason

There is a concept called "Extension Mobility Equivalency" read the below link and you will get your answer.

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/8_5_1/ccmfeat/fsgd-851-cm/fsem.html#wp1386088

HTH

JB

[Jason Amick]

Jitender:

Thanks for the reply.  So it looks like "Extension Mobility Equivalency" is a feature that is already there and does not take any administrative tasks to enable we just need to be aware of the amount of lines the user has configured but they can use any template on the system.  There also might be some features that will not be supported when swinging between one device type to the other.  Correct??  One of the things that was a concern is that the department that got new phones currently run on a 7962 (6 line) phone and now they are getting replaced with an 8945 (4 line) phones.  Most of the device profiles for these users have 4 lines configured but they are configured on line appearances 1, 2, 3, and 6.  So when the user logs into a 8945 they will not see that line that configured on line 6.  Would it be just as easy to just move that line appearance up to line 4 and then the user can see it when they login the their new 8945?

[Jitender Bhandari]

Jason,

if your phone supports "Extension Mobility Equivalency" then you can log in to multiple phone model without any issue, if if you have more lines configured on device Profile (DP) and your phone supports less likes then rest of the lines will not show up. And if your phone does not support "Extension Mobility Equivalency" then you would have to chose specific DP.

HTH

JB

[Jason Amick]

Jitender:

Thanks, just to clarify your last sentence.. Did you mean I would need to create a new profile with that specific device type if it does not support "Extension Mobility Equivalency".  Also the link you sent me does not list the 8945 model phone supported for "Extension Mobility Equivalency" but I tested and was able to login fine, I may just have to tweak some of the lines and move them up on their device profile. Thanks!!

And if your phone does not support "Extension Mobility Equivalency" then you would have to chose specific DP.

[Jitender Bhandari]

Jason,

that is the exact CUCM version you are running

JB

[Jason Amick]

Jitender:

We are running System version: 8.6.2.23900-10. Thanks!!

[Jaime Valencia]

No, that's wrong, the fact that a device does not have EM equivalency does NOT mean you need to configure a specific UDP for every single model there is.

That is the reason why you configure default device profile, the EM configuration guide explains this, and is listed as one of the things you should do.

Default Device Profile

You can configure a default device profile for eachCisco Unified IP Phone that you want to supportCisco Extension Mobility. The phone takes on the default device profile whenever a user logs in to a phone for which that user does not have a user device profile.

A default device profile includes device type (phone), user locale, phone button template, softkey template, and multilevel precedence and preemption (MLPP) information.

[Jitender Bhandari]

Jason,

My Bad, i missed out of Default Device Profile

In Cisco Unified Communications Manager Administration, use the Device > Device Settings > Default Device Profile menu path to configure default device profiles.

Use the default device profile for whenever a user logs on to a phone model for which no user device profile exists. To create a default device profile for each phone model that supports Cisco Extension Mobility, use the Default Device Profile Configuration window. The maximum number of default device profiles cannot exceed the number of phone models that support Cisco Extension Mobility.

For example, a user logs on to a Cisco Unified IP Phone 7960, for which there is a user device profile. The user device profile for the user gets downloaded to the phone to which the user logged on. Later, the same user logs on to a Cisco Unified IP Phone 7940, for which he does not have a user device profile. In this case, the default device profile for the 7940 gets downloaded to the phone.

A default device profile comprises the set of attributes (services and/or features) that are associated with a particular device. The default device profile contains attributes such as device type, user locale, phone button template, expansion modules, softkey template, Join Across Lines and Single Button Barge feature settings, multilevel precedence and preemption (MLPP) information, and IP phone services.

Cisco Extension Mobility (EM) equivalency eliminates the phone-model dependency of phone button templates.

HTH

JB

[Jason Amick]

Thank you both, I think I should be in good shape then if it will just use the default device profile when when a user that is configured with a UDP of a device type 7962 and logs into EM of an 8945 because I already have a default device profile setup for the 8945 phone model.  Thanks again!!