Yealink SIP-T19 E2 T4 Series, Руководство администратора

Страница: 847 / 981

Configuring Security Features
825
Encrypting and Decrypting Contact Files
Encrypted contact files can be used to protect against unauthorized access and tampering of
private information (for example, contact number). It is helpful for protecting trade secrets.
You can configure the contact files to be automatically encrypted using 16-character symmetric
keys (configured by the parameter “static.auto_provision.aes_key_16.mac”) when uploading to
the server (by setting the value of the parameter “static.auto_provision.encryption.directory” to
1). The encrypted contact files have the same file names as before. The encrypted contact files
can be downloaded from the server and decrypted using 16-character symmetric keys during
auto provisioning. If the parameter “static.auto_provision.aes_key_16.mac” is left blank, the value
of the parameter “static.auto_provision.aes_key_16.com” will be used.
If the downloaded contact files is encrypted, the IP phone will try to decrypt
<MAC>-contact.xml file using the plaintext AES key. After decryption, the IP phone resolves
contact files and updates contact information onto the IP phone system.
Incoming Signaling Validation
Yealink IP phones support the following three optional levels of security for validating incoming
network signaling:

Source IP address validation
: ensure request is received from an IP address of a server
belonging to the set of target SIP servers.

Digest authentication
: challenge requests with digest authentication using the local
credentials for the associated registered account.

Source IP address validation and digest authentication
: apply both of the above
methods.
Procedure
Incoming signaling validation can be configured using the configuration file.
Central Provisioning
(Configuration File)
<y0000000000xx>.cf
g
Configure incoming dignaling validation.
Parameter
:
sip.request_validation.source.list
sip.request_validation.digest.list
sip.request_validation.digest.realm
sip.request_validation.event