Cisco 8831 Administration Manual page 14

View Phone Information
Appendix A, "Cisco Unified IP Conference Phone 8831 for Third-Party Call Control Field Reference,"
briefly describes each parameter available on the phone web user interface.
View Phone Information
You can check the current status of the Cisco Unified IP Conference Phone 8831 for Third-Party Call
Control by clicking the Info tab. The Info tab shows information about all phone extensions, including
phone statistics and the registration status.
View Reboot Reasons
The phone stores the most recent five reasons the phone was refreshed or rebooted. When the phone is
reset to factory defaults, this information is deleted.
The list describes the reboot and refresh reasons for Cisco Unified IP Conference Phone 8831 for
Third-Party Call Control.
Reason
Upgrade
Provisioning
SIP Triggered
RC
User Triggered
IP Changed
You can view the reboot history from the phone web user interface, the IP phone screen, and the phone
Status Dump file (http://phoneIP/status.xml or http://phoneIP/admin/status.xml).
View the Reboot History on the Phone Web User Interface
The Info > System Information > Reboot History page displays the device reboot history, the five most
recent reboot dates and times and a reason for the reboot. Each field displays the reason for the reboot
and a time stamp indicating when the reboot took place. For example:
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 reboot history is displayed in reverse chronological order; the reason for the most recent reboot is
displayed in Reboot Reason 1.
Cisco Unified IP Conference Phone 8831 for Third-Party Call Control Administration Guide
1-4
Description
The reboot was a result of an upgrade operation (regardless
whether the upgrade completed or failed).
The reboot was the result of changes made to parameter values by
using the IP phone screen or phone web user interface, or as a
result of synchronization.
The reboot was triggered by a SIP request.
The reboot was triggered as a result of remote customization.
The user manually triggered a cold reboot.
The reboot was triggered after the phone IP address was changed.
Chapter 1 Get Started