Keeping User's Personalized Settings After Auto Provisioning; Keeping User's Personalized Settings Configuration - Yealink SIP-T2 Series Administrator's Manual

Keeping User's Personalized Settings after Auto Provisioning

Generally, you deploy phones in batch and timely maintain company phones via auto provisioning, yet some users
would like to keep the personalized settings (for example, ring tones, wallpaper or DSS keys) after auto provisioning.
Topics

Keeping User's Personalized Settings Configuration

Auto Provisioning Flowchart for Keep User's Personalized Configuration Settings
Example: Keeping User's Personalized Settings
Clearing User's Personalized Configuration Settings
Keeping User's Personalized Settings Configuration
The following table lists the parameters you can use to keep user's personalized settings.
Parameter static.auto_provision.custom.protect
It enables or disables the IP phone to keep user's personalized settings after auto provisioning.
Note: The provisioning priority mechanism (phone/web user interface >central provisioning >factory
Description
defaults) takes effect only if the value of this parameter is set to 1 (Enabled). If "overwrite_mode" is set to
1 in the boot file, the value of this parameter will be set to 1 (Enabled).
0-Disabled
Permitted
1-Enabled, <MAC>-local.cfg file generates and personalized non-static settings configured via the web
Values
or phone user interface will be kept after auto provisioning.
Default 0
Parameter static.auto_provision.custom.sync
It enables or disables the IP phone to upload the <MAC>-local.cfg file to the server each time the file
updates, and to download the <MAC>-local.cfg file from the server during auto provisioning.
Description
Note: It works only if "static.auto_provision.custom.protect" is set to 1 (Enabled). The upload/download
path is configured by the parameter "static.auto_provision.custom.sync.path".
Permitted 0-Disabled
Values 1-Enabled
Default 0
Parameter static.auto_provision.custom.sync.path
It configures the URL for uploading/downloading the <MAC>-local.cfg file.
If it is left blank, the IP phone will try to upload/download the <MAC>-local.cfg file to/from the pro-
Description
visioning server.
Note: It works only if "static.auto_provision.custom.sync" is set to 1 (Enabled).
Permitted
URL
Values
Default Blank
Parameter static.auto_provision.custom.upload_method
It configures the way the IP phone uploads the <MAC>-local.cfg file, <MAC>-calllog.xml file or <MAC>-
Description
contact.xml file to the provisioning server (for HTTP/HTTPS server only).
Permitted 0-PUT
<y0000000000xx>.cfg
<y0000000000xx>.cfg
<y0000000000xx>.cfg
[1]
<y0000000000xx>.cfg
Phone Provisioning
87