DMA OperationsGuide Licenses
70 Polycom, Inc.

See also:

“Local Cluster Configuration” on page 63

“Local Cluster Configuration Procedures” on page82

Licenses

The Polycom DMA system is licensed for the number of concurrent calls it can

handle and optionally for API access. See “License the Polycom DMA System”

on page 26 for more information about licensing.

The following table describes the fields on the Licenses page.

Table 4-3 Fields on the Time Settings page
Field Description
System time zone Time zone in which the system is located. We strongly
recommend selecting the time zone of a specific
geographic location (such as America/Denver), not one
of the generic GMT offsets (such as GMT+07 POSIX).
If you really want to use a generic GMT offset (for
instance, to prevent automatic daylight saving time
adjustments), note that they use the Linux/Posix
convention of specifying how many hours ahead of or
behind local time GMT is. Thus, the generic equivalent
of America/Denver (UTC-07:00) is GMT+07, not
GMT-07.
Manually set system
time We don’t recommend setting time and date manually.
NTP Servers Specify up to three time servers for maintaining system
time (we recommend three). Enter IP addresses or fully
qualified domain names.
Table 4-4 Fields on the Licenses page
Field Description
Active License
Licensed calls The maximum number of concurrent calls that the
license enables.
Licensed capabilities Currently, the only separately licensed capability is
access to the RealPresence Platform API.
Note: An API license isn't required in order for a
Polycom RealPresence Resource Manager system to
access the API. It's only needed for a client application
you or a third party develop.