Yealink SIP-T2 Series - Page 27

Getting Started
17
#Group4: Configure expansion module key.
expansion_module.X.key.Y.type =
expansion_module.X.key.Y.line =
expansion_module.X.key.Y.value =
expansion_module.X.key.Y.pickup_value =
expansion_module.X.key.Y.label =
expansion_module.X.key.Y.xml_phonebook =
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. 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.
Yealink IP phones have built-in system ring tones. You can change the ring type, or
customize a ring tone and upload it to the phone via auto provisioning.
The ring tone file must meet the following:
Phone Model
File Format
Single File Size
Total Files Size
SIP-T28P/T26P/T22P/T20P
.wav
<=100KB
<=100KB
The ring tone file must be PCMU audio format, mono channel, 8K sample rate and 16 bit
resolution.
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 5 and Editing MAC-Oriented CFG File on page 7.