/mcpPhones with Key Expansion Module If the Key Expansion Module (KEM) attached to your old phone is not compatible with your new phone model, you will lose the KEM 'Expansion Module Information' configuration settings on the new phone after phone migration. The following table explains different scenarios: Table 70: KEM Migration Scenarios Expected Behavior After Migration New Phone (Model 88xx) Old Phone (Model 79xx) Scenarios KEM 1 configuration settings are carried over. KEM 1 KEM 1 • KEM 1 attached to the old phone is compatible with the new phone. • User removes the KEM 1 from the old phone and attaches it with the new phone. KEM 1 configuration settings are carried over to KEM 2. KEM 2 KEM 1 • KEM 1 attached to the old phone is incompatible with the new phone. • User attaches a compatible KEM 2 (brand new or used) to the new phone. KEM 1 configuration settings are carried over to KEM 3. KEM 3 KEM 1 • KEM 1 attached to the old phone is deprecated. • User attaches a new KEM 3 to the new phone. Product Specific Configuration Parameters During phone migration, the product-specific parameters of the older phones are also migrated. The new phone considers only the parameters that the phone understands. The remaining parameters are set to their default value. If the ‘Line Mode’ parameter is already configured during phone migration, the ‘Line Mode’ configuration settings are carried over. Else, this parameter is set as ‘Session Line Mode’ by default. Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 715 Device Management Phones with Key Expansion Module