Applicable to Quoted
String Operands
Applicable to Integer
and Version Operands
DescriptionAlternate
Syntax
Operator
NoYesless than or equal tole<=
NoYesgreater thangt>
NoYesgreater than or equal toge>=
YesYesandAND
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.
When used in the context of the Profile_Rule* and Upgrade_Rule parameters, conditional expressions must
be enclosed within the syntax “(expr)?” as in this upgrade rule example:
($SWVER ne sip68xx.11-0-0MPP)? http://ps.tell.com/sw/sip68xx.11-0-0MPP-BN (BN==Build
Number).loads
Do not use the preceding syntax with parentheses to configure the Resync_Trigger_* parameters.
URL Syntax
Use Standard URL syntax to specify how to retrieve configuration files and firmware loads in Profile_Rule*
and Upgrade_Rule parameters, respectively. The syntax is as follows:
[ scheme:// ] [ server [:port]] filepath
Where scheme is one of these values:
•
tftp
•
http
•
https
If scheme is omitted, tftp is assumed. The server can be a DNS-recognized hostname or a numeric IP address.
The port is the destination UDP or TCP port number. The filepath must begin with the root directory (/); it
must be an absolute path.
If server is missing, the tftp server specified through DHCP (option 66) is used.
For upgrade rules, the server must be specified.Note
If port is missing, the standard port for the specified scheme is used. (tftp uses UDP port 69, http uses TCP
port 80, https uses TCP port 443.)
A filepath must be present. It need not necessarily refer to a static file, but can indicate dynamic content
obtained through CGI.
Cisco IP Phone 6800 Series Multiplatform Phones Provisioning Guide
19
Provisioning Scripts
Open Profile Encryption with AES
To Next Page
Loading...
Need help?
General
