Auto Provisioning" Procedure; Introduction; Preparatory Steps - Siemens optiPoint 150 S Administration Manual

"Auto Provisioning" Procedure

"Auto Provisioning" Procedure

Introduction

Instead of using DLS (Deployment Service; not compatible with
optiPoint 150 S) as a large-scale administration tool, optiPoint 150 S fea-
tures an "Auto Provisioning" procedure for the automated provisioning of
firmware and configuration data.
The telephone uses the "Auto Provisioning" procedure to run automatic
comparisons at specific intervals between the device configuration and
firmware and corresponding versions on a TFTP server
perform automatic data updates where necessary.
The "Auto Provisioning" procedure means you can update multiple devices
at once without a great deal of effort. It is also possible to create custom-
ized configuration patterns on individual devices. These specific configura-
tion settings

Preparatory Steps

The following prerequisites must be satisfied before you can run the
"Auto Provisioning" procedure:
•
•
•
•
•
•
24
page 27 are then transferred to the corresponding devices.
A TFTP server is available
DHCP option 66 (TFTP server name) was activated on the DHCP server
to transfer the TFTP server address to optiPoint 150 S.
A common configuration file (common.cfg) exists with parameter infor-
mation page 27 for all telephones; this file was saved in the root di-
rectory on the TFTP server.
A separate configuration file is stored in the TFTP server root directory
for each device that should feature specific parameters in its configura-
tion page 27. This file's name contains the last six characters of the
telephone's MAC address
the MAC address 00082B0AB3D2).
This file is referred to as the MAC-specific configuration file in the fol-
lowing sections.
Automatic firmware upgrades are only possible if the Auto-Config-
function page 41 is activated in the Web-Based Management tool.
For easy-to-understand documentation on firmware updates, the
FWLEVEL parameter
configuration file on the basis of the firmware version. The firmware is
not updated if the FWLEVEL is identical to the previous common con-
figuration file.
page 30.
page 49 (for example, 0AB3D2.cfg for
page 27 should be adapted in the relevant
page 30 and to