Yealink W80, Руководство администратора

Страница: 89 / 260

Phone Provisioning
86
5.
Save the boot file and place it on the provisioning server.
Related Topic
Boot File Attributes
Configuration Files
Yealink supports two configuration template files: Common CFG file and MAC-Oriented CFG file.
These configuration files contain two kinds of parameters:
l
Static: The parameters start with a prefix “static.”, for example, static.auto_provision.custom.protect.
l
Non-static: The parameters do not start with a prefix “static.”, for example, local_time.date_format.
You can deploy and maintain a mass of Yealink phones automatically through configuration files stored in a pro-
visioning server.
Note : For protecting against unauthorized access, you can encrypt configuration files. For more information on encrypting
configuration files, refer to
Encrypting and Decrypting Files
.
Topics
Common CFG File
MAC-Oriented CFG File
MAC-local CFG File
Configuration File Customization
Configuration File Attributes
Common CFG File
Common CFG file, named <y0000000000xx>.cfg, contains parameters that affect the basic operation of the IP
phone, such as language and volume. It will be effective for all phones in the same model. The common CFG file
has a fixed name for each phone model.
The name of the common CFG file for W80DM device is y000000000103.cfg.
MAC-Oriented CFG File
MAC-Oriented CFG file, which is named after the MAC address of the IP phone. For example, if the MAC address of
an IP phone is 00156574B150, the name of MAC-Oriented CFG file is 00156574b150.cfg (lowercase). It contains
parameters unique to a particular phone, such as account registration. It will only be effective for a MAC-specific IP
phone.
MAC-local CFG File
MAC-local CFG file, which is named after the MAC address of the IP phone. For example, if the MAC address of an
IP phone is 00156574B150, the name of the MAC-local CFG file is 00156574b150-local.cfg (lowercase). It contains
changes associated with a non-static parameter that you make via the web user interface or handset user interface
(for example, changes for time and date formats).
This file generates only if you enable the provisioning priority mechanism. It is stored locally on the IP phone and
you can upload it to the provisioning server each time the file updates. This file enables the users to keep their per-
sonalized configuration settings, even though the IP phone performs auto provisioning.
Note : The non-static changes that you made before enabling the provisioning priority mechanism are not saved in the gen-
erated MAC-local file, but the previous settings still take effect on the phone. The static changes are never be saved to the
<MAC>-local.cfg file.
The provisioning priority mechanism is enabled by the parameter “static.auto_provision.custom.protect”.
Configuration File Customization
You can create some new CFG files by making a copy and renaming the configuration template file (for example,
sip.cfg, account.cfg). You can rearrange the parameters in the configuration template file and create your own con-