Cisco SPA942 - - IP Phone Administration Manual page 141

Provisioning Basics
Upgrading, Resyncing, and Rebooting Phones
Cisco SPA and Wireless IP Phone Administration Guide
256-bit symmetric key encryption of profiles is supported. In addition, an
unprovisioned Cisco IP phone can receive an encrypted profile specifically
targeted for that device without requiring an explicit key. a secure first-time
provisioning mechanism using SSL functionality.
User intervention is not required to initiate or complete a profile update or
firmware upgrade. The Cisco IP phone upgrade logic is capable of automating
multi-stage upgrades, if intermediate upgrades are required to reach a future
upgrade state from an older release. A profile resync is only attempted when the
Cisco IP phone is idle, because this may trigger a software reboot.
General purpose parameters are provided to help service providers manage the
provisioning process. Each Cisco IP phone can be configured to periodically
contact a normal provisioning server (NPS). Communication with the NPS does not
require the use of a secure protocol because the updated profile is encrypted by
a shared secret key. The NPS can be a standard TFTP, HTTP or HTTPS server.
The administrator can upgrade, reboot, or resync Cisco IP phones using the web
interface.
Upgrading Firmware on a Phone
Use the upgrade URL to upgrade firmware on the Cisco IP phone. You can
upgrade from either a TFTP or HTTP server.
The Upgrade Enable parameter on the Provisioning web page must be set to Yes:
Cisco IP phone web UI: Provisioning > Firmware Upgrade > Upgrade Enable: yes
Use the following syntax to upgrade firmware on a phone:
http://phone-ip-address/admin/upgrade?protocol://server-
name[:port]]/firmware-path
• Protocol defaults to TFTP.
• Server name is the host requesting the URL.
• Port is the port of the protocol being used (for example, 69 for TFTP or 80
for HTTP).
• Firmware-path defaults to /spa.bin (for example, http://192. 1 68.2.217/
admin/upgrade?tftp://192. 1 68.2.251/spa.bin) for SPA phones and /
wip310.img for the WIP310. The firmware-pathname is typically the file
name of the binary located in a directory on the TFTP or HTTP server.
1-
7
139