/mcpMigration Scenarios Phones Using Shared Lines Consider a scenario where an old phone has the primary DN shared line with multiple devices. These devices may be owned by the same user or among multiple users. When you try to migrate the old phone with a new Cisco IP Phone using Self-Provisioning IVR or Phone Migration Service methods using a shared line, migration is possible only for users who own the device with the DN as Line 1. Here, the shared lines feature settings are carried over after phone migration. If the old phone does not support the Shared Line feature, the old phones lines are removed after phone migration. The new phone retains the old phones lines after phone migration. Phone Migration Service Running on Proxy TFTP Native phone migration using Phone Migration Service support Cisco proxy TFTP server deployment models. Phone Migration Service running on the proxy TFTP searches for the primary extension on all the remote clusters and redirect the phone to its home or local Phone Migration Service for completing phone migration. In a proxy setup environment, Unified Communications Manager server looks for devices with same DN in a remote cluster. If there is more than one device in the registered or unregistered state with the same DN in any one of the off-cluster, those devices from that particular off-cluster is not considered for phone migration. This is a known limitation for Release 11.5(1)SU8. In Proxy TFTP, after migration, the phone restarts with configuration settings migrated from your old phone. Note that the phone takes 2 reset cycles to restart after successful migration. Note Phone Migration Service—User Assigned with Multiple Devices If there is more than one device for the user with the same primary extension for migration, user will be prompted to choose the device to be migrated. The following table displays the various migration scenarios possible: Table 68: Device Listing and Migration Scenarios Phone Display During Migration Device Status Before Phone Migration Phone Configuration settings of Device 2 will be migrated. Device 1—Registered Device 2—Unregistered Scenario 1 Phone Configuration settings of Device 3 will be migrated. Device 1—Registered Device 2—Registered Device 3—Unregistered Scenario 2 Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 712 Device Management Migration Scenarios