Provisioning Examples
Profile Management
Provisioning Guide for Cisco SPA100 and SPA200 Series Analog Telephone Adapters 61
4
Profile Management
This section demonstrates the formation of configuration profiles in preparation for
downloading. To explain the functionality, TFTP from a local PC is used as the
resync method, although HTTP or HTTPS can be used as well.
Open Profile gzip Compression
A configuration profile in XML format can become quite large if all parameters are
individually specified by the profile. To reduce the load on the provisioning server,
the ATA supports compression of the XML file, by using the deflate compression
format supported by the gzip utility (RFC 1951).
NOTE Compression must precede encryption for the ATA to recognize a compressed and
encrypted XML profile.
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 ATA expects the file to contain a
valid gzip header.
Exercise
STEP 1 Install gzip on the local PC.
STEP 2 Compress the basic.txt configuration profile (described in the TFTP Resync
exercise) 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 ATA.
To Next Page
Loading...
Need help?
General
