Compression must precede encryption for the phone to recognize a compressed and encrypted XML
profile.
Note
For integration into customized back-end provisioning server solutions, the open source zlib compression
library can be used in place of the standalone gzip utility to perform the profile compression. However, the
phone expects the file to contain a valid gzip header.
Procedure
Step 1
Install gzip on the local PC.
Step 2
Compress the basic.txt configuration profile (described in TFTP Resync, on page 45) by invoking gzip
from the command line:
gzip basic.txt
This generates the deflated file basic.txt.gz.
Step 3
Save the basic.txt.gz file in the TFTP server virtual root directory.
Step 4
Modify the Profile_Rule on the test device to resync to the deflated file in place of the original XML file, as
shown in the following example:
tftp://192.168.1.200/basic.txt.gz
Step 5
Click Submit All Changes.
Step 6
Observe the syslog trace from the phone.
Upon resync, the phone downloads the new file and uses it to update its parameters.
Related Topics
Open Profile Compression, on page 16
Encrypt a Profile with OpenSSL
A compressed or uncompressed profile can be encrypted (however, a file must be compressed before it is
encrypted). Encryption is useful when the confidentiality of the profile information is of particular concern,
such as when TFTP or HTTP is used for communication between the phone and the provisioning server.
The phone supports symmetric key encryption by using the 256-bit AES algorithm. This encryption can be
performed by using the open source OpenSSL package.
Cisco IP Phone 6800 Series Multiplatform Phones Provisioning Guide
59
Provisioning Examples
Encrypt a Profile with OpenSSL
To Next Page
Loading...
Need help?
General
