Polycom HDA50, Руководство администратора

Страница: 8 / 109

Before You Begin
Polycom, Inc. 6
● ProxyServerPort =
5082
Literal Fashion
These examples show the format of the literal fashion. The literal fashion is used when provisioning or
writing OBIPhoneXML apps.
●
ParameterGroupName
. ParameterName .
Parameter Value {replace-with-actual-value}
●
Parameter.Group.Name.ParameterGroupName.
ParameterName.
Parameter Value
The
ParameterGroupName.
is the name of the first parameter group in literal fashion. This string MUST
NOT CONTAIN ANY SPACES, and always is terminated with a period, as shown. More than one
ParameterGroupName. may be used.
The
ParameterGroupName.
is case-sensitive.
The ParameterName. is the name of the parameter, and always is terminated with a period, as shown. This
string MUST NOT CONTAIN ANY SPACES. The ParameterName
.
is case-sensitive.
The
Parameter Value
is the literal value to assign to the named parameter and may contain spaces. The
Parameter Value
is not case-sensitive, but it MUST EXACTLY MATCH the value when one or more
choices are available.
When using the literal fashion in your XML, you need to exactly match the text string for
ParameterGroupName
. ParameterName .
Parameter Value
, but text formatting such as bold face is not
required and will be removed when your script or app is processed.
Boolean Values
You can identify parameters that take a Boolean value on your device’s configuration web pages by a check
box next to the parameter name. Throughout the document, we may loosely refer to a Boolean value as
“enable/disable” or “yes/no”, but the only valid Boolean parameter values to use in a device configuration
file is either
true/false
or
True/False
(case-sensitive). This is equivalent to selecting or clearing the
check box on the configuration web pages.
Multiple Choice Values
You must provision parameters that take one of several valid options from a drop-down list on the device
message with string values that match exactly one of those choices. Otherwise, the device uses the default
choice. Matching the provisioned value against valid strings is case-sensitive and doesn’t allow extra
spaces.
When a choice must be selected, the device web page provides a drop-down menu for that parameter. Copy
that value into your provisioning script.
Parameter Values
When entering a parameter value from the web page or via provisioning, avoid adding extra white spaces
before or after the parameter value. If the value is a comma-separated list of strings or contains attributes
after a comma or semicolon, avoid adding extra white space before and after the delimiter.
For example: CertainParameter
= 1,2,3,4;a;b;c