3-47
Cisco SIP IP Phone Administrator Guide
Chapter 3 Managing Cisco SIP IP Phones
Performing an Image Upgrade and Remote Reboot
To upgrade the firmware image and perform a remote reboot, complete the following steps:
Step 1
Using an ASCII editor, open the SIPDefault.cnf file located in the root directory of your TFTP server
and change the image_version parameter to the name of the latest image.
Step 2
Using an ASCII editor, open the syncinfo.xml file located in the root directory of your TFTP server and
specify values for the image version and sync parameter as follows:
<IMAGE VERSION=”image_version” SYNC=”sync_number”/>
Where:
•
image_version is the image version of the phone. The asterisk (*) can be used as a wildcard
character.
•
sync_number is the synchronization level of the phone. The default synchronization level for the
phone is 1. A valid value is a character string of up to 32 characters.
Step 3
Send a NOTIFY message to the phone. In the NOTIFY message, ensure that the an Event header that is
equal to “check-sync” is included.
The following is a sample NOTIFY message:
NOTIFY sip:lineX_name@ipaddress:5060 SIP/2.0
Via: SIP/2.0/UDP ipaddress:5060;branch=1
Via: SIP/2.0/UDP ipaddress
From: <sip:webadim@ipaddress>
To: <sip:lineX_name@ipaddress>
Event: check-sync
Date: Mon, 10 Jul 2000 16:28:53 -0700
Call-ID: 1349882@ipaddress
CSeq: 1300 NOTIFY
Contact: <sip:webadmin@ipaddress>
Content-Length: 0
After the remote reboot process is initiated on the phone via the NOTIFY message, the following actions
take place:
1.
If the phone is currently in an idle state, the phone waits 20 seconds and then contacts the TFTP
server for the syncinfo.xml file. If the phone is not in an idle state, the phone waits until it is in an
idle state for 20 seconds and then contacts the TFTP server for the syncinfo.xml file.
2.
The phone reads the syncinfo.xml file and performs the following as appropriate:
a.
Determines whether the current image is specified. If so, the phone proceeds to Step
c.
If not,
the phone proceeds to Step
b.
b.
Determines whether there is a wildcard entry (*) in the image version parameter. If so, the phone
proceeds to Step
c.
If not, the phone proceeds to Step
d.
c.
Determines if the synchronization value is different than what is stored on the phone. If so, the
phone proceeds to Step
e.
If not, the phone proceeds to Step
d.
d.
The phone does nothing.
e.
The phone reboots.
The phone the performs a normal reboot process as described in the
“Initialization Process
Overview” section on page 2-1
, sees the new image, and upgrades to the new image with a
synchronization value of what is specified in the syncinfo.xml file.
