Cisco SPA901-UK Provisioning Guide - Page 38

Status Messages, Sample Configuration File, Proprietary Plain-Text Configuration File

Get Cisco SPA901-UK - Small Business Pro PDF manuals and user guides
UPC - 745883570751
View all Cisco SPA901-UK manuals
Add to My Manuals
Save this manual to your list of manuals

Page 38 highlights

Creating Provisioning Scripts Proprietary Plain-Text Configuration File 2 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 Proprietary Plain-Text Configuration File 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. Cisco Small Business IP Telephony Devices Provisioning Guide 37

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
Creating Provisioning Scripts
Proprietary Plain-Text Configuration File
Cisco Small Business IP Telephony Devices Provisioning Guide
37
2
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
Proprietary Plain-Text Configuration File
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.