Status Messages; Sample Configuration File; Proprietary Plain-Text Configuration File - Cisco SPA901-UK - Small Business Pro Provisioning Manual

Voice system, voice gateways, and ip telephones
Table of Contents

Advertisement

Creating Provisioning Scripts

Proprietary Plain-Text Configuration File

Proprietary Plain-Text Configuration File
Cisco Small Business IP Telephony Devices Provisioning Guide

Status Messages

After each compilation, SPC prints a final status message. Syntax error messages
are also printed if a compilation is not successful.
The status and error messages can be suppressed by using the --quiet command
line option.:
spc –-quiet . . .
Messages can be redirected to a file by using the --log file_name option.
spc –-log prov.log . . .
When the messages are redirected, the SPC command is also printed in the log
file, preceded by a timestamp.

Sample Configuration File

SPC can also be used to generate sample configuration source files (for both plain
text and XML formats), corresponding to the accompanying firmware release. The
commands for producing sample files are as follows:
# sample plain.txt to be used as source file for eventual spc compilation:
spc –-sample-profile plain.txt
# sample config.xml to be fed directly to a device running 2.0.6 or above:
spc --sample-xml config.xml
The plain-text configuration file uses a proprietary format that can be encrypted to
prevent unauthorized use of confidential information. By convention, the profile is
named with the extension .cfg (for example, spa962.cfg). The SPC tool is used to
compile the plain-text file into an encrypted CFG file.
The plain-text format is an alternative to the open format for firmware releases
2.0.6 and later, and it is the only format recognized by firmware releases prior to
2.0.6.
2
37

Advertisement

Table of Contents
loading

Table of Contents