Keeping User's Personalized Settings Configuration; Auto Provisioning Flowchart For Keep User's Personalized Configuration Settings - Yealink SIP-T3 Administrator's Manual

Hide thumbs Also See for SIP-T3:
Table of Contents

Advertisement

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 the user's personalized settings.
Parameter static.auto_provision.custom.protect
It enables or disables the phone to keep the 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
Values
web or phone user interface will be kept after auto provisioning.
Default
0
Parameter static.auto_provision.custom.sync
It enables or disables the 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
1-Enabled
Values
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 phone will try to upload/download the <MAC>-local.cfg file to/from the provisioning
Description
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 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).
0-PUT
Permitted
Values
1-POST
Default
0
Auto Provisioning Flowchart for Keep User's Personalized Configuration
Settings
The following shows an auto provisioning flowchart for Yealink phones when a user wishes to keep the user's per-
sonalized configuration settings.
<y0000000000xx>.cfg
<y0000000000xx>.cfg
<y0000000000xx>.cfg
<y0000000000xx>.cfg
Phone Provisioning
103

Advertisement

Table of Contents
loading

This manual is also suitable for:

Sip-t2Sip-t4Sip-t5Sip-cp920

Table of Contents