Using A Device Management Server - Avaya B179 SIP Installation And Administration Manual

Avaya B179 SIP Conference Phone Installation and Administration Guide

USING 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. (Note: 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.
 Note one exception. Phone language entered on the unit 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 avayab179.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.
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.
56