Yealink SIP-T2 Series, Administrator'S Manual

Page: 77 / 1009

Getting Started
55
Server
HTTP/HTTPS TFTP/FTP
Linux
Support: ~ ` ! @ $ ^
( ) _ - , . ' ; [ ] { } | < > : "
(including space)
Not Support: / \ * ? #
% & = +
Support: ~ ` ! @ $ ^
( ) _ - , . ' ; [ ] { } | < > :
" % & = + (including
space)
Not Support: / \ * ? #
Generally, the administrator deploys phones in batch via auto provisioning, yet some
users would like to keep the personalized settings (e.g., ringtones, dial plan, time format
and DSS keys), after auto provisioning. These specific scenarios are applicable to SIP
VP-T49G/SIP-T48G/T46G/T42G/T41P/T40P/T29G/T27P/T27G/T23P/T23G/T21(P) E2/T19(P)
E2/CP860 IP phones running firmware version 80 or later. The following demonstrated
specific scenarios are taking SIP-T46G/T23G IP phones as example for reference.
Note
The following table lists the configuration parameters used to determine the phone
behavior for keeping user personalized settings:
Parameters Permitted Values Default
auto_provision.custom.protect 0 or 1 0
Description:
Enables or disables the IP phone to keep user personalized settings after auto
provisioning.
0-Disabled
1-Enabled
If it is set to 1 (Enabled), personalized settings
configured via web
or phone user
interface will be kept after auto provisioning.
Web User Interface:
Yealink IP phones support FTP, TFTP, HTTP and HTTPS protocols for uploading the
MAC-local CFG file. This section takes the TFTP protocol as an example. Before
performing the following, make sure the provisioning server supports uploading.
If you are using the HTTP/HTTPS server, you can specify the way the IP phone uploads the
MAC-local CFG file to the provisioning server. It is determined by the value of the
parameter “auto_provision.custom.upload_method”.
Platform