Mitel UC360, Руководство администратора

Страница: 115 / 141

MASS DEPLOYMENT
99
Mass Deployment of UC360 Collaboration Point
In order to deploy a large number of UC360 units in an office, there are ways to configure them
without physical access to each unit. The UC360 uses configuration files (programmed offline)
for setting up its configuration at boot-up time. See “Mass Deployment Configuration File
Reference” on page 115 for an example of the types information to included in the UC360 XML
Configuration File.
Requirements
See the following requirements below for mass deployment of UC360 units.
MiVoice Business or 3rd Party SIP Server
This server provides the SIP Registrar. If MiVoice Business is not be used, the UC360 needs
a 3rd party SIP Registrar.
MiVoice Business or 3rd Party DHCP Server
This server is used to provide the IP address (Static IP address can also be assigned) of the
units. DHCP options 125/43 and option 66 can be used to specify separate URI’s for firmware
upgrade and mass deployment XML configuration files. This enables units to upgrade firmware
and apply configuration from a factory default state.
HTTP Configuration Server
An HTTP server is used to host the configuration files. When the UC360 is configured with an
HTTP server, the unit will check for any changes to its XML configuration file on boot up.
The configuration files should be placed in an HTTP server directory and that URI can be
statically programmed as the HTTP Configuration Server Address under:
Settings -> Advanced -> System Settings -> Backup Import/Export -> HTTP Import ->
Configuration Server Address
Alternatively, if that static setting is left blank (as it is by default) the URI can be sourced from
DHCP options 125, 43 or 66.
Note: The HTTP Configuration Server can be the same server as the HTTP S/W Upgrade
Server. A single server or separate servers are possible as the URI’s are independent.
An HTTPS URI may be specified for the configuration server URI to employ secure SSL HTTPS
XML configuration file transfer.
Note by default that the SSL certificate of the server must be signed by a trusted root CA
(Certificate Authority) included in the standard list of trusted root CA’s in Android Gingerbread