Cisco SPA921 - - IP Phone Provisioning Manual page 50

Creating Provisioning Scripts
Proprietary Plain-Text Configuration File
Cisco Small Business IP Telephony Devices Provisioning Guide
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, as given to SPC.
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 specified, on the other hand,
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.
For example, GPP_F could contain the following POST body template:
Product = "$PN"; MAC_Addr = "$MA"; Ser_Num = "$SN"; SW_Ver = "$SWVER";
Then, a URL option such as the following would use the POST method to convey
the information to the server in the body of the profile request message (shown
here with an accompanying URL):
[--post f ] http://ps.one.com/cpe/resyncs?
alias
The alias option provides a flexible means of recognizing alternative parameter
names in XML-based configuration profiles. This is useful in cases where part of
the configuration profile is obtained from a customer database form that uses
different terminology than expected by the IP Telephony Device.
For example, a customer XML profile specifies the SIP registration parameters:
name, number, auth-secret, enclosed in an XML element hierarchy as follows:
<CPE>
<SIP-Credentials>
<name>J. Smith</name>
<number>14085551234</number>
<auth-secret>732091751563sfd</auth-secret>
2
48