From CUCM versions 11.5 SU 8, 12.5 SU 3, 14 Cisco introduced a feature called Phone migrations.
The Phone Migration feature is an easy and intuitive Cisco IP Phone migration solution native to Unified Communications Manager. It minimizes the cost and complexity of replacing deprecated or faulty phones.
Phone Migration Supports below three options.
- Using Self-provisioning IVR Service
- Using Phone Migration Service
- Using Cisco Unified CM Administration Interface
Enterprise Parameters for Phone Migration
Migration depends on the following two parameters in the Enterprise Parameters Configuration page:
- When Provisioning a Replacement Phone for an End User—You can choose either Retain Existing Phone(s) (default option) or Delete the Existing Phone for that End User. If the Retain Existing Phone(s) option is selected, then during migration the old phone is marked as migrated and can be filtered in the Find and List Phones page to generate migration report.
| If the administrator decides to choose the Retain Existing Phone(s) option for phone migration, a total of two licenses will be consumed, that is, one license each for the existing phone and the new phone picked up for migration. |
| During phone migration, if the administrator decides to choose the Retain Existing Phone(s) option for phone migration, the intercom DN is not migrated to the new device. If the Delete the Existing Phone for that End User option is selected, the intercom DN information is also migrated. |
- Security Profile for Migrated Phone—This option determines the type of security profile that is applied for a migrated phone (old phone was in secure mode) during phone migration. Choosing the Non-secure profile brings up your device in the non-secure mode.
- Phone Migration User Identification Prompt—This parameter determines whether a user is able to proceed with phone migration using the Self-Service User ID or using the Primary Extension. If the Use Enduser Self-Service User ID option is selected, the end user is prompted to enter the unique Self-Service User ID before proceeding with phone migration. If the Use Enduser Primary Extension option is selected, you can migrate your phone after entering the primary extension number. In this mode, if the same DN exists in different route partitions, phone migration is not possible using IVR or Phone Migration service.
Using Self-provisioning IVR Service
Note:- I am not going discussing about how to configure self provisioning in this blog. i will add another article to cover this topic.
If you are using Self provisioning in your Office, There is no extra configuration required to make use of phone migration feature.
When dialing Self Provisioning Number you get a option 2 to replace the Existing phone. Watch the below video.
Before end users can use self-provisioning for migration, the following should be configured:
- Enable Auto-registration.
- End users must have a primary extension. Ensure that the primary DN is always Line 1 on the phone or device.
I am going to replace my below 7811 phone with a new 7841 and i choose Retain Existing phone in enterprise parameter. So after migration i will see two devices with extension 400.
For Self Provisioning we need to enable Auto registrations and my new device got registered with an extension 4455521.
If you choose Delete the Existing Phone for that End User, you will see Only 7841 with 400 Extension.
Using Phone Migration Service
Before your end users can use Phone Migration Service for migration, the following should be configured:
- Disable Auto-registration.
- End users must have a primary extension. Ensure that the primary DN is always Line 1 on the phone or device.
- Supported Phone Models: 88XX, 78XX, 8832, and 7832.
- Minimum supported phone version is Release 12.8.1 and above.
If you choose Delete the Existing Phone for that End User, you will see Only 7841 with 400 Extension.
To Learn more about this feature refer CUCM Feature Configurations Guide. Here is the Link for 12.5SU(4)
CRAZY NETWORKING 