Mitel 6867i Premium, Руководство администратора

Страница: 659 / 1042

Encrypted Files on the IP Phone
7-6
Example 5
Encrypting all cfg files in C:\data with password 1234abcd using MAC encryption and generating
a security.tuz file at the same time (for firmware version 3.3.1 and above):
C:\>anacrypt -d C:\data -p 1234abcd -m -i -v3
Example 6
Encrypting all cfg files in C:\data with password 1234abcd and generating a security.tuz file at
the same time (for firmware version 3.3.1 and above):
C:\>anacrypt -d C:\data -p 1234abcd -i -v3
VENDOR CONFIGURATION FILE ENCRYPTION
Some vendors can have specific methods to encrypt files on their configuration servers. For
each phone, the configuration server can generate a random hex string (encryption key) that
is used to encrypt the phone’s MAC-specific configuration file.
The encryption key is placed in a plain text MAC-specific configuration file that the server
downloads to the phone. After the phone receives the file, it updates the encryption key.
This method of encryption does not affect the implementation of the Mitel method of file
encryption.
You can set the phone-specific encryption key using the configuration files only.
For more information about configuration file encryption, contact Mitel Technical Support.
CONFIGURING VENDOR CONFIGURATION FILE ENCRYPTION
Use the following procedure to configure vendor configuration file encryption on the IP Phones.
For specific parameters you can set in the configuration files for automatic update, see Appendix
A, the section, “Configuration Encryption Setting” on
page A-285
.
Note:
The phone will not reboot automatically after updating the configuration encryption
key. Upon the next reboot, the phone will download the encrypted MAC-specific
configuration file from configuration server (provided that the unencrypted MAC-specific
file is not present on the configuration server)
Note:
The
startup.cfg
file is not encrypted with this feature.
CONFIGURATION FILES