| Phone Provisioning | 33
For example:
• [T58A, CP960]include:config <configure/Teams.cfg>
• [T56A]include:config “http://10.2.5.206/configure/account.cfg”
•
## file Teams.cfg only applies to T58S and CP960 phones, file account.cfg only applies to T56A phones
5.
Specify the overwrite mode and exclude mode.
For example:
• overwrite_mode = 1
• specific_model.excluded_mode = 1
6.
Save the boot file and place it on the provisioning server.
Related information
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:
• Static: The parameters start with a prefix “static.”, for example, static.network.lldp.enable .
• Non-static: The parameters do not start with a prefix “static.”, for example,phone_setting.phone_lock.enable.
You can deploy and maintain a mass of Yealink Teams IP Phones automatically through configuration files stored in a
provisioning server.
Note: For protecting against unauthorized access, you can encrypt configuration files. For more information
on encrypting configuration files, refer to Encrypting Configuration Files.
•
Common CFG File
•
MAC CFG File
•
Configuration File Customization
Common CFG File
Common CFG file, named <y0000000000xx>.cfg, contains parameters that affect the basic operation of the 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 following table lists the name of the common CFG file for each phone model:
Phone Model Common CFG file
T58A y000000000058.cfg
T56A y000000000056.cfg
T55A y000000000099.cfg
CP960 y000000000073.cfg
VP59 y000000000091.cfg
To Next Page
Loading...
Need help?
General
