Yealink SIP-T23, Provisioning Manual

Page: 14 / 321

Yealink IP Phones Auto Provisioning Guide
10
interface, the other configurations in this group can also be saved to the
<MAC>-local.cfg file (if the parameter isn't configured, the value of this parameter will
be written by “%NULL%”) in addition to the modified configuration.
#Group1: Configure line key.
linekey.X.line =
linekey.X.value =
linekey.X.pickup_value =
linekey.X.type =
linekey.X.xml_phonebook =
linekey.X.label =
#Group2: Configure programable key.
programablekey.X.type =
programablekey.X.line =
programablekey.X.value =
programablekey.X.xml_phonebook =
programablekey.X.history_type =
programablekey.X.label =
To protect against unauthorized access and tampering of sensitive information (e.g.,
login password, registration information), you can encrypt configuration files using
Yealink Configuration Encryption Tool. AES keys must be 16 characters and the
supported characters contain: 0 ~ 9, A ~ Z, a ~ z and the following special characters are
also supported: # $ % * +, - . : = ? @ [ ] ^ _ { } ~
. For more information on how to encrypt
configuration files, refer to
Yealink Configuration Encryption Tool User Guide
.
When configuring some particular features, you may need to upload resource files to IP
phones, such as personalized ring tone file, language package file and logo file. Yealink
supplies some resource file templates for the particular features. Ask the distributor or
Yealink FAE for resource file templates. The following provides information on how to
customize resource files and specify the access URL for the resource files.
We recommend you do not edit the MAC-local CFG file. If you really want to edit
MAC-local CFG file, you can export and then edit it. For more information on how to
export this file,
refer to Scenario D Import or export the local configuration file
on
page 55 . For more information on how to edit this file, refer to Editing Common CFG
File
on page
4
and
Editing MAC-Oriented CFG File
on page
6
.