Upgrading From Release 2.2 Or Later Releases To Release 4.0 - Cisco MGCP IP Phone Administrator's Manual

Upgrading the Cisco MGCP IP Phone Firmware
Release 5.0
Cisco has added image authentication to IP phone protocols, which means that tampering with the binary
image before the image is downloaded to the phone is not allowed. Any tampering with the image will
cause the phone to fail the authentication process and reject the image. Once you download the Release
5.0 image, you cannot downgrade to any earlier releases.
Release 5.1
Release 5.1 is the second release of the signed Cisco IP phone image. Release 5.1 is compatible with
Release 5.0 and later releases. Release 5.1 addresses the user interface responsiveness and voice clipping
issues.
Procedure
Unzip the ZIP archive to extract the binary images and any notes or readme text files. Read these text
Step 1
files for any special directions regarding the images.
Copy the new images P0M3-xx-y-zz.sbn (signed binary) and P0M3-xx-y-zz.bin (unsigned
Step 2
binary)—where xx is the release major version, y is the release minor version, and zz is the maintenance
number—from Cisco.com to the root directory of the TFTP server.
Using a text editor, open the configuration file and update the image version specified in the
Step 3
image_version variable. The version name in the image_version variable should match the version name
(without the .sbn extension) of the latest firmware that you downloaded (for example, P0M3-xx-y-zz).
Step 4 Reset each phone.
The phone contacts the TFTP server and requests its configuration files. The phone compares the image
defined in the file to the image that it has stored in Flash memory. If the phone determines that the image
defined in the file differs from the image in Flash memory, it downloads the image defined in the
configuration file (which is stored in the root directory on the TFTP server). Once the new image has
been downloaded, the phone programs that image into Flash memory and then reboots.
Note If you do not define the image_version parameter in the default configuration file, only phones that have
an updated phone-specific configuration file with the new image version and that have been restarted use
the latest firmware image. All other phones use the older version until their configuration files have been
updated with the new image version.

Upgrading from Release 2.2 or Later Releases to Release 4.0

Step 1 Copy the Release 4.0 image P0M3-xx-y-zz.bin, where xx is the release major version, y is the release
minor version, and zz is the maintenance number, from Cisco.com to the root directory of the TFTP
server.
Using a text editor, open the configuration file and update the image version specified in the
Step 2
image_version variable. The version name in the image_version variable should match the version name
(without the .bin extension) of the latest firmware that you downloaded (for example, P0M3-xx-y-zz).
Reset each phone.
Step 3
Cisco MGCP IP Phone Administrator Guide, Release 5.0 and Release 5.1
3-14
Chapter 3 Configuring the Cisco MGCP IP Phone