Reboot History - Cisco 8831 Administration Manual

Info

Reboot History

The conference phone stores the reasons for the last five reboots or refreshes. When the phone is reset
to factory defaults, this information is deleted.
The reboot history is displayed in reverse chronological order, with the reasons for the latest reboot
displayed in the Reboot Reason 1 field.
Each Reboot Reason field displays the reason for the reboot and a time stamp indicating when the reboot
took place as in the following examples:
Reboot Reason 1: [08/13/14 06:12:38] User Triggered
Reboot Reason 2: [08/10/14 10:30:10] Provisioning
Reboot Reason 3: [08/10/14 10:28:20] Upgrade
The following is a list of the supported reboot/refresh reasons:
Reason
Upgrade
Provisioning
SIP Triggered
RC
User Triggered
IP Changed
You can view the reboot history from the phone Web GUI, and the phone Status Dump file
(http://phoneIP/status.xml or
http://phoneIP/admin/status.xml).
Viewing the Reboot History in the Status Dump File
The reboot history is stored in the Status Dump file
(http://<phone_IP_address>/admin/status.xml). In this file, tags Reboot_Reason_1 to
Reboot_Reason_3 store the reboot history, as shown in this example:
<Reboot_History>
<Reboot_Reason_1>[08/10/14 14:03:43]Provisioning</Reboot_Reason_1>
<Reboot_Reason_2>[08/10/14 13:58:15]Provisioning</Reboot_Reason_2>
<Reboot_Reason_3>[08/10/14 12:08:58]Provisioning</Reboot_Reason_3>
<Reboot_Reason_4>
<Reboot_Reason_5>
<Reboot_History/>
The Web GUI and the LCD screen get the reboot history from these tags.
Cisco Unified IP Conference Phone 8831 for Third-Party Call Control Administration Guide
A-2
Appendix A Cisco Unified IP Conference Phone 8831 for Third-Party Call Control Field Reference
Description
An upgrade operation caused a reboot (regardless whether the
upgrade completed or failed).
Changes made to parameter values by using the phone LCD or
Web GUI, or a resync caused a reboot.
A SIP request caused a reboot.
A remote customization caused a reboot.
The user manually triggered a cold reboot.
The phone IP address was changed triggering a warm reboot.