Download Procedure

The Avaya-provided upgrade script files and the binaries included in the zip files upgrade the Avaya IP Telephones. You should not need to modify them. It is essential that all the binary files be together on the file server. When downloading a new release onto a file server with an existing release already on it, we recommend that you:

• Stop the file server.
• Back up all the current file server directories as applicable.
• Copy your 46xxsettings.txt file to a backup location.
• Remove all the files in the download directory. This ensures that you do not have an inappropriate binary or configuration file on the server. The only system values that can be used in the Conditional statement are: BOOTNAME, GROUP, and SIG.
• Download the self-extracting executable file, or the corresponding zip file.
• Extract all the files.
• Copy your 46xxsettings.txt file back into the download directory.
• Check the Readme files for release-specific information.
• Modify the 46xxsettings.txt file as desired.
• Restart the HTTP/HTTPS server.
• Reset your Avaya IP Telephones.

You can download a default upgrade script file, sometimes called merely the “script file,” from
http://www.avaya.com/support. This file allows the telephone to use default settings for customer-definable options. Of course, these settings can also be changed with DHCP or in some cases, from the telephone’s dialpad itself. However, you might want to open the default file and administer the options to add useful functionality to your Avaya IP Telephones. This file must reside in the same directory as the upgrade script file, and must be called 46xxsettings.scr or 46xxsettings.txt. The Avaya IP Telephones can operate without this file.

NOTE: Most Windows systems interpret the file extension *.scr as a screen saver. The 4600 IP Telephones originally used *.scr to indicate a script file. We highly recommend that the settings file have the extension *.txt.

The settings file can include any of the five types of statements, one per line:

• Comments, which are statements with a “#” character in the first column.
• Tags, which are comments that have exactly one space character after the initial #, followed by a text string with no spaces.
• Goto commands, of the form GOTO tag. Goto commands cause the telephone to continue interpreting the settings file at the next line after a # tag statement. If no such statement exists, the rest of the settings file is ignored.
• Conditionals, of the form IF $name SEQ string GOTO tag. Conditionals cause the Goto command to be processed if the value of name is a case-insensitive equivalent to string. If no such name exists, the entire conditional is ignored.
• SET commands, of the form SET parameter_name value. Invalid values cause the specified value to be ignored for the associated parameter_name so the default or previously administered value is retained. All values must be text strings, even if the value itself is numeric, a dotted decimal IP Address, etc.

NOTE: Enclose all data in quotation marks for proper interpretation.

The Avaya-provided upgrade script file includes lines that tell the telephone to GET 46xxsettings.scr and 46xxsettings.txt. These lines cause the telephone to use HTTP/HTTPS to attempt to download the file specified in the GET command. If the file is obtained, its contents are interpreted as an additional script file. That is how your settings are changed from the default settings. If the file cannot be obtained, the telephone continues processing the upgrade script file. The upgrade script file is processed so that if there is no 46xxsettings.scr file, the telephone looks for a 46xxsettings.txt file. If the settings file is successfully obtained but does not include any setting changes the telephone stops using HTTP. This happens when you initially download the script file template from the Avaya support Web site, before you make any changes. When the settings file contains no setting changes, the telephone does not go back to the upgrade script file.

You can change the settings file name, if desired, as long as you also edit the corresponding GET command in the upgrade script file. However, we encourage you not to alter the Avaya-provided upgrade script file. If Avaya changes the upgrade script file in the future, any changes you have made will be lost. We strongly encourage you to use the 46xxsettings file to customize your settings instead.

For more details on customizing your settings file, see Contents of the Settings File.