Vendor Configuration File Encryption - Aastra 9143i Series Administrator's Manual

IP Phone Administrator Guide
Encrypted Files on the IP Phone
Example 5
Encrypting all cfg files in C:\data with password 1234abcd using the new MAC
encryption and generating a security.tuz file at the same time.(2.2.0 and up)
C:\>anacrypt -d C:\data -p 1234abcd -m -i
Example 6
Encrypting all cfg files in C:\data with password 1234abcd using the and
generating a security.tuz file at the same time for all firmware versions.(any
version)
C:\>anacrypt -d C:\data -p 1234abcd -i -v1

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 Aastra
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 Aastra
Technical Support.
7-6
Note: The aastra.cfg file is not encrypted with this feature.
41-001160-03, Rev 00, Releaes 2.4