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

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

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

Creating Provisioning Scripts Proprietary Plain-Text Configuration File 2 Operator Alternate Description Syntax > gt greater than >= ge greater than or equal to Applicable to Integer and Version Operands Yes Yes Applicable to Quoted String Operands 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" It is important to enclose macro variables in double quotes where a string literal is expected. Do not do so where a number or version number is expected. For legacy support of firmware versions prior to 2.0.6, a relational expression with no left-hand-side operand assumes $SWVER as the implicit left-hand-side. For example, ! 1.0.33 is equivalent to: $SWVER != 1.0.33. When used in the context of the Profile_Rule* and Upgrade_Rule parameters, conditional expressions must be enclosed within the syntax "( expr )?" as in the following upgrade rule example: ( $SWVER ne 2.0.6 )? http://ps.tell.com/sw/spa021024.bin On the other hand, the syntax above using parentheses should not be used when configuring the Resync_Trigger_* parameters. Cisco Small Business IP Telephony Devices Provisioning Guide 45

  • 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
Proprietary Plain-Text Configuration File
Cisco Small Business IP Telephony Devices Provisioning Guide
45
2
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”
It is important to enclose macro variables in double quotes where a string literal is
expected. Do not do so where a number or version number is expected.
For legacy support of firmware versions prior to 2.0.6, a relational expression with
no left-hand-side operand assumes $SWVER as the implicit left-hand-side. For
example, ! 1.0.33 is equivalent to: $SWVER != 1.0.33.
When used in the context of the Profile_Rule* and Upgrade_Rule parameters,
conditional expressions must be enclosed within the syntax “( expr )?” as in the
following upgrade rule example:
On the other hand, the syntax above using parentheses should not be used when
configuring the Resync_Trigger_* parameters.
>
gt
greater than
Yes
No
>=
ge
greater than
or equal to
Yes
No
Operator
Alternate
Syntax
Description
Applicable to
Integer and
Version
Operands
Applicable to
Quoted String
Operands