Creating XML Provisioning Scripts
Using Provisioning Parameters
Provisioning Guide for Cisco SPA100 and SPA200 Series Analog Telephone Adapters
29
2
In the following example, the profile returned by the server is assumed to contain
XML element tags that need to be remapped to proper parameter names by the
aliases map stored in GPP_B.
[--alias b] https://p.tel.com/account/spa$MA.xml
A resync is typically considered unsuccessful if a requested profile is not received
from the server. This default behavior can be overridden by the parameter
Resync_Fails_On_FNF. If Resync_Fails_On_FNF is set to No, then the device
accepts a file-not-found response from the server as a successful resync. The
default value for Resync_Fails_On_FNF is Yes.
Report Rule
The ATA provides a mechanism for reporting its current internal configuration to
the provisioning server. This is useful for development and debugging. The report
syntax is similar to the Open format profile. All provisionable parameters are
included, except for the values of passwords, keys, and the GPP_SA to GPP_SD
parameters, which are not shown.
The Report_Rule parameter is evaluated like a profile rule parameter. In other
words, it accepts a URL, optionally qualified with a bracketed expression. The URL
specifies the target destination for the report and an encryption key can be
included as an option.
The URL scheme can be TFTP, HTTP, or HTTPS. When using TFTP, the operation
performed is TFTP PUT. In the case of HTTP and HTTPS, the operation performed
is HTTP POST or HTTP PUT.
If an encryption key is specified, the report is encrypted using 256-bit AES in CBC
mode. The encrypted report can be decrypted with the following OpenSSL (or
equivalent) command:
openssl enc –d –aes-256-cbc –k secretphrase –in rep.xml.enc –out rep.xml
The following is an example of the corresponding Report_Rule configuration:
[ --key secretphrase ] http://prov.serv.net/spa/$MA/rep.xml.enc