Table of Contents
Advertisement
Creating Provisioning Scripts
Proprietary Plain-Text Configuration File
Cisco Small Business IP Telephony Devices Provisioning Guide
Optional Resync Arguments
The URLs entered in Profile_Rule* parameters can be preceded by optional
arguments, collectively enclosed by square brackets. The options are key, post,
and alias.
key
The key option is used to specify an encryption key. It is required to decrypt
profiles that have been encrypted with an explicit key. The key itself is specified as
a (possibly quoted) string following the term --key.
Some usage examples:
[--key VerySecretValue]
[--key "my secret phrase"]
[--key a37d2fb9055c1d04883a0745eb0917a4]
The bracketed optional arguments are macro expanded. In particular, note that the
special purpose parameters GPP_SA through GPP_SD are only macro expanded
into their macro variables $SA through $SD when used as arguments of the key
option, as in the following examples:
[--key $SC]
[--key "$SD"]
In the case of XML-style profiles, the argument to --key must be the same as the
argument to the -k option given to openssl.
In the case of SPC compiled profiles, the argument to --key must be the same as
the argument to either the --ascii-key or the --hex-key options.
post
The post option provides an alternative access method for the http and https
schemes. If left unspecified, the IP Telephony device performs an HTTP GET
operation, when contacting the provisioning server. If post is specified, the device
performs an HTTP POST operation.
The body of the POST is generated from the contents of one of the general
purpose parameters, GPP_A through GPP_P, with macro expansion applied. The
GPP_* parameter to use is indicated by a single lowercase letter (a through p)
given as argument to the term --post.
Using POST provides a convenient alternative to the GET method when arbitrary
state or identifying information needs to be supplied from the IP Telephony device
to the server, as part of periodic resyncs.
2
45
Advertisement
Table of Contents
