Preventing Cisco Webex DX80 from Reverting to Previous Version

How to Prevent Cisco Webex DX80 from Reverting to Previous Version

Question

An administrator recently upgraded a Cisco Webex DX80 through its web interface but discovered the next morning that the unit has received to its previous version.

What must the administrator do to prevent this from happening again?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

C.

The issue described in the question suggests that the Cisco Webex DX80 was upgraded successfully, but the upgrade was not persistent, and the device reverted to its previous version. This behavior indicates that the device may have received a configuration or policy update that caused it to roll back to the previous version. To prevent this from happening again, the administrator should take the following steps:

Option A: Assign a phone security profile with secure SIP This option is not relevant to the issue described in the question. Secure SIP is a protocol used to establish and maintain sessions between SIP-enabled devices, and it is not directly related to device upgrades or configuration persistence.

Option B: Set the prepare cluster for rollback to pre-8.0 enterprise parameter to true This option is also not relevant to the issue described in the question. The "prepare cluster for rollback" parameter is used to enable or disable the rollback feature for all devices in a Cisco Unified Communications Manager (CUCM) cluster. This feature allows administrators to revert all devices in the cluster to a previous version in case of a failed upgrade or deployment. However, this parameter does not affect the behavior of individual devices, and it is not related to the persistence of device upgrades.

Option C: Confirm the phone load name in the phone configuration This option may help prevent the described issue. The phone load is the software image that is loaded onto a Cisco IP Phone or endpoint, and it contains the operating system and firmware that control the device's behavior. If the phone load is not configured correctly, the device may fail to upgrade or may revert to a previous version. Therefore, the administrator should confirm that the correct phone load is configured for the DX80 and ensure that it is compatible with the target version of the CUCM or Cisco Webex.

Option D: Assign a universal device template to the phone This option may also help prevent the described issue. A universal device template is a configuration template that defines common settings for a group of devices, such as phone models or locations. By assigning a universal device template to the DX80, the administrator can ensure that the device receives a consistent and compatible set of configuration settings that are tailored to its role and location. This can help prevent conflicts or errors that may cause the device to roll back to a previous version.

In summary, the best options to prevent the described issue are C and D. The administrator should confirm the phone load name in the phone configuration and assign a universal device template to the phone to ensure that it receives the correct software and configuration settings.