Extension mobility in 7.1(2) change or same as 4.2(3)

Answered Question
Nov 25th, 2009

We are preparing to upgrade to the Call Manager 7.1(2).

Does a user with extension mobility still have to login to the same phone model?

In 4.2(3 )For example,  User A has a 7961 on their desk.  User A has device profile with device type is 7961. 

Remote desk phone is 7961.  Everything matches.

In 7.1(2)  Can User A have a 7941 on their desk and login into a 7961?  Im guessing NO but want to make sure.

I have this problem too.
0 votes
Correct Answer by rob.huffman about 7 years 4 days ago

Hi Thomas,

Here is a clip that describes the CCM 4.x behaviour;


On authentication, if the login profile matches the login device (that is, the user has a user device profile that is configured for a Cisco IP Phone Model 7960 and logs into a Cisco IP Phone Model 7960), Cisco CallManager Extension Mobility behaves:


The phone automatically reconfigures with the individual user device profile information.


If the user has one user device profile, then the system uses this profile. If the user has more than one user device profile, the user can choose the user device profile that will be used from a list.


The user can access all the services that the user configured on the device profile.


If that same user logs into a Cisco IP Phone model where the user does not have a configured user device profile, the login profile will not match the login device on authentication. In this scenario, the system loads the device profile default for that phone model onto the phone, and Cisco CallManager Extension Mobility works as described here:


The system copies all device-independent configuration (that is, user hold audio hold audio source, user locale, userid, speeddials, and directory number configuration except for the setting "line setting for this device") from the user device profile to the login device.


The system uses the device profile default for that phone model for phone template and softkey template configuration and, if the phone can support addon modules, for the addon module.


If the phone model supports Cisco IP Phone Services and they are configured, the system copies the services from the user device profile.


If the user device profile does not have Cisco IP Phone Services configured, the system uses the Cisco IP Phone Services that are configured in the device profile default for the login device that is accessed during login. If parameters exist for the subscriber service, the system copies the parameters from the device profile default and the parameters may not reflect the correct information.


For example, the following scenarios occur when a user who has a user device profile that is configured for Cisco IP Phone Model 7960 logs in to a Cisco IP Phone Model 7905, and the device default profile is loaded on the phone.


The user can access the user's hold audio source, user locale, userid, speeddials and directory number configuration. The user cannot access his phone line setting; the system configured the phone line setting from the device profile default that is configured for the Cisco IP Phone Model 7905.


The user can access the phone template and the softkey template of the Cisco IP Phone Model 7905.


The user cannot access an addon module because Cisco IP Phone Model 7905 does not support it.


The user can access Cisco IP Phone Services if they are configured for the Cisco IP Phone 7905, but, the parameters from the subscriber services will reflect the device profile default, not the parameters that the user chose on the User Options window.



http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/4_2_1/ccmfeat/fsem.html#wp1146344


Here is one of the main CUCM 7.x EM changes;

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 includes the following support feature for the Cisco Unified IP Phones:


Feature Safe on Phone Button Template-Phones can use any phone button template that has the same number of line buttons that the phone model supports.


Release 7.0(1) of Cisco Unified Communications Manager enhances the existing Extension Mobility (EM) equivalency mechanism. The equivalency enhancement works across phone types as follows:


7940 SCCP, 7941 SCCP, 7942 SCCP, and 7945 SCCP models, which are equivalent, can share an EM profile.


7940 SIP, 7941 SIP, 7942 SIP, and 7945 SIP models, which are equivalent, can share an EM profile.


7960 SCCP and 7961 SCCP models, which are equivalent, can share an EM profile.


7962 SCCP and 7965 SCCP models, which are equivalent, can share an EM profile.


7960 SIP, 7961 SIP, 7962 SIP, and 7965 SIP models, which are equivalent, can share an EM profile.


7970 SCCP and 7971 SCCP models, which are equivalent, can share an EM profile.


7970 SIP, 7971 SIP, and 7975 SIP models, which are equivalent, can share an EM profile.


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

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/7_0_1/cucm-rel_notes-701.html

Hope this helps!

Rob

Correct Answer by Jaime Valencia about 7 years 4 days ago

ALL CUCM versions have the device default configuration which already enables what you want, it's all covered in any EM config guide

If you do not configure the default config for 7941 and all your UDPs are 7961 it won't work, once you create the default config for 7941 you can log (obviusly some stuff changes like # of lines, speed dials, etc)

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (3 ratings)
Loading.
Correct Answer
Jaime Valencia Thu, 11/26/2009 - 06:19

ALL CUCM versions have the device default configuration which already enables what you want, it's all covered in any EM config guide

If you do not configure the default config for 7941 and all your UDPs are 7961 it won't work, once you create the default config for 7941 you can log (obviusly some stuff changes like # of lines, speed dials, etc)

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

rob.huffman Thu, 11/26/2009 - 06:41

Hey Java,

Hope all is well buddy! Sorry, I missed your post (while I was poderously hammering out

my answer ;-) +5 points my friend!

Cheers!

Huff

PS: I'm working on getting your Badges back!

Correct Answer
rob.huffman Thu, 11/26/2009 - 06:23

Hi Thomas,

Here is a clip that describes the CCM 4.x behaviour;


On authentication, if the login profile matches the login device (that is, the user has a user device profile that is configured for a Cisco IP Phone Model 7960 and logs into a Cisco IP Phone Model 7960), Cisco CallManager Extension Mobility behaves:


The phone automatically reconfigures with the individual user device profile information.


If the user has one user device profile, then the system uses this profile. If the user has more than one user device profile, the user can choose the user device profile that will be used from a list.


The user can access all the services that the user configured on the device profile.


If that same user logs into a Cisco IP Phone model where the user does not have a configured user device profile, the login profile will not match the login device on authentication. In this scenario, the system loads the device profile default for that phone model onto the phone, and Cisco CallManager Extension Mobility works as described here:


The system copies all device-independent configuration (that is, user hold audio hold audio source, user locale, userid, speeddials, and directory number configuration except for the setting "line setting for this device") from the user device profile to the login device.


The system uses the device profile default for that phone model for phone template and softkey template configuration and, if the phone can support addon modules, for the addon module.


If the phone model supports Cisco IP Phone Services and they are configured, the system copies the services from the user device profile.


If the user device profile does not have Cisco IP Phone Services configured, the system uses the Cisco IP Phone Services that are configured in the device profile default for the login device that is accessed during login. If parameters exist for the subscriber service, the system copies the parameters from the device profile default and the parameters may not reflect the correct information.


For example, the following scenarios occur when a user who has a user device profile that is configured for Cisco IP Phone Model 7960 logs in to a Cisco IP Phone Model 7905, and the device default profile is loaded on the phone.


The user can access the user's hold audio source, user locale, userid, speeddials and directory number configuration. The user cannot access his phone line setting; the system configured the phone line setting from the device profile default that is configured for the Cisco IP Phone Model 7905.


The user can access the phone template and the softkey template of the Cisco IP Phone Model 7905.


The user cannot access an addon module because Cisco IP Phone Model 7905 does not support it.


The user can access Cisco IP Phone Services if they are configured for the Cisco IP Phone 7905, but, the parameters from the subscriber services will reflect the device profile default, not the parameters that the user chose on the User Options window.



http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/4_2_1/ccmfeat/fsem.html#wp1146344


Here is one of the main CUCM 7.x EM changes;

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 includes the following support feature for the Cisco Unified IP Phones:


Feature Safe on Phone Button Template-Phones can use any phone button template that has the same number of line buttons that the phone model supports.


Release 7.0(1) of Cisco Unified Communications Manager enhances the existing Extension Mobility (EM) equivalency mechanism. The equivalency enhancement works across phone types as follows:


7940 SCCP, 7941 SCCP, 7942 SCCP, and 7945 SCCP models, which are equivalent, can share an EM profile.


7940 SIP, 7941 SIP, 7942 SIP, and 7945 SIP models, which are equivalent, can share an EM profile.


7960 SCCP and 7961 SCCP models, which are equivalent, can share an EM profile.


7962 SCCP and 7965 SCCP models, which are equivalent, can share an EM profile.


7960 SIP, 7961 SIP, 7962 SIP, and 7965 SIP models, which are equivalent, can share an EM profile.


7970 SCCP and 7971 SCCP models, which are equivalent, can share an EM profile.


7970 SIP, 7971 SIP, and 7975 SIP models, which are equivalent, can share an EM profile.


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

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/7_0_1/cucm-rel_notes-701.html

Hope this helps!

Rob

thomuff Fri, 11/27/2009 - 06:37

Thanks for the answer.   I found it about an hour after posting. I appreciate it. The reason I posted is because the consultant that initially installed the phones told the customer that everything needed to match. Dont know why

Thanks again

Anand Hariharan V Tue, 10/18/2011 - 06:33

This is a 6 year old thread but let me ask this questions for the latest CUCM 8.5 version

Has anything changed in the way EM is handled by CUCM 8.5?

While on CUCM 6.1.3 a single phone profile/template (7961/7962 profile) was used for for all IP Phone models in use(7931, 7961 and 7962’s) and the same profile worked fine for all the IP Phone models.

After upgrade to 8.5 the users are able to login into the 7931 IP Phones but the phone buttons have stopped working.

Is this due to changes in who EM is handled in 8,5?

Actions

This Discussion

Related Content