No Local Tftp/Http Servers; Configuration File Download - Avaya E129 User Manual

Firmware upgrades take around 60 seconds in a controlled LAN or 5-10 minutes over the Internet. We
recommend completing firmware upgrades in a controlled LAN environment whenever possible.

NO LOCAL TFTP/HTTP SERVERS

For users that would like to use remote upgrading without a local TFTP/HTTP server, AVAYA offers a
NAT-friendly HTTP server. This enables users to download the latest software upgrades for their phone via
this server. Please refer to the webpage:
Alternatively, users can download a free TFTP or HTTP server and conduct a local firmware upgrade. A
free windows version TFTP server is available for download from :
.
Instructions for local firmware upgrade via TFTP:
1. Unzip the firmware files and put all of them in the root directory of the TFTP server;
2. Connect the PC running the TFTP server and the phone to the same LAN segment;
3. Launch the TFTP server and go to the File menu->Configure->Security to change the TFTP server's
default setting from "Receive Only" to "Transmit Only" for the firmware upgrade;
4. Start the TFTP server and configure the TFTP server in the phone's web configuration interface;
5. Configure the Firmware Server Path to the IP address of the PC;
6. Update the changes and reboot the phone.
End users can also choose to download a free HTTP server from http://httpd.apache.org/ or use
Microsoft IIS web server.
Note:
When the phone boots up, it will send a TFTP or HTTP request to download the configuration file
"cfgxxxxxxxxxxxx" where "xxxxxxxxxxxx" is the MAC address of the phone. If it is a normal TFTP or HTTP
upgrade, the following messages "TFTP Error from [IP ADRESS] requesting cfg000b82023dd4 : File does
not exist. Configuration File Download" can be ignored in the TFTP/HTTP server log.

CONFIGURATION FILE DOWNLOAD

AVAYA SIP Devices can be configured via the Web Interface as well as via a Configuration File (binary or
XML) through TFTP or HTTP/HTTPS. The "Config Server Path" is the TFTP or HTTP/HTTPS server path
for the configuration file. It needs to be set to a valid URL, either in FQDN or IP address format. The
"Config Server Path" can be the same or different from the "Firmware Server Path".
FIRMWARE VERSION 1.0.5.2 E129 SIP DESKPHONE USER MANUAL Page 57 of
60