Cisco SPA1112 Provisioning Manual page 30

Creating XML Provisioning Scripts
Using Provisioning Parameters
Provisioning Guide for Cisco SPA100 and SPA200 Series Analog Telephone Adapters
Once the report rule is configured, an actual report can be generated and
transmitted by sending the device a SIP NOTIFY message, with the Event: report
type. The SIP NOTIFY request is handled like other SIP notifies, with the device
requiring authentication from the requesting server before honoring the request to
issue a report. Each SIP NOTIFY report request generates one attempt to transmit
the report. Retries are not supported.
Deltas Report
In addition to reporting the current internal configuration to the provisioning server,
the Report Rule has an option for triggering the reporting of configuration changes
(deltas) to the server since the last resync, reboot, or upgrade.
The syntax of this option is:
Report Rule: [--delta] URL
Where URL is the path to where the report is stored on the server.
For example, to store delta configuration changes in a file with a name like
SPA504G_<MAC>_<serial#>.xml, do one of the following:
• On the phone Web GUI, set the Report Rule field on the Configuration
Profile page (Voice tab > Provisioning tab > Configuration Profile) to:
[--delta] http://reportTargetServer/reportPath/$PN_$MA_
$SN.xml
• Add the following to your provisioning file:
<Report_Rule ua="na">[ --delta ]
http://reportTargetServer/reportPath/$PN_$MA_$SN.xml
</Report_Rule>
Status.xml Report
The Report Rule has an option to report the status.xml data if [--status] is specified
in the report rule. The status report file path should be defined after the [--status]
keyword, separated with a comma. If the [--status] keyword or the status report
file path is missing, the phone will not report the status.xml data.
For example, if the following is configured:
[--status]http://my_http_server/config-525.xml
The phone will report the status file to http://my_http_server/config-525.xml.
2
30