Aastra Telecom 41-001343-02 manual Vendor Configuration File Encryption

Encrypted Files on the IP Phone

For firmware version 2.2.0 and above:

C:\>anacrypt -i -p 1234abcd

or

C:\>anacrypt -i -p 1234abcd -v2

For any firmware version:

C:\>anacrypt -i -p 1234abcd -v1

Example 2

Encrypting a single aastra.cfg file with password 1234abcd (for firmware version 3.3.1):

C:\>anacrypt aastra.cfg -p 1234abcd -v3

Example 3

Encrypting a <mac>.cfg file with password 1234abcd (for firmware version 3.3.1):

C:\>anacrypt 00085d000000.cfg -p 1234abcd -v3

Example 4

Encrypting a <mac>.cfg file with password 1234abcd using MAC encryption (for firmware version 3.3.1):

C:\>anacrypt 00085d000000.cfg -m -p 1234abcd -v3

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):

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):

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 Aastra method of file encryption.

Note:

The aastra.cfg file is not encrypted with this feature.

You can set the phone-specific encryption key using the configuration files only.

For more information about configuration file encryption, contact Aastra Technical Support.

41-001343-02 REV04 – 05.2014 7-4