Zultys ZIP4x4, User Manual

Page: 52 / 194

42
ZIP4x4 User’s Manual
5.3.4.5 Step 5
Action. ZIP4x4 initiates TFTP read request for ZIP4x4_common.cfg
Description. ZIP4x4 requests its common configuration file using the TFTP Server address
provided by DHCP option #66.
5.3.4.6 Step 6
Action. ZIP4x4 receives TFTP data (ZIP4x4_common.cfg) from the TFTP Server
Description. The ZIP4x4 receives the common configuration file and reads it. It is possible that the
specific configuration file for a phone is located in a directory that is not the TFTP root directory.
If this is the case, the subdirectory is indicated in this common configuration file.
5.3.4.7 Step 7
Action. ZIP4x4 initiates TFTP read request for MAC_address.cfg
Description. The ZIP4x4 requests its specific configuration file. The specific configuration file is
uniquely named with the specific MAC address of the phone (for example, 0008A10FF312.cfg).
5.3.4.8 Step 8
Action. ZIP4x4 receives TFTP data (MAC_address.cfg) from the TFTP Server
Description. The ZIP4x4 reads its specific configuration file and determines whether its software
version matches that specified. If not, it retrieves the new software.
5.3.4.9 Step 9
Action. ZIP4x4 initiates TFTP read request for ZIP4x4_version bin.
Description. The ZIP4x4 requests the specific software version using the TFTP Server address
provided by DHCP option #66 (for example, ZIP4x4_0_1_34.bin).
5.3.4.10 Step 10
Action. The ZIP4x4 receives TFTP data (ZIP4x4_version.bin) from the TFTP Server
Description. After downloading the software version the ZIP4x4 reboots and repeats all of the
steps (except for retrieving software). At this point, the ZIP4x4 performs a checksum verification
and compares the new software version file name with the version information stored internally
to the .bin file. If the checksum fails or if the file name does not match that of the version
information stored internally to the .bin file, the phone indicates an error and loads the previous
software version.
5.3.5 Summary
For a user, the process of updating the software is fully automatic. The administrator of the
network can initiate this process at any time. When the phone is idle, it will start the process of
updating the software. Usually, the administrator would cause this to happen when no one is
likely to want to use the phone.