Table of Contents
Advertisement
Creating Provisioning Scripts
Proprietary Plain-Text Configuration File
Cisco Small Business IP Telephony Devices Provisioning Guide
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.
Assignment Expressions
Arbitrary parameters can be pre-assigned values within the context of
Profile_Rule* and Upgrade_Rule parameter. This causes the assignment to be
performed before the profile if retrieved.
The syntax for performing these assignments is a list of individual parameter
assignments, enclosed within parentheses ( assignments )!, with each assignment
taking the form:
ParameterXMLName = "Value" ;
Note that the recognized parameter names correspond to the names as for XML-
based profiles.
Any parameter can be assigned a new value in this way, and macro-expansion
applies. For example, the following is a valid assignment expression:
( User_ID_1_ = "uid$B" ; GPP_C = "" ; GPP_D = "$MA" ; )!
For conciseness, the general purpose parameters GPP_A through GPP_P can also
be referred to by the single lowercase letters a through p. The example above is
equivalent to the following:
( User_ID_1_ = "uid$B" ; c = "" ; d = "$MA" ; )!
White space can be used for readability.
2
43
Advertisement
Table of Contents
