Reboot History - Cisco SPA301 Administration Manual

Hide thumbs Also See for SPA301:
Table of Contents

Advertisement

Cisco SPA IP Phone Field Reference
Info Tab
Cisco Small Business SPA300 Series, SPA500 Series, and WIP310 IP Phone Administration Guide

Reboot History

The IP 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: Provisioning(06/22/2011 13:29:33)
Reboot Reason 2: Upgrade(06/22/2011 13:01:43)
Reboot Reason 3: Provisioning(06/22/2011 10:40:12)
The following is a list of the supported reboot/refresh reasons:
Reason
Upgrade
Provisioning
SIP Triggered
RC
User Triggered
Software Req
System n
IP Changed
You can view the reboot history from the phone Web GUI, the phone LCD screen,
and the phone SPA Status Dump file (http://phoneIP/status.xml or
http://phoneIP/admin/status.xml).
Viewing the Reboot History on the Phone LCD Screen
A new menu, Reboot History, was added under the Setup menu. On the Reboot
History Page, the 5 reboot entries are displayed in reverse chronological order,
just like the Web GUI.
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 warm reboot.
A remote server triggered a warm reboot.
System events (for example, running out of
resources) triggered a warm reboot.
The phone IP address was changed triggering a
warm reboot.
A
235

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents