SIP Device Profile

[mightyking]

Hello Everyone,

Migrating 7000 SCCP Phones to SIP. Users are using Extension Mobility (EM) to log into phones.

We have more than 5000 SCCP Device Profiles (EM). Do we need to migrate the DP to SIP as well or the SCCP DP will work with SIP Phones?

Thanks,

MK

[Brandon Buffin · Accepted solution]

With Extension Mobility Equivalency the SCCP profiles should work on SIP phones.

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/10_0_1/ccmfeat/CUCM_BK_F3AC1C0F_00_cucm-features-services-guide-100/CUCM_BK_F3AC1C0F_00_cucm-features-services-guide-100_chapter_011000.html#CUCM_RF_EDCB3C30_00

Extension Mobility Equivalency

Cisco Extension Mobility (EM) equivalency eliminates the phone-model dependency of phone button templates. The following factors determine the model equivalency among the various phones:

• Various features that the phone models support

• Number of buttons that the phone models support

EM equivalency allows the user to use any phone button template that is configured on the system.

Cisco Unified Communications Manager enhances the existing Extension Mobility (EM) equivalency mechanism to work across both SCCP and SIP protocols on the following models:

• Cisco 7906

• Cisco 7941

• Cisco 7941G-GE

• Cisco 7942

• Cisco 7945

• Cisco 7961

• Cisco 7961G-GE

• Cisco 7962

• Cisco 7965

• Cisco 7970

• Cisco 7971

• Cisco 7975

• Cisco IP Communicator

The enhancement works for all phone models that are size safe and requires no administration tasks to activate.

Note

The list of supported phone models varies per version and device pack. Log in to Cisco Unified Reporting to obtain the complete list of phone models that support these features in your installation. Within Cisco Unified Reporting, choose the Unified CM Phone Feature List system report. When generating this system report, specify All in the Product drop-down list box. In the Feature drop-down list box, specify Size Safe on Phone Template.

• Size Safe Feature
• EM Equivalency During Login

Size Safe Feature

If a phone model supports Size Safe on Phone Button Template, any phone button template can associate with that phone model. The actual phone button layout that displays on the phone shows the same order as the defined phone button template. If the phone model has more buttons than the phone button template, all defined buttons display. If the phone model has fewer buttons than the defined phone button template, only the buttons that are available on the phone display.

For example, a Cisco Unified IP Phone 7961 phone button template defines the following buttons:

• Line1

• Line2

• SD1

• SD2

• Line3

• Line4

When this phone button template gets assigned to a Cisco Unified IP Phone 7942, the actual phone button layout shows the following:

• Line1

• Line2

The rest of the template does not display because the buttons are not available.

When this phone button template gets assigned to a Cisco Unified IP Phone 7975, that actual phone button layout shows the following:

• Line1

• Line2

• SD1

• SD2

• Line3

• Line4

• Undefined

• Undefined

Thus, if a phone model supports the Size Safe on Phone Button Template feature, regardless of the login profile model, the user always sees the same order of the phone button template layout as that which gets defined with the login profile.

EM Equivalency During Login

Size safe phones use the template from the login profile and the template is applied as described in the preceding section.

Non-size safe phones must use the template that is associated with the default device profile for the model and protocol that matches the phone that the user logs into.

Note	The device that the user logs into must support Size Safe on Phone Template for EM Equivalency. The capability of the EM Profile does not effect EM Equivalency during login.

[mightyking]

Thank you Brandon,

MK

[Tech_Learner]

If the device profiles which are SCCP are used on SIP phones, will there be any problem with future CUCM releases?

Or is it necessary to move the sccp device profiles to sip while we are moving the sccp phones to sip? If yes, please explain how this can be done.