Cisco Systems WRP400 Telephone Accessories User Manual


 
Basic Administration and Configuration
Provisioning Your ATA Device
ATA Administration Guide 45
2
The ATA device supports up to 256-bit symmetric key encryption of profiles. For
the initial transfer of the profile encryption key (initial provisioning stage), the ATA
device can receive a profile from an encrypted channel (HTTPS), or it can resync
to a binary profile generated by the Cisco-supplied profile compiler. In the latter
case, the profile compiler can encrypt the profile specifically for the target ATA
device, without requiring an explicit key exchange.
Remote firmware upgrade is achieved via TFTP or HTTP (firmware upgrades
using HTTPS are not supported). Remote upgrades are controlled by configuring
the desired firmware image URL into the ATA device via a remote profile resync.
For further information about remote provisioning refer to the SPA Provisioning
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.