Where to Find More Information

https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/cucm/whitePaper/CUCM_Headsets_for_ContactCenter_WP.pdf

You can see the headset firmware update source on the phone web page. The information displays on the Device Information page.

This feature has no user impact.

Where to Find More Information

• Cisco IP Phone 7800 Series Administration Guide

If you need to replace a user's phone, you can easily migrate the old phone configuration to the new phone. To support this feature, you need new phones that run Firmware Release 12.8(1).

The change may be required for a number of reasons, for example:

• You have updated your Cisco Unified Communications Manager (Unified CM) to a software version that doesn't support the phone model. In this case, the user needs a new, supported phone.

• The phone requires repair or replacement with the same phone model.

To migrate the phone, the old phone must be powered off. You power on the new phone, and receive a prompt to either replace an existing phone or provision a new phone. If you select the option to replace an existing phone, the phone prompts you for the extension number of the old phone (and PIN, if required). The phone contacts the Unified CM and the old phone configuration is copied into the configuration record for the new phone.

This feature supports migration of SIP and SCCP phones.

This feature requires Unified CM Release 11.5SU8 or later, or Release 12.5SU3 or later. The feature requires configuration of new fields in the Enterprise Parameters Configuration administration page. The feature also requires that the Unified CM administrator disable phone autoconfiguration.

If the old phone has a key expansion model configured and the new phone doesn't support an expansion module, the Unified CM doesn't copy the expansion module information.

Limitations for Lines and Line Keys

If the old phone has more lines or more line buttons than the new phone supports, only the supported number of lines or line buttons are migrated.

For example:

• Scenario: The old phone had 4 line buttons and the new phone has 2 line buttons

• Migration result: The new phone has the line buttons set up like the first 2 line buttons on the old phone.

Where to Find More Information

• Cisco IP Phone 7800 Series Administration Guide

• Feature Configuration Guide for Cisco Unified Communications Manager, Release 12.5(1)SU3 or later

Your Extension Mobility users can easily start their sign in to Extension Mobility when they plug their Cisco Headset 500 Series or Cisco Headset 730 into someone else's phone. To support this, you need to enable the Headset-based Extension Mobility field in Cisco Unified Communications Manager for your phones.

• The Cisco Headset 500 Series needs to connect to the phone with the USB or Y-cable, or be paired and connected to the phone through the Cisco Headset 560 Series Standard Base or Cisco Headset 560 Series Multibase.

• The Cisco Headset 730 needs to connect to the phone with the USB cable. The Cisco Headset 730 USB dongle is not supported.

When the user connects the headset into a phone, the phone checks with Cisco Unified Communications Manager (Unified CM) to discover if the headset serial number is mapped to a user.

• If the mapping exists, the phone displays the Extension Mobility screen and displays the user ID associated with the headset. The user enters their PIN to sign in.

• If the mapping doesn't exist, the user sees a headset association page and enters their user ID and PIN. The phone relays the headset serial number to the Unified CM, which maps the headset to the user. Then the Extension Mobility sign-in screen displays. The user changes the user ID to their user ID and and enters their PIN.

  The next time the user plugs their headset into a phone, the Unified CM finds the user ID, based on the headset serial number.

Note	With Unified CM Software Release 12.5(1)SU3, you can disable the requirement for the PIN input when the headset is register to a user.

The user automatically signs out of Extension Mobility when they unplug the headset or after a predetermined inactivity time.

The user can also be signed out automatically if the Cisco Headset 560 Series is taken too far from the base. In this case, if the headset reconnects with the base before the inactivity timer expires, the user doesn't need to sign in again.

Users can associate their headset with their user ID from the Accessories menu on the phone

Administrators can associate the headset with a user in Unified CM from the User Management page.

This feature requires:

• Unified CM:

  • Software Release 11.5(1)SU8 or later

  • Software Release 12.5(1)SU3 or later

  The feature requires configuration of new fields in the Service Parameter Configuration administration page. the feature also needs the Cisco Headset Service to be active on the Unified CM.

Note	If the headset is upgrading or the user is on a call, the association can't be made. The user must wait until the upgrade is finished or the call is finished before they perform this procedure.

Mobile and Remote Access doesn't support this feature..

Where to Find More Information

• Cisco IP Phone 7800 Series User Guide

• Feature Configuration Guide for Cisco Unified Communications Manager