Yealink SIP-T48G [17/384] Encrypting configuration files

Getting Started

programablekey.X.history_type =

programablekey.X.label =

#Group3: Configure expansion module key. (Expansion module key is only applicable

to the SIP-T48G, SIP-T46G, SIP-T29G, SIP-T27P IP phones. X stands for the serial number of

expansion module, Y stands for the serial number of expansion 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.,

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 58. 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 6.