Using SCCP 7945 Device profile on 8841's

[bencross89]

Hello,
We are moving towards replacing all our 7945 phones with 8841’s. As such we have 500+ extension mobility profiles. Beyond having additional lines is there any other beneficial reason to recreate these 7945 sccp profiles as 8841 sip profiles?

I did locate this thread on a similar question

https://community.cisco.com/t5/ip-telephony-and-phones/sip-device-profile/td-p/3091489

But it was more about the how the templates are affected and not anything else.

[Nithin Eluvathingal]

Replacing 7945 with 8841 You can make use of Phone migration feature if you are on CUCM, 14,5SU3,11.5SU8.

Its quite simple and easy. More details has been covered on CUCM Feature configuration Guides.

https://www.youtube.com/watch?v=A_Cila92cNQ

You can use the Bulk Administration Tool (BAT) to add and delete several user device profiles for Cisco Extension Mobility at one time. See the Bulk Administration Guide for Cisco Unified Communications Manager.

[bencross89]

Thanks for the response Nithin,

Great video, ill apply it to the few phones that dont have extension mobility users.

My issue pertains to the specific Extension mobility profiles the end users have. Most of our user base does not have their Ext on the physical phone but on their extension mobility profile. Is thier a reason to update the Profiles device type and Protocol type from 7945 and SCCP to 8841 and SIP. If so is the best method to delete the profile and recreate it?

[Jaime Valencia · Accepted solution]

Because EM profiles are specific to a device model, and there is equivalence for profiles (explained in the EM config guide) but that is applicable only to very similar phone models, your case does not apply for that as they're different protocols, models and generation of phones.

So, if you do not have a EM profile matching your device model, it will use the default device profile that you would have created for other phone models users might have available (also explained in the EM documentation) and that one not customizable per user. So if a user had a specific phone button template, and they end up using the default device profile, they'll use whatever phone button template the profile has, and not the one they actually use on their EM profile for their specific phone model. Which means if they had speed dials, and services, but the phone button template for the default profile has none, they won't be available to the users. 

[Mahmoud Belhaj]

use the Bulk Administration Tool to add and delete user device profiles