Linksys SPA921 Cisco Small Business IP Telephony Devices Provisioning Guide - Page 58

Upgrade Rule, is HTTP POST.

Get Linksys SPA921 - Cisco - IP Phone PDF manuals and user guides
UPC - 745883570799
View all Linksys SPA921 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 58 highlights

Creating Provisioning Scripts Using Provisioning Parameters 2 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. 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 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. Upgrade Rule The IP Telephony Device provides one configurable remote upgrade parameter, Upgrade_Rule. This parameter accepts a syntax similar to the profile rule parameters. URL options not supported for upgrades, but conditional expressions and assignment expressions can be used. If conditional expressions are used, the parameter can be populated with multiple alternatives, separated by the | character. The syntax for each alternative is as follows: [ conditional-expr ] [ assignment-expr ] URL As in the case of Profile_Rule* parameters, the Upgrade_Rule parameter evaluates each alternative until a conditional expression is satisfied or an alternative has no conditional expression. The accompanying assignment expression is evaluated, if specified. Then, an upgrade to the specified URL is attempted. Cisco Small Business IP Telephony Devices Provisioning Guide 56

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
Creating Provisioning Scripts
Using Provisioning Parameters
Cisco Small Business IP Telephony Devices Provisioning Guide
56
2
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.
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:
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.
Upgrade Rule
The IP Telephony Device provides one configurable remote upgrade parameter,
Upgrade_Rule. This parameter accepts a syntax similar to the profile rule
parameters. URL options not supported for upgrades, but conditional expressions
and assignment expressions can be used. If conditional expressions are used, the
parameter can be populated with multiple alternatives, separated by the |
character. The syntax for each alternative is as follows:
[ conditional-expr ] [ assignment-expr ] URL
As in the case of Profile_Rule* parameters, the Upgrade_Rule parameter evaluates
each alternative until a conditional expression is satisfied or an alternative has no
conditional expression. The accompanying assignment expression is evaluated, if
specified. Then, an upgrade to the specified URL is attempted.