Using Correct Parameter XML Schema, Value Ranges, and Special Characters

The configuration parameters available in the UC software templates use a variety of value types.

UC software includes an XML schema file ( polycomConfig.xsd ) that provides information about parameter type, permitted values, default values, and valid enumerated type values. You can view this template file with an XML editor.

Polycom configuration parameters support the following value types:
  • Boolean
  • Enumerated
  • Integer
  • String
The following rules apply to UC software parameter values:
  • Boolean values are not case sensitive.
  • UC software interprets Null as empty.
  • The values 0, false, and off are supported and interchangeable.
  • The values 1, true , and on are supported and interchangeable. This administrator guide documents only 0 and 1 .
The following rules apply when you set a parameter with a numeric value outside of its valid range:
  • If the value is greater than the allowable range, the maximum allowable value is used.
  • If the value is less than the allowable range, the minimum allowable value is used.
  • If you insert invalid parameter values into the configuration file, the value is ignored and the default value is used. Examples of invalid parameter values include enumerated values that do not match values defined in the UC software, numeric parameters set to non-numeric values, string parameters whose value is too long or short, and null strings in numeric fields. Invalid values are logged in the phone's log files.
You must use the appropriate XML code for special characters in a configuration file:
  • & as &
  • ” as "
  • ' as '
  • < as &lt;
  • > as &gt;
  • random numbers as &0x12;