Yealink SIP-T23G [61/841] Sip t48g t46g t42g t41p t29g t27p t23p t23g t21 p e2 t19 p e2 ip phones running

Getting Started

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 and DSS

keys), after auto provisioning. These specific scenarios are applicable to

SIP-T48G/T46G/T42G/T41P/T29G/T27P/T23P/T23G/T21(P) E2/T19(P) E2 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

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:

None

Phone User Interface:

None

auto_provision.custom.sync

0 or 1

Description:

Enables or disables the IP phone to periodically (every 5 minutes) upload the

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”.