Configuration Profile - Cisco Small Business SPA2102 Administration Manual

Basic Administration and Configuration
Provisioning Your ATA Device
Cisco Small Business ATA Administration Guide

Configuration Profile

The ATA configuration profile can be either an XML file or a binary file with a
proprietary format.
The XML file consists of a series of elements (one per configuration parameter),
encapsulated within the element tags <flat-profile> ... </flat-profile>. The
encapsulated elements specify values for individual parameters. Here is an
example of a valid XML profile:
<flat-profile>
<Admin_Passwd>some secret</Admin_Passwd>
<Upgrade_Enable>Yes</Upgrade_Enable>
</flat-profile>
Binary format profiles contain ATA parameter values and user access permissions
for the parameters. By convention, the profile uses the extension .cfg (for example,
spa2102.cfg). The Profile Compiler (SPC) tool compiles a plain-text file containing
parameter-value pairs into a properly formatted and encrypted .cfg file. The SPC
tool is available for the Win32 environment and Linux-i386-elf environment.
Requests for SPC tools compiled on other platforms are evaluated on a case-by-
case basis. Please contact your sales representative for further information about
obtaining the SPC tool.
The syntax of the plain-text file accepted by the profile compiler is a series of
parameter-value pairs, with the value in double quotes. Each parameter-value pair
is followed by a semicolon. Here is an example of a valid text source profile for
input to the SPC tool:
Admin_Passwd "some secret";
Upgrade_Enable "Yes";
Refer to the SPA Provisioning Guide for further details.
The names of parameters in XML profiles can generally be inferred from the ATA
configuration Web pages, by substituting underscores (_) for spaces and other
control characters. Further, to distinguish between Lines 1, 2, 3, and 4,
corresponding parameter names are augmented by the strings _1_, _2_, _3_, and
_4_. For example, Line 1 Proxy is named Proxy_1_ in XML profiles.
Parameters in the case of source text files for the SPC tool are similarly named,
except that to differentiate Line 1, 2, 3, and 4, the appended strings ([1], [2], [3], or
[4]) are used. For example, the Line 1 Proxy is named Proxy[1] in source text
profiles for input to the SPC.
2
46