Cisco 8800 Series, Manual

Page: 456 / 544

• Open—The phone has booted for the first time and is not configured.
• Aborted—Remote customization is aborted due to other Provisioning like DHCP options.
• Pending—The profile has been downloaded from the EDOS server.
• Custom-Pending—The phone has downloaded a redirect URL from the EDOS server.
• Acquired—In the profile downloaded from the EDOS server, there is a redirect URL for provision
configuration. If the redirect URL download from the provisioning server is successful, this state is
displayed.
• Unavailable—Remote customization has stopped because the EDOS server responded with an empty
provisioning file and the HTTP response was
200 OK
.
Procedure
Step 1 On the Phone Web page, select Admin Login > Info > Status .
Step 2
In the Product Information section, you can view the customization state of the phone in the Customization
field.
If any provisioning is failing, you can view the details in the Provisioning Status section on the same page.
Reboot Reasons
The phone stores the most recent five reasons that the phone was refreshed or rebooted. When the phone is
reset to factory defaults, this information is deleted.
The following table describes the reboot and refresh reasons for the Cisco IP Phone.
Description Reason
The reboot was a result of an upgrade operation
(regardless whether the upgrade completed or failed). Upgrade
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. Provisioning
The reboot was triggered by a SIP request. SIP Triggered
The reboot was triggered as a result of remote
customization. RC
The user manually triggered a cold reboot. User Triggered
The reboot was triggered after the phone IP address
changed. IP Changed
Cisco IP Phone 8800 Series Multiplatform Phone Administration Guide for Release 11.3(1) and Later
436
Troubleshooting
Reboot Reasons