96x1 Phones SIP Firmware Download
in B5800 Centralized Branch Deployments
Release Date: August 31, 2011
Introduction
When Avaya SIP phones are deployed in the centralized branch deployment model, the primary method for
phone firmware download is centralized as well. In this mode the phones get their settings file and firmware
file from a central HTTP server.
However if this method cannot be used e.g. due to WAN bandwidth concerns, an alternative method may be
used leveraging the Avaya B5800 Branch Gateway located in the phones’ branch.
This document describes the process for 96x1 Series Phone SIP firmware download using the Avaya B5800
Branch Gateway. This document does not cover the procedure required to replace H.323 version of the
firmware to SIP version.
B5800 Support for SIP phone firmware download
This capability is made available in the Avaya B5800 Branch Gateway Release 6.1 3Q Service Pack. However,
please note that when upgrading from phones, a hidden B5800 system configuration parameter (the B5800
NoUser Source Number ‘ENABLE_SIP_FIRMWARE_DOWNLOAD’) needs to be configured.
Pre-upgrade process steps
A DHCP server has to be set up to provide correct HTTP server address to the phones.
The preferred approach is for the DHCP server to be enabled on the B5800 Branch Gateway in each of the
branches. In B5800 Manager:
• Select System - LAN tab - LAN Settings
• Under ‘DHCP Mode’ select ‘Server’
• Click on Advanced button
• Select ‘Apply to Avaya IP Phones only’
Alternatively external DHCP servers can be used if preferred, in which case the DHCP server has to be
configured to provide the IP address of the right B5800 for each branch as the HTTP server address in the
Site-Specific Option of the DHCP response to the phone.
Page 1 of 3
96x1 Phones SIP Firmware Download in B5800 Centralized Branch Deployments
The SIP phone configuration file 46xxsettings.txt has to be edited and then loaded to the B5800. This should
be done as part of installation and does not have to be repeated when upgrading to a new phone SIP
firmware.
• SIP_CONTROLLER_LIST has to have the appropriate Avaya Aura® Session Manager IP address as a primary
SIP server.
• Recommendations for settings file parameters relevant to the branch deployment are provided in the
document ‘Implementing the Avaya B5800 Branch Gateway’ (available on the Avaya support site).
• HTTPSRVR IP address may have to be set to point to the B5800 (if this is not what is already provided to
the phone via DHCP).
The SIP phone firmware load of the required version has to be obtained. It comes as a zip file containing
multiple files (tar, xml, txt).
Loading phone files to the B5800
The SIP phone firmware has to be loaded onto the B5800 SD card. The entire content of the zip file should be
copied to the B5800. In particular, be sure to load onto the B5800 the phone upgrade file 96x1Supgrade.txt
containing the correct name of the new firmware files.
Loading the files to the B5800 can be done using B5800 Manager, either locally in the branch or remotely
where B5800 Manager connects from the NOC to the different branches and loads the files to each B5800 at
a time. The unzipped files have to be on the machine running the B5800 Manager. In the B5800 Manager, go
to File / Advanced / Embedded File Management, and copy the files onto the B5800 SD card \System\Primary
folder.
The phone configuration file (46xxsettings.txt) also has to be loaded on the B5800 SD card. This can also be
done using B5800 Manager Embedded File Management, but this file does not have to be modified and
loaded to B5800 again each time a new firmware for the SIP phone is available.
Phone Upgrade Process
The phones have to be rebooted to start the firmware download from the B5800. This can be done by power
cycling the phones, or remotely from the Avaya Aura® System Manager in the NOC using the procedure
outlined below.
When upgrading from phones running firmware versions prior to 6.0 SP2 it is recommended to upgrade up
to 10 phones in each branch at once. Once these phones finish, another set of up to 10 phones can be
rebooted to start the upgrade. If more than 10 phones try to download their firmware from B5800 at once
there is a risk that download will not be successful on some of them. In such case, the phones that failed to
download successfully should be rebooted to try again.
When upgrading from phones running firmware versions 6.0 SP2 and later, simultaneous upgrade of groups
of up to 50 phones is supported.
Page 2 of 3