Auto Provisioning Guide for Yealink Teams IP Phones
38
If configuration files have been AES encrypted, the phone will uses the Common AES key to
decrypt the Common CFG file and the MAC-Oriented AES key to decrypt the <MAC>.cfg file
after downloading the configuration files. For more information on how the phone decrypts
configuration files, refer to
Yealink Configuration Encryption Tool User Guide
.
Using MAC-local CFG File
Updating configurations in the <MAC>-local.cfg file
You can configure whether the phone updates configurations in the <MAC>-local.cfg file
during auto provisioning. This process is controlled by the value of the parameter
“static.auto_provision.custom.protect”. If the phone is configured to keep user’s personalized
settings (by setting the value of the parameter “static.auto_provision.custom.protect” to 1), it
will update configurations in the <MAC>-local.cfg file. If the value of the parameter
“overwrite_mode” is set to 1 in the boot file, the value of the parameter
“static.auto_provision.custom.protect” will be forced to set to 1.
The IP phone updates configuration files during auto provisioning in sequence: CFG files
referenced in the boot file>MAC-local CFG file (if no boot file is found, Common CFG
file>MAC-Oriented CFG file>MAC-local CFG file). The configurations in the <MAC>-local.cfg
file take precedence over the ones in other downloaded configuration files. As a result, the
personalized settings of the phone configured via the phone or web user interface can be kept
after auto provisioning.
Verifying Configurations
After auto provisioning, you can then verify the update via phone user interface or web user
interface of the phone. For more information, refer to
Yealink phone-specific user guide
.
During the auto provisioning process, you can monitor the downloading requests and response
messages by a WinPcap tool. The following shows some examples.
To Next Page
Loading...
