Updated my Google doc table of IP Phone firmware:
Updated my Google doc table of IP Phone firmware:
This article provides an overview of the Avaya IP Phone registration procedure (for UNIStim IP Phones)
When the phone is powered up, the following happens:
|If you experience any problems with any part of the process, use the IP Phone Factory Default reset procedure to clear all local configuration settings.|
|Leaving LLDP/ADAC enabled when it is not supported by the Layer 2 switching equipment installed at the site can extend boot times for IP Phone devices. While LLDP/ADAC is enabled in a factory default configuration, it is recommended that this be disabled unless it is specifically supported by the networking environment.|
The only information that is critical to an IP phone for the boot process is:
When troubleshooting, eliminate variables by resetting the unit back to factory default and then configure only the minimum number of settings needed to establish connectivity (start with manually configuring the phone, then migrate components of the configuration back to auto to determine where the process fails.)
The 2033 Conference phone firmware versions are approximations. I’m recreating this table from documentation, since Avaya doesn’t seem to care to keep such a thing current. I do have some old UNIStim 3.0 documentation. I’m debating whether or not to include the now-manufacture-discontinued IP phones (i.e., i2001, i2002, i2004). I’m very tempted to do so, since I still see a lot of 4.5 and earlier systems (which still support the older IP Phones.)
There are several reasons why you might want to enable manual provisioning of your Avaya IP Phones:
The provisioning phase of the boot process can use DHCP or HTTP. To use HTTP, you must configure DHCP Option 66 in the IP Phone VLAN to point to the HTTP server name and prefix the server name with “http://”. For example DHCP Option 66 “http://httpserver/”. Whether you select TFTP or HTTP, the provisioning phase process checks the system.prv file and if it exists, may load one of the other provisioning files. If multiple provisioning files are loaded, the configuration parameters take effect in the following priority:
The provisioning files provide the Info Block, which contains all the information you might normally stick in DHCP (or manually configure on the phone if you’re especially sadistic towards your telecom analysts). The Info Block can also contain information that is not normally provided in the DHCP string (e.g., Node and TN.) After the provisioning block is loaded, the IP phone will load the configuration file to determine how it should obtain firmware and font file updates. At some future point, I might come back and write another article to cover provisioning via HTTP or TFTP, but for now, we’re going to focus on the configuration file and manually upgrading the firmware on an IP phone.
The Configuration file can contain a lot of information:
We’re going to focus only on the [FW] values in this article.
|[FW]||Section header for SET FIRMWARE download information.|
|DOWNLOAD_MODE||AUTO||Recommended value. Download firmware only if the VERSION on the provisioning server is newer than the version on the phone.|
|FORCED||VERSION of the phone is ingored. Firmware is always downloaded.|
|VERSION||e.g., 0625C8J||The VERSION string is compared to what is on the phone. VERSION should match the firmware FILENAME exactly.|
|FILENAME||e.g., 0625C8J.bin||Image filename. Must match the filename of the actual IP phone FW file to be downloaded|
|SERVER_IP||x.x.x.x||IP address of the TFTP server in decimal notation.|
|SERVER_PORT||0 to 65535||The port used by the TFTP server at SERVER_IP. Optional|
|SECURITY_MODE||0||For future use|
Example 1140E.cfg file:
[FW] DOWNLOAD_MODE AUTO VERSION 0625C8J FILENAME 0625C8J.bin PROTOCOL TFTP SERVER_IP 192.168.0.101 SECURITY_MODE 0
After placing both the configuration file (e.g., 1140E) and the FILENAME (firmware image) in the root of the TFTP server at SERVER_IP, the next step is to choose the method of configuring the IP Phone to know about the external provisioning server (if you haven’t already done this). The options available are:
|While it is possible to configure the DHCP Option 66 to point to an HTTP server (to retrieve the *.prv or *.cfg files), other files must be available via the protocol specified within the *.cfg file. For the purposes of this article, that means a TFTP server is required whether you provide the <TYPE>.cfg via HTTP or TFTP.|
Select a method and implement it. To keep this article short and focused, we’re going to assume you know how to do this.
Plug in your phone and power it up. Assuming that (your DHCP configuration or manually configured provisioning server is correct and) it is able to reach the provisioning server, it will download the <TYPE>.cfg file from the TFTP/HTTP server, then using the instructions contained within, determine if a firmware download is required and perform that download if necessary.
If you use DOWNLOAD_MODE FORCED, the IP phone will force a download of the firmware each time the phone boots. This will increase the boot time for all IP phones configured to use that <TYPE>.cfg file.
I hope you found this article helpful. If you did, please share it.
Note regarding i2007.cfg file
Early versions of the IP Phone 2007 FW will fail to download newer versions of FW if the [FW] line is present before the FW download information in the .cfg file.
If the FW version currently on the IP Phone 2007 is prior to any version of 0621C4x, then delete the [FW] line. Once the phone has FW version 0621C4x or greater, the [FW] line must be present. Example: Phone has 0621C3A – comment out or delete the [FW] line in the i2007.cfg file Phone has 0621C4J – keep the [FW] line in the i2007.cfg file