Print

Provisioning from a device management server

Using Device management facilitates the upgrading and configuration of multiple conference phones. To use this feature, the Device management needs to be enabled (default) and configured and the appropriate files must be located on a server reachable from all phones, here called a device management server.

The configuration and firmware download are controlled with a configurable frequency. The default value is once every 30 minutes.

noteNote

The interval can only be edited directly in the configuration file.

Configuration priorities

Because the same configuration parameters can be entered in multiple locations, there is a need for priorities. The local configuration files have the highest priority followed by the global configuration file. Configuration entered on the unit itself, via the web interface or directly on the phone, is overridden the next time the configuration files are downloaded.

noteNote

The exception to this is any phone language entered on the unit, which will take precedence.

Files on the device management server

Global configuration file

The global configuration file contains the basic configuration – all settings that are common for all conference phones on your location. The easiest way to create this file is simply to configure one phone and export the configuration file or use the built in configuration file creator.

The default name for this file is avaya.xml, but it is possible to create a custom name by using the pagename element in the configuration file. It is also possible to refer to a cgi, php, asp, js or jsp file, instead of the xml file, if this is declared using the type element in the configuration file.

Avaya B179 searches for configuration files in the following order:

'' Type parameter value Result
1 <nothing> <pagename>.xml
2 cgi <pagename>.cgi?phone_model=avaya_b179>
3 %''% <pagename>.php?phone_model=avaya_b179>
4 asp <pagename>.asp?phone_model=avaya_b179>
5 E <pagename>.js?phone_model=avaya_b179>
6 E % <pagename>.jsp?phone_model=avaya_b179>
: <any name> <pagename>.<any name>?phone_model=avaya_b179>
= auto 1, 2, 3, 4, 5, and 6 will be tried in that order

Local configuration file

The local configuration file contains configuration parameters that are unique for every conference phone. The settings in this file takes precedence over the settings in the global configuration file.

The default name for this file is avaya-<MAC>.xml, where <MAC> is the MAC address of the specific conference phone. The MAC address should be written without colons.

It is possible to create a custom name by using the pagename element in the configuration file. It is also possible to refer to a cgi, php, asp, js or jsp file, instead of the xml file, if this is declared using the type element in the configuration file.

Avaya B179 searches for configuration files in the following order:
'' Type parameter value Result
1 <nothing> <pagename>-<MAC>.xml
2 cgi <pagename>.cgi?phone_model=avaya_b179&eth=<MAC>
3 %''% <pagename>.php?phone_model=avaya_b179&eth=<MAC>
4 asp <pagename>.asp?phone_model=avaya_b179&eth=<MAC>
5 E <pagename>.js?phone_model=avaya_b179&eth=<MAC>
6 E % <pagename>.jsp?phone_model=avaya_b179&eth=<MAC>
: <any name> <pagename>.<any name>?phone_model=avaya_b179&eth=<MAC>
= auto 1, 2, 3, 4, 5, and 6 will be tried in that order

Firmware binary

Contains the firmware binary that will be downloaded and installed by Avaya B179 if the metadata file shows that this is a newer version than the present installed. The binary file can be downloaded from support.avaya.com.

Firmware metadata file

A metadata file in xml format with information of the firmware version in the binary file. The file is used to check if the binary file should be downloaded to the phone or not.

The name of this file shall be avaya_fw_version.xml. The file shall contain the following elements in xml format:

<firmware_version>  
<version>X.X.X</version> Eg. 2.0.7
<filename>xxxx</filename> Eg. AVAYA_B179_v2.0.7.kt
<checksum>XXXX</checksum> MD5 checksum of the firmware binary
</firmware_version>