hit counter script

Upgrading From Release 2.2 Or Later Releases To Release 4.0; Upgrading From Release 2.1 Or Earlier Releases To Release 4.0; Dual Booting From Sccp Or Mgcp To Release - Cisco SIP IP Phone Administrator's Manual

Table of Contents

Advertisement

Chapter 3
Managing Cisco SIP IP Phones
See the upgrade scenarios in
Table 3-11 Upgrade Scenarios
Image Name
P0S30100, P0S30200, P0S30201, and
P0S3Zxxx
P003xxxx or P003xxxxxxxx (these images are
loaded on the Cisco SIP IP phone when it is
shipped)
P0M3xx-y-zz
P0S30202, P0S30203 and P0S3-03-y-xx

Upgrading from Release 2.2 or Later Releases to Release 4.0

Step 1
Copy the new Release 4.0 binary image P0S3-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, P0S3-xx-y-zz).
Reset each phone.
Step 3
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.1 or Earlier Releases to Release 4.0

Copy the P0S30202.bin binary image from Cisco.com to the root directory of the TFTP server.
Step 1
If you are dual booting from a Cisco IP phone running the Skinny Client Control Protocol (SCCP) or
Step 2
MGCP protocol, open the OS79XX.TXT file with a text editor and change the file to include P0S30202.
Ensure that the latest version of the Cisco SIP IP phone firmware has been copied from Cisco.com
to the root directory of your TFTP server.
Table 3-11
Upgrading the Cisco SIP IP Phone Firmware
to determine how to upgrade.
Use Section
Upgrading from Release 2.1 or Earlier Releases to
Release 4.0, page 3-45

Dual Booting from SCCP or MGCP to Release 4.0,

page 3-46
Dual Booting from SCCP or MGCP to Release 4.0,
page 3-46
Upgrading from Release 2.2 or Later Releases to
Release 4.0, page 3-45
Cisco SIP IP Phone Administrator Guide
3-45

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents