Yealink SIP-T48G [58/384] Generally the administrator deploys phones in batch via auto provisioning yet some

Yealink IP Phones Auto Provisioning Guide

Generally, the administrator deploys phones in batch via auto provisioning, yet some

users would like to remain 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 IP phones running firmware

version 80 or later. The following demonstrated specific scenarios are taking SIP-T23G IP

phones as example for reference.

The following table lists the configuration parameters used to determine the phone

behavior for protecting personalized settings:

Parameters

Permitted Values

Default

auto_provision.custom.protect

0 or 1

Description:

Enables or disables the IP phone to protect 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 protected and remained after auto provisioning.

auto_provision.custom.sync

0 or 1

Description:

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

<MAC>-local.cfg file to the provisioning server, and download the <MAC>-local.cfg file

from the provisioning server during auto provisioning.

0-Disabled

1-Enabled

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(S) 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‖. For more information on

description of this parameter, refer to Description of Configuration Parameters in CFG

Files on page 91.