McDewey

Behavior with Phone Migration Service Behavior without Phone Migration Service Onboarding Method at Device Defaults Level Autoregistration Enabled at Enterprise Level Phone or Device preconfigured by Administrator Phone replacement screen prompts to select one of the following: “Provision a new phone” or “Replace an existing phone”. Welcome screen of the phone prompts the following: "Enter activation code". Device Type set to Activation Code Yes No Phone replacement screen prompts the following: “Replace an existing phone”. Device retries to register to the network and gives up. Device Type set to Auto Registration No No Phone replacement screen prompts to select one of the following: “Provision a new phone” or “Replace an existing phone”. Welcome screen of the phone prompts the following: "Enter activation code". Device Type set to Activation Code No No Device registers with the preconfigured settings. Device retries to register to the network and keeps retrying based on the back-off timer set. N/A N/A Yes Phones Using Extension Mobility In scenarios where the old phone supports Extension Mobility login, after migration the new device will also support the Extension Mobility capability. If the old phone was logged-in before migration, then the logged-in Extension Mobility user is automatically logged-out during the phone migration. The user must perform fresh Extension Mobility login on the new phone. Native phone migration does not support end-users Extension Mobility Device profile migration. Note CTI Controlled Devices If an old device is CTI Controlled before phone migration, then the new device is also CTI controlled. This is because the device configuration settings are carried over after phone migration. Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 714 Device Management Phones Using Extension Mobility