Operation Manual

Getting Started
Viewing Phone Information
Cisco Small Business SPA300 Series, SPA500 Series, and WIP310 IP Phone Administration Guide 25
1
The following is a list of the supported reboot/refresh reasons (Cisco SPA525G or
Cisco SPA525G2):
You can view the reboot history from the phone web user interface, the IP phone
screen, and the phone SPA Status Dump file (http://phoneIP/status.xml or http://
phoneIP/admin/status.xml).
System n The reboot was triggered by system events (for
example, running out of resources).
IP Changed The reboot was triggered after the phone IP address
was changed.
Reason Description
Reason Description
Upgrade The reboot was a result of an upgrade operation
(regardless whether the upgrade completed or
failed).
Provisioning The reboot was the result of changes made to
parameter values via the IP phone screen or phone
web user interface, or as a result of synchronization.
SIP Triggered The reboot was triggered by a SIP request.
RC The reboot was triggered as a result of remote
customization.
User Triggered The user manually triggered a warm reboot.
Software Req The warm reboot was triggered by a remote server.
System n The reboot was triggered by system events (for
example, running out of resources).
IP Changed The reboot was triggered after the phone IP address
was changed.
Downloaded from www.Manualslib.com manuals search engine