Optional Resync Arguments - Cisco SPA921 - - IP Phone Provisioning Manual

Creating Provisioning Scripts
Proprietary Plain-Text Configuration File
Cisco Small Business IP Telephony Devices Provisioning Guide
If scheme is omitted, tftp is assumed. The server can be a DNS-recognized host
name or a numeric IP address. The port is the destination UDP or TCP port
number. The filepath must begin with the root directory (/). In other words, it must
be an absolute path.
If server is missing, then the tftp server specified through DHCP (option 66) is
used instead.
If port is missing, then the standard port for the specified scheme is used instead
(tftp uses UDP port 69, http uses TCP port 80, https uses TCP port 443). A filepath
must be present. It need not necessarily refer to a static file, but can indicate
dynamic content obtained through CGI.
Macro expansion applies within URLs. The following are examples of valid URLs:
/$MA.cfg
/cisco/spa021025.bin
192.168.1.130/profiles/init.cfg
tftp://prov.call.com/cpe/cisco$MA.cfg
http://neptune.speak.net:8080/prov/$D/$E.cfg
https://secure.me.com/profile?Linksys

Optional Resync Arguments

The URLs entered in Profile_Rule* parameters may be preceded by optional
arguments, collectively enclosed by square brackets. The recognized options are
key, post, and alias.
key
The key option is used to specify an encryption key. It is required to decrypt
profiles which 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"]
2
47