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

Profile_Rule_D

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 56 highlights

Creating Provisioning Scripts Using Provisioning Parameters 2 3. Profile_Rule_C 4. Profile_Rule_D Each evaluation may result in a profile being retrieved from a remote provisioning server, possibly updating some number of internal parameters. If an evaluation fails, the resync sequence is interrupted, and is retried again from the beginning specified by the Resync_Error_Retry_Delay parameter (seconds). If all evaluations succeed, the device waits for the second specified by the Resync_Periodic parameter, and then performs a resync again. The contents of each Profile_Rule* parameter consist of a set of alternatives. The alternatives are separated by the | (pipe) character. Each alternative consists of a conditional expression, an assignment expression, a profile URL, and any associated URL options. All these components are optional within each alternative. The following are the valid combinations, and the order in which they must appear, if present: [ conditional-expr ] [ assignment-expr ] [[ options ] URL ] Within each Profile_Rule* parameter, all of the alternatives except the last one must provide a conditional expression. This expression is evaluated and processed as follows: 1. Conditions are evaluated from left to right, until one is found that evaluates as true (or until one alternative is found with no conditional expression) 2. Any accompanying assignment expression is evaluated, if present 3. If a URL is specified as part of that alternative, an attempt is made to download the profile located at the specified URL, and update the internal parameters accordingly. If all alternatives have conditional expressions, and none evaluates to true (or if the whole profile rule is empty), then the entire Profile_Rule* parameter is skipped, and the next profile rule parameter in the sequence is evaluated. The following are some examples of valid programming for a single Profile_Rule* parameter. The following example resyncs unconditionally to the profile at the specified URL, performing an HTTP GET request to the remote provisioning server. http://remote.server.com/cisco/$MA.cfg Cisco Small Business IP Telephony Devices Provisioning Guide 54

  • 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
54
2
3.
Profile_Rule_C
4.
Profile_Rule_D
Each evaluation may result in a profile being retrieved from a remote provisioning
server, possibly updating some number of internal parameters. If an evaluation
fails, the resync sequence is interrupted, and is retried again from the beginning
specified by the Resync_Error_Retry_Delay parameter (seconds). If all evaluations
succeed, the device waits for the second specified by the Resync_Periodic
parameter, and then performs a resync again.
The contents of each Profile_Rule* parameter consist of a set of alternatives. The
alternatives are separated by the | (pipe) character. Each alternative consists of a
conditional expression, an assignment expression, a profile URL, and any
associated URL options. All these components are optional within each alternative.
The following are the valid combinations, and the order in which they must appear,
if present:
[ conditional-expr ] [ assignment-expr ] [[ options ] URL ]
Within each Profile_Rule* parameter, all of the alternatives except the last one must
provide a conditional expression. This expression is evaluated and processed as
follows:
1.
Conditions are evaluated from left to right, until one is found that evaluates as
true (or until one alternative is found with no conditional expression)
2.
Any accompanying assignment expression is evaluated, if present
3.
If a URL is specified as part of that alternative, an attempt is made to download
the profile located at the specified URL, and update the internal parameters
accordingly.
If all alternatives have conditional expressions, and none evaluates to true (or if the
whole profile rule is empty), then the entire Profile_Rule* parameter is skipped,
and the next profile rule parameter in the sequence is evaluated.
The following are some examples of valid programming for a single Profile_Rule*
parameter.
The following example resyncs unconditionally to the profile at the specified URL,
performing an HTTP GET request to the remote provisioning server.