Before You Begin
Polycom, Inc.
5
To find all Polycom partner solutions, see
Strategic Global Partner Solutions
The Polycom
Community
gives you access to the latest developer and support information. Participate in
discussion forums to share ideas and solve problems with your colleagues. To register with the Polycom
Community, simply create a Polycom Online account. When logged in, you can access Polycom support
personnel and participate in developer and support forums to find the latest information on hardware,
software, and partner solutions topics.
Documentation Feedback
We welcome your feedback to improve the quality of Polycom documentation.
You can email
for any important queries or suggestions related to this
documentation.
Notational Conventions
This guide provides device configuration parameters and their values in the following formats:
●
Canonical fashion
●
Literal fashion
Both notational conventions point to the same parameters, but their appearances are different.
The canonical fashion simplifies locating parameters on the device’s native web portal or on OBiTALK at
The literal fashion is required when provisioning or writing OBIPhoneXML apps.
Canonical Fashion
This example shows the format of the canonical fashion.
●
Parameter Group Name
::
ParameterName
=
Parameter Value {replace with actual
value}
The
Parameter Group Name
is the heading of the parameter group on the left side panel of the device local
configuration or OBiTALK Configuration web page. This string may contain spaces. When a group heading
has more than one level, each level is separated with a –, such as:
●
Services Providers - ITSP Profile A – SIP
:
The
ParameterName
is the name of the parameter as shown on the web page and MUST NOT CONTAIN
ANY SPACES.
Parameter Group Name
and
ParameterName
are separated by two colons (::),as shown
in the first example above.
The
Parameter Value
is the literal value to assign to the named parameter and may contain spaces. You
can omit
Parameter Group Name
or its top-level headings when the context is clear. For example:
●
SP1 Service
::
AuthUserName
=
4082224312
●
ITSP Profile A - SIP
::
ProxyServer
=
sip.myserviceprovider.com
