User guide

48
USING A DEVICE MANAGEMENT SERVER
Using Device management facilitates the upgrading and conguration of multiple confer-
ence phones. To use this feature, the Device management needs to be enabled (default)
and congured and the appropriate les must be located on a server reachable from all
phones, here called a device management server.
The conguration and rmware download are controlled with a congurable frequency.
The default value is once every 30 minutes. (Note: The interval can only be edited directly
in the conguration le.)
Conguration priorities
Because the same conguration parameters can be entered in multiple locations, there is
a need for priorities. The local conguration les have the highest priority followed by the
global conguration le. Conguration entered on the unit itself, via the web interface or
directly on the phone, is overridden the next time the conguration les are downloaded.

Note one exception. Phone language entered on the unit will take precedence.
Files on the device management server
Global conguration le
The global conguration le contains the basic conguration – all settings that are
common for all conference phones on your location. The easiest way to create this le
is simply to congure one phone and export the conguration le or use the built in
conguration le creator.
The default name for this le is kt300ip.xml, but it is possible to create a custom name by
using the pagename element in the conguration le. It is also possible to refer to a cgi,
php, asp, js or jsp le, instead of the xml le, if this is declared using the type element in
the conguration le.
Konftel 300IP searches for conguration les in the following order:
PROVISIONING – UPGRADE AND CONFIGURATION
"
%"%
4
5 E
E %
:
=