Compression And Encryption - Cisco SPA1112 Provisioning Manual

Creating XML Provisioning Scripts

Compression and Encryption

Compression and Encryption
Provisioning Guide for Cisco SPA100 and SPA200 Series Analog Telephone Adapters
</flat-profile>
• Numeric character escapes, using decimal and hexadecimal values (s.a. &
#40; and &#x2e;), are translated.
• The firmware does not support the full Unicode character set, but only the
ASCII subset.
The configuration profile can be compressed to reduce the network load on the
provisioning server. It also can be encrypted to protect confidential information.
Compression is not required, but it must precede encryption.
The supported compression method is the gzip deflate algorithm (RFC1951). The
gzip utility and the compression library that implements the same algorithm (zlib)
are available from Internet sites.
To identify when compression is applied, the ATA expects the compressed file to
contain a gzip compatible header, as generated by invoking the gzip utility on the
original Open profile. The ATA inspects the downloaded file header to determine
the format of the file.
For example, if profile.xml is a valid profile, the file profile.xml.gz is also
accepted. This profile type can be generated with either of the following
commands:
>gzip profile.xml
replaces original file with compressed file.
>cat profile.xml | gzip > profile.xml.gz
leaves original file in place, produces new compressed file.
A tutorial on compression is provided in
page 61.
Open Profile gzip Compression,
2
20