Cisco SPA901-UK Provisioning Guide - Page 43

Creating Provisioning Scripts, Operator, Alternate, Syntax, Description, Applicable to, Integer

Get Cisco SPA901-UK - Small Business Pro PDF manuals and user guides
UPC - 745883570751
View all Cisco SPA901-UK manuals
Add to My Manuals
Save this manual to your list of manuals

Page 43 highlights

Creating Provisioning Scripts Proprietary Plain-Text Configuration File 2 Note that version numbers take the form of three non-negative integers separated by periods (major, minor, and build numbers), plus an optional alphanumeric string in parentheses. No spaces are allowed. The following are examples of valid version numbers: 1.0.31(b) 1.0.33 2.0.3(G) 2.0.3(0412s) 2.0.6 Quoted strings can be compared for equality or inequality. Integers and version numbers can also be compared arithmetically. The comparison operators can be expressed as symbols or as acronyms. Acronyms are particularly convenient when expressing the condition in an XML-style profile. Operator Alternate Description Syntax = eq equal to != ne not equal to < lt less than gt greater than >= ge greater than or equal to Applicable to Integer and Version Operands Yes Yes Yes Yes Yes Yes Applicable to Quoted String Operands Yes Yes No No No No For legacy support to firmware versions prior to 2.0.6, the not-equal-to operator can also be expressed as a single ! character (in place of the two-character != string). Conditional expressions typically involve macro-expanded variables. For example: $REGTMR1 gt 300 and $PRVTMR gt 1200 and "$EXTIP" ne "" $SWVER ge 2.0.6 and "$CCERT" eq "Installed" Cisco Small Business IP Telephony Devices Provisioning Guide 42

  • 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
Creating Provisioning Scripts
Proprietary Plain-Text Configuration File
Cisco Small Business IP Telephony Devices Provisioning Guide
42
2
Note that version numbers take the form of three non-negative integers separated
by periods (major, minor, and build numbers), plus an optional alphanumeric string
in parentheses. No spaces are allowed.
The following are examples of valid version numbers:
1.0.31(b)
1.0.33
2.0.3(G)
2.0.3(0412s)
2.0.6
Quoted strings can be compared for equality or inequality. Integers and version
numbers can also be compared arithmetically. The comparison operators can be
expressed as symbols or as acronyms. Acronyms are particularly convenient
when expressing the condition in an XML-style profile.
For legacy support to firmware versions prior to 2.0.6, the not-equal-to operator
can also be expressed as a single ! character (in place of the two-character !=
string).
Conditional expressions typically involve macro-expanded variables. For example:
$REGTMR1 gt 300 and $PRVTMR gt 1200 and “$EXTIP” ne “”
$SWVER ge 2.0.6 and “$CCERT” eq “Installed”
Operator
Alternate
Syntax
Description
Applicable to
Integer and
Version
Operands
Applicable to
Quoted String
Operands
=
eq
equal to
Yes
Yes
!=
ne
not equal to
Yes
Yes
<
lt
less than
Yes
No
<=
le
less than or
equal to
Yes
No
>
gt
greater than
Yes
No
>=
ge
greater than
or equal to
Yes
No