polycom realpresence resource manager system, version 8.0 · polycom® realpresence® resource...

1

Release Notes

Polycom® RealPresence® Resource Manager System, Version 8.0.1

Polycom is pleased to announce this release of the Polycom RealPresence Resource Manager system. These release notes describe this release.

Contents What’s New in this Release

About the RealPresence Resource Manager System

Software Version History

System Parameters

Localization Information

Installation and Upgrade Information

Web Interface System Requirements

Products Tested With This Release

Resolved Issues

Known Issues

Where to Get the Latest Product Information

8.0.1 | May 2014 | 3725-72100-001E1

RealPresence Resource Manager System Release Notes

2

What’s New in this ReleaseThe RealPresence Resource Manager system offers the following bug fixes and enhancements.

Flexible Guestbook Entries

Documentation Corrections

Resolved Issues

Flexible Guestbook EntriesWhen entering a guest in the guest book, now only the First Name, E-mail Address and Location are required fields for guest information.

Documentation CorrectionsThe RealPresence Resource Manager System Operations Guide incorrectly describes the support for TANDBERG endpoints. The below information correctly describes Polycom’s support for the following TANDBERG endpoints.

Endpoint Type Glo

bal

Ad

dre

ss B

oo

k A

cce

ss

Dyn

amic

Ma

nag

emen

ta

a. Dynamic Management and Scheduled Management are mutually exclusive functionality. Third-party endpoints cannot be dynamically managed.

Sch

ed

ule

d M

ana

gem

enta

Sch

ed

ulin

g (

Dia

l In

on

ly)c

c. Scheduling (Dial In Only) and Scheduling (Dial In and Dial Out) are presented as mutually exclusive functionality.

Sch

ed

ulin

g (

Dia

l in

an

d D

ial o

ut)

b

Mo

nit

ori

ng

(S

tan

dar

d)d

d. Standard RealPresence Resource Manager monitoring does not involve using SNMP. It includes endpoint monitoring (online/offline status) and alerts.

Co

mm

and

an

d C

on

tro

le

e. Command and Control means the RealPresence Resource Manager system can send a Reboot command, and the endpoint can receive and act on the command.

Rep

ort

s fo

r IP

Cal

lsf

Rep

ort

s fo

r IS

DN

Cal

lse

TANDBERG T150 MXP Y N Y N Y Y Y Y N

TANDBERG 95 MXP Y N Y N Y Y Y Y Y

TANDBERG C Series and Other TANDBERG Models

Y N Yb

b. You cannot schedule a software update for a TANDBERG C Series if it requires an upgrade key.

N Y Y Y Y N


3

About the RealPresence Resource Manager SystemThe RealPresence Resource Manager system is a key element of the Polycom RealPresence Platform. The RealPresence Resource Manager system takes on most of the functions previously handled by its predecessor the Polycom CMA system.

The RealPresence Resource Manager system offers the following new features. Each of these features is discussed in more detail in the following sections.

Integration with a Polycom DMA™ 7000 System

Multi-tenancy and the Areas Functionality

Scheduling Pooled or Anytime Conferences

REST-based APIs

Session Border Controller Support

Billing Interface

Unsupported Polycom CMA System Functions

Additional System Information

SNMP Trap Support

Polycom RealPresence Mobile and RealPresence Desktop Support

Integration with a Polycom DMA™ 7000 SystemThe RealPresence Resource Manager system does not include H.323 gatekeeper functionality. Instead, the RealPresence Resource Manager system is your centralized user, conference, room, and device manager, while an integrated Polycom Distributed Media Application™ (DMA 7000) system acts as the H.323 gatekeeper, SIP registrar, SIP proxy, and SIP to H.323 gateway for your network.

In this configuration, the DMA system is also the virtualized conference manager—managing call control, bandwidth, priority-based routing, and your pool of MCU resources. As such, the DMA system supports numerous dial options including flat dial plan, MCU prefix dialing, ISDN gateway dialing, prefix dialing and Polycom One Dial.

The RealPresence Resource Manager system can only integrate with a single DMA 7000 system, be it in a cluster or supercluster system configuration.

f. Reports for IP Calls are generated as part of standard gatekeeper functionality. Reports for ISDN Calls are additional system functionality. Endpoints that aren't registered with the gatekeeper or ISDN calls send an alert to the device management function to record CDR information. Some legacy endpoints do not send this alert so the CDRs are not written.


4

MCU Systems Registered with the DMA System

With this release, you can schedule conferences on MCUs that are directly registered with the RealPresence Resource Manager system (direct conferences) as well as resources that are registered to the DMA system (pooled conferences).

You cannot have the same MCU managed by both systems. It must either be managed by the DMA system or managed by the RealPresence Resource Manager system. MCUS that are managed the RealPresence Resource Manager system should not be added to the DMA system’s conferencing resources.

Multi-tenancy and the Areas FunctionalityThe RealPresence Resource Manager system supports multi-tenancy with its Areas feature. Multi-tenancy allows you to use the RealPresence Resource Manager system to service multiple customers (tenants), internal or external. Each area serves a tenant by partitioning off a collection of resources including users, associated endpoints, MCU resources and other network devices.

As the RealPresence Resource Manager system administrator, you may delegate administration and conferencing duties for areas to users within each areas or to a set of super users who are allowed to view and manage all areas.

You may choose to have an area scheduler or area operator for each respective tenant or area or

You can limit area administration tasks to users specifically allowed to manage that area.

For example, in an enterprise deployment, you can divide up users and resources according to department and then delegate video conferencing duties to users within that area. This allows the system administration duties to remain with a specialized video IT department, while video conference scheduling can be delegated to users within specific areas.

Areas also allow you to run area-specific reports on how specific departments within the enterprise are utilizing video conferencing.

Scheduling Pooled or Anytime ConferencesThe RealPresence Resource Manager system manages the following conference types:

Pooled - Conferences hosted on MCUs that are managed by the DMA system as part of the system’s MCU pools. These are ad hoc conferences that do not reserve MCU resources, but instead pull from the resource pool.

Anytime conferences - Conferences are system-managed, ad hoc, dial out conferences. They do not have designated start and end times. Once an Anytime conference is configured by your administrator, conferences can be started at any time by authorized participants.

REST-based APIs The RealPresence Resource Manager system provides functional Application Programming Interfaces (APIs) for:

Scheduling

Directory support


5

User management

Conference control and management

These APIs use an XML encoding over HTTPS transport. The API adheres to a Representational State Transfer (REST) architecture. For more information, see the Polycom RealPresence Platform Application Programming Interface (API) Developer Guide.

These APIs are licensed separately.

Session Border Controller SupportThe RealPresence Resource Manager system can dynamically manage (provision, upgrade, and manage) select remote endpoints through critical session border controller functions to enable high quality interactive communication — voice, video, and multimedia sessions — across IP network borders.

The Polycom® RealPresence® Access Director™ enables users within and beyond the firewall to securely access video services – whether you are at home, in the office or on the go. A software based edge server – RealPresence Access Director – securely routes communications, management and content through firewalls without requiring additional client hardware or software.

For more information about this solution, see Deploying Polycom® Unified Communications in an Polycom RealPresence® Access Director™ System Environment.

Acme Packet® Net-Net ESD secures the borders to the service provider IP network, the private VPN that connects major enterprise or contact center sites, and the Internet. This allows for secure communication between remote office and remote users, as well as users and organizations outside of the enterprise.

For more information about this solution, see Deploying Polycom® Unified Communications in an Acme Packet® Net-Net Enterprise Session Director Environment.

Billing InterfaceThe RealPresence Resource Manager system also provides a billing interface that will allow the enterprise or service provider to detail “per call” information downloadable from the system as a CDR Report.

Unsupported Polycom CMA System FunctionsWhile the RealPresence Resource Manager system takes on most of the functions previously handled by its predecessor the CMA system, the following list describes the CMA system functions it does not support:

Scheduling Plugin Support

This system release does not support the Polycom® Scheduling Plugin for Microsoft® Outlook® or the Polycom® Scheduling Plugin for IBM® Lotus® Notes®. Instead, the system provides a scheduling API which will allow integrators to implement scheduling applications.

Gatekeeper functionality

The system does not include H.323 gatekeeper functionality. Instead, the system will integrate with other standard H.323 gatekeepers like the Polycom DMA 7000 system for gatekeeper, registration and call control.


6

External Database

The system does not use or support an external database. The RealPresence Resource Manager system incorporates an internal database that does not need to be managed. System backups now automatically include all database data.

Legacy Device Support

This system release does not include support for the following “end-of-life” Polycom endpoints:

Polycom PVX systems

Polycom iPower systems

Polycom VSX endpoint systems are supported, but the RealPresence Resource Manager system does not manage scheduled software updates for them.

Cascaded conferencing support

The RealPresence Resource Manager system supports cascading conferences only on the Polycom MGC system. If the RealPresence Resource Manager system is a migrated CMA system, cascading conferences scheduled on the CMA system for an RMX system are deleted from the system. Cascading conferences scheduled for Polycom MGC system remain on the system.

Lifesize 220 Express and Team

This Lifesize Express and Lifesize 220 Team endpoints have not been tested with this release. The RealPresence Resource Manager system does not support Lifesize 220 Express and Lifesize 220 Team endpoints.

Additional System InformationThe following sections describe additional information about this RealPresence Resource Manager system release.

Support of Multiple Provisioning Servers

Create an SRV record to point to the RealPresence Resource Manager system provisioning service that endpoints can use to auto discover the system for dynamic provisioning.

Two or more provisioning servers may co-reside on a network; however only one may be used for DNS-based discovery of provisioning services.

If more than one provisioning server is used within an environment, there is no knowledge or coordination between the provisioning servers. This includes, but is not limited to:

No shared directory services

No shared management or provisioning services

No shared scheduling

No shared licenses


7

SNMP Trap SupportThe RealPresence Resource Manager system includes an SNMP agent. It translates local system information and makes it available to your SNMP management system.

SNMP traps allow the RealPresence Resource Manager system to notify the SNMP management system of significant events by sending out an unsolicited SNMP message. In this release, RealPresence Resource Manager system supports the following SNMP event traps.

mcuDownAlert,

dbConnectionDownAlert,

ldapConnectionDownAlert,

cmaFailoverAlert,

licenseCapacityAlert,

licenseExpirationAlert

redundantServerDownAlert

ldapSystemAccountPasswordFailed

bandwidthUsedSiteAlert

bandwidthUsedSubnetAlert

bandwidthUsedSiteLinkAlert

auditUsageThresholdExceeded

alertDiskSpaceUsageExceeded

certificateExpirationWarning

certificateExpiredWarning

cpuUsageExceededAlert

memoryUsageExceededAlert

idsFloodDetected

dmaDownAlert

SNMP traps not listed here may be included in the RealPresence Resource Manager MIB but are not supported and have no information.


8

Software Version History

Table 5-1 Software Version History

Software Version Release Date Features

v7.0 August 2012 Runs on Linux-based operating system. Integration with Polycom DMA system. Full multi-tenancy support.

v.7.1 December 2012 Support for RealPresence Group Series endpoints.

Dynamically-provisioned system and E.164 naming schemes for endpoints.

Access Control Lists for tighter dynamic-management.

Support for RealPresence Access Director systems.

v7.1.1 April 2013 Associate billing codes with conferences.

Support for RealPresence Collaboration Server 800s.

v8.0 August 2013 Rule-based dynamic provisioning.

Re-organization of menu system.

Direct import and linking to MCU conference profiles.

Support for SVC conferences.

Integration with a Polycom DMA supercluster.

Ability to auto-generate SIP URIs for dynamically-managed endpoints.

Increased security options.

Support for IPv6 networks.

Support for Polycom MGC systems.

Performance enhancements.

Better license reclamation for Polycom soft endpoints.

v8.0.1 October 2013 Resolved some known issues.


9

System Parameters The RealPresence Resource Manager system operates within the following system parameters:

Users—250000

Groups—1000

Areas—no limit

Devices—limited to maximum number of device licenses (50000)

Global Address Book entries—limited to maximum number of device licenses

Room entries—no limit, but if the system has more than 500 room entries, it could experience user interface performance issues.

Site entries—supports up to 500 total sites

Subnets—supports up to 5000 total subnets

Site links—no limit

Maximum number of concurrent endpoint software upgrade: 80

Maximum number of licensed endpoints: 50000.

Max number concurrent calls that can be monitored—no limit

Max number directory entries—no limit

Max number of registered DMA systems (or DMA superclusters)—1

Maximum number of registered MCUs—no limit

Maximum text message length that can be sent to a hard endpoint is 100 characters.

Maximum number of provisioning profiles is 2000.

Maximum number of provisioning rules is 2000.

Maximum password age for local user is 180 days when this feature is enabled.

Maximum displayed users in the Users page is 500.

Maximum number of tiers in Address book: 3

Maximum Guest book entry: 500

Maximum 50 user GUI login sessions per system and 10 sessions per user.

Localization InformationThis version of the RealPresence Resource Manager system user interface (UI) is only available in the following languages: English, French, German, International Spanish, Japanese, Korean, Simplified Chinese, Traditional Chinese, Portuguese, and Russian.

Localization of the UI is not complete in some areas.


10

Installation and Upgrade Information Your RealPresence Resource Manager system must be running v8.0 in order to apply the upgrade software for v8.0.1.

Only RealPresence Resource Manager systems running version 7.1.x AND that have applied the pre-upgrade patch can be migrated to version 8.0. You must apply a pre-upgrade patch before you can migrate.

Existing Polycom CMA system customers can migrate to RealPresence Resource Manager with the help of Polycom Global Services. Polycom only supports migrating from CMA system v6.2 to RealPresence Resource Manager v8.0.

Polycom CMA system customers running versions previous to v6.2 need to upgrade to v6.2 before they can migrate their systems to RealPresence Resource Manager.

Polycom supports the following upgrade and migration paths for the RealPresence Resource Manager system.l

Migrating to v8.0

You can download the RealPresence Resource Manager v7.1.x Pre-Upgrade patch from the RealPresence Resource Manager system support site: http://support.polycom.com/PolycomService/support/us/support/network/management_scheduling/realpresence_resource_manager.html

After applying the RealPresence Resource Manager system 7.1.x Pre-Upgrade patch, please request the RealPresence Resource Manager system v8.0 DVD by clicking http://response.polycom.com/05-DR-C-RPRM-System-v8.0Software-Aug2013 and submitting the order information to Polycom.

Version Number Upgrade/Migration StepsUse the Following Documentation

RealPresence Resource Manager system v8.0

1 Upgrade system to v8.0.1 RealPresence Resource Manager System Upgrade Guide v8.0.1

RealPresence Resource Manager system v7.1.x 1 Apply v7.1.x pre-upgrade patch

2 Migrate system to v8.0

3 Upgrade system to v8.0.1

RealPresence Resource Manager System Upgrade Guide v8.0.1 and v8.0

RealPresence Resource Manager system v7.x 1 Upgrade to v7.1.x

2 Apply v7.1.x pre-upgrade patch

3 Migrate system to v8.0

4 Upgrade system to v8.0.1

RealPresence Resource Manager System Upgrade Guide v8.0.1 and v8.0

http://support.polycom.com/PolycomService/support/us/support/network/management_scheduling/realpresence_resource_manager.html

http://response.polycom.com/05-DR-C-RPRM-System-v8.0Software-Aug2013


11

Web Interface System Requirements The following table describes the requirements for the RealPresence Resource Manager system web interface.

Note that you cannot use Mozilla Firefox and Apple Safari to upload files to the RealPresence Resource Manager system. It is not supported. To upload files, use Google Chrome or Internet Explorer.

You should always check the Polycom support site (http://support.polycom.com) to verify that you have the latest software release and release information for the product.

Product Versions

Microsoft Internet Explorer®

Mozilla Firefox®

Apple Safari

Google Chrome

8.0, 9.0 or 10.0

11 or higher

5.1.6 or 5.1.7

17 or higher

Adobe Flash Player 9.x or 10.x

http//support.polycom.com


12

Products Tested With This ReleasePolycom RealPresence Resource Manager systems are tested extensively with a wide range of products. The following list is not a complete inventory of compatible equipment. It simply indicates the products that have been tested for compatibility this release.

You are encouraged to upgrade all your Polycom systems with the latest software before contacting Polycom support to ensure the issue has not already been addressed by vendor software updates. Go to http://support.polycom.com/PolycomService/support/us/support/service_policies.html to find the current Polycom Supported Products matrix.

Product Tested Versions

Polycom Video Endpoints

Polycom HDX systems v3.1.1, v3.1.2

Polycom RealPresence Group Series (300, 500, 550, and 700)

v4.0.2, v4.1.1

CMA Desktop (Windows and Mac) 5.2.5

RealPresence Mobile v2.3, v3.0

RealPresence Desktop (Windows and Mac) v2.3, v3.0

Polycom VVX 1500 v3.3.2

Polycom VSX 7000 v9.0.6

Network Devices

RealPresence Collaboration Server 800s v8.0, v8.1a

Polycom RMX system (1500/2000/4000) v7.8, v8.1b

Polycom MGC system v9.04

Polycom DMA 7000 v5.2.2, v6.0.2

RealPresence Access Director v2.1.1, v3.0

Polycom VBP-ST v11.2.16

Third Party Products

Acme Packet Net-Net Enterprise Session Director 6.3

LifeSize 200 Series 4.7.22

Tandberg MXP Series F9.3.1

http://support.polycom.com/PolycomService/support/us/support/service_policies.html

http://support.polycom.com/PolycomService/support/us/support/service_policies.html


13

Polycom RealPresence Mobile and RealPresence Desktop SupportThe RealPresence Resource Manager system supports authentication, management, and CDR generation for RealPresence Mobile and RealPresence Desktop clients.

Licenses for the RealPresence Mobile and RealPresence Desktop clients are managed in the same pool as CMA Desktop clients.

The RealPresence Resource Manager system supports dynamic provisioning for RealPresence Mobile and RealPresence Desktop clients.

Dynamic software updates are supported for RealPresence Desktop and CMA Desktop clients.

The RealPresence Mobile clients as well as the RealPresence Desktop clients do not support presence when registered to the RealPresence Resource Manager system.

Resolved IssuesThe following table lists the resolved issues in this RealPresence Resource Manager system release.

Tandberg C20/C90 6.1.2

Tandberg T150 L6.1

a. The RealPresence Resource Manager system reports port numbers based on resource usage for CIF calls. Version 8.1 and later Polycom MCUs report port numbers based on resource usage for HD720p30 calls. In general, 3 CIF = 1 HD720p30, but it varies depending on bridge/card type and other factors.

b. The RealPresence Resource Manager system reports port numbers based on resource usage for CIF calls. Version 8.1 and later Polycom MCUs report port numbers based on resource usage for HD720p30 calls. In general, 3 CIF = 1 HD720p30, but it varies depending on bridge/card type and other factors.

Issue Number Description

XMA-5206 RealPresence Resource Manager could not get a list of endpoints from the RealPresence DMA system if the DMA system was deployed as a supercluster.

XMA-5019 When monitoring an ongoing pooled conference, you cannot delete a SIP participant and add it back to the conference. This happens when the conference is SIP only.

XMA-5015 When restoring a RealPresence Resource Manager system from a system backup file, there is no indication when the server reboots.

XMA-5014 Access Control List does not initialize after you delete an enterprise directory that was associated with a list.

XMA-5002 When you create an RPAD server provisioning profile, do not set the minimum value for the heartbeat, server status, and provisioning interval to be 0.

Product Tested Versions

https://jira.polycom.com:8443/browse/XMA-5019





14

Known IssuesThe following table lists the known issues in this RealPresence Resource Manager system release.

XMA-4992 When updating a DSR in the DSR API, the deviceType is not a mandatory field in the yang model.

XMA-4970 When the RealPresence Resource Manager system is integrated with the DMA system, site-related report information may be unavailable.

XMA-4904 The RealPresence Resource Manager may have show two devices with the same alias and IP.

XMA-4903 The RealPresence Resource Manager system allows the user to assign two Bundled Provisioning Profiles with the same name.

Issue Number DescriptionRecommended Workaround

XMA-5273 ITP functions are unsupported, but still show up in the system. Disregard all mention of ITP support.

XMA-5227 When the HDX web access port is set to something higher than 1025, the device displays in RealPresence Resource Manager as “device not responding.'

XMA-5168 When monitoring an ad-hoc conference that is scheduled on a Polycom MGC and one of the conference participants is removed from the conference using the monitor view of the Polycom MGC system, the RealPresence Resource Manager does not show that the participant has been removed. Instead the participant is shown as disconnected.

XMA-5166 You cannot schedule a software update for a Cisco endpoint, if the update requires a software key.

XMA-5123 When you add a participant, (user, room or guest) to an ongoing SVC-only conference, you cannot select Dial-In.

XMA-5109 If you choose to upload certificates after completing first time set up, you must reboot your RealPresence Resource Manager system before you can modify OSCP settings. You cannot select "Continue Working".

XMA-5094 If you change the conference layout during an ongoing conference call, you cannot change it back to Auto.

XMA-5082 You cannot create a provisioning rule based on a room ID.

Issue Number Description












15

XMA-5078 You cannot add ISDN participants to a direct conference if you have edited the respective RMX system's ISDN video number.

XMA-5076 When you schedule ISDN participants in conferences with a prefix, the prefix is not added and the participant appears twice in the conference monitoring screen.

XMA-5059 You cannot provision a Group system if the username used for authentication starts with a space.

XMA-5031 A CMA Desktop user that is also an Active Directory user cannot add another Active Directory user as a CMA Desktop favorite.

Ensure that “Allow endpoint directories for local users to include enterprise directory user and group information is checked.

XMA-5028 Audio conferences are still allowed even when the RealPresence Resource Manager system admin unchecks the “Allow audio-only conferences” option.

XMA-5026 If the RealPresence Resource Manager has unselected “Allow non-dynamically managed endpoints”, endpoints registered to the DMA system are still allowed.

XMA-5022 You cannot create a provisioning rule with a site condition of the Default Internet/VPN site.

XMA-5019 If you delete a SIP participant from an ongoing scheduled point-to-point conference, it cannot rejoin the conference after being removed.

XMA-5017 On rare occasions, the CMA Desktop client may fail to login and authenticate with the RealPresence Resource Manager.

Re-try the login immediately.

Alternatively, you can update to RealPresence Mobile or RealPresence Desktop clients (chat and presence are not supported).






16

XMA-5015 When you migrate a Polycom CMA system to RealPresence Resource Manager, sometimes there is no indication that system restore is finished.

XMA-5013 After migrating a CMA 5000 system (v6.2x) to RealPresence Resource Manager system, you cannot perform a scheduled software update for a LifeSize endpoint.

XMA-5012 On rare occasions, the CMA Desktop client may to receive an invitation for an added contact.

Re-try sending the contact immediately.

Alternatively, you can update to RealPresence Mobile or RealPresence Desktop clients (chat and presence are not supported).

XMA-5002 When you create an RPAD server provisioning profile, do not set the minimum value for the heartbeat, server status, and provisioning interval to be 0.

Don't set the value for the heartbeat, server status, and provisioning interval to be 0.

XMA-4992 When updating a dial string reservation using the API, the deviceType is not a mandatory field in the yang model. If you don’t enter a deviceType, the deviceType will be changed to Other.

When updating a dial string reservation via DSR API, ensure the deviceType field is accurate.

XMA-4989 When “alerts” is selected in the Filter drop-down menu in Endpoint > Monitor View, a warning message pops up if no endpoint applies to the filter.

None.

XMA-4986 When viewing Direct Conference templates, you cannot filter by routing name.

None.

XMA-4970 When the RealPresence Resource Manager system is integrated with the DMA system, site-related report information may be unavailable.

None.








17

XMA-4956 The RealPresence Resource Manager dashboard incorrectly mentions the DMA status as DMAs. The RealPresence Resource Manager supports integration with only one DMA system.

None.

XMA-4954 Site-Link Statistics information may be inaccurate. None.

XMA-4949 You cannot provision a security banner for dynamically-managed endpoints.

None.

XMA-4946 The RealPresence Resource Manager system API returns an error code 400 instead of 409 when you attempt to create a user without the user name.

None.

XMA-4944 You cannot set default passwords for LifeSize endpoints with the Endpoint Management Settings feature.

None.

XMA-4926 When areas are enabled, the endpoint inventory report includes site information for endpoints within sites that the user cannot manage.

None.

XMA-4923 In some circumstances, the RealPresence Resource Manager system shows an inaccurate “Conference Type Report” due to the different in time zones between system components.

None.

XMA-4918 A scheduler cannot schedule recurring pooled conferences with a start time of “now”.

None

XMA-4914 In some circumstances, some endpoints appear in Polycom VBP system list.

None.

XMA-4904 The RealPresence Resource Manager may show two devices with the same alias and IP.

None.

XMA-4903 The RealPresence Resource Manager system allows the user to assign two Bundled Provisioning Profiles with the same name.

None.












18

XMA-4901 When you export an endpoint inventory report, area information is not included unless you have the area administrator role.

None.

XMA-4896 When filtering Alerts, you can only filter on the first page of endpoints.

None.

XMA-4893 When you includes guests in Anytime conferences, the Conference monitoring screen sometimes displays them as external participants.

None.

XMA-4890 For pooled conferences, some dynamically-managed HDX systems do not display correctly in the Conference monitoring screen.

None.

XMA-4870 You cannot add an ISDN guest to an ongoing conference. None.

XMA-4869 If you extend the duration of a conference, it may not end when all endpoints disconnect.

None.

XMA-4868 The icons for guest and room in the conferencing monitoring screen are not correct.

XMA-4850 Users with the area operator role cannot use the Favorites menu. None.

XMA-4846 When the RealPresence Resource Manager system is configured for redundancy and supports more than 20,000 endpoints, it may take up to 60 seconds to log into the system.

None.

XMA-4835 During an upgrade or server restart, it still looks like the RealPresence Resource Manager system maintains connections to endpoints. It does not.

None.












19

XMA-4834 Users with the area administrator role can incorrectly assign DMA pool orders to areas. This is not supported.

None.

XMA-4832 When you add a contact to the CMA Desktop, the contact name will not display if the contact name was created with a space. For example, “contact 10" displays as “ “.

None.

XMA-4831 Anytime conferences do not support having a SIP user being the conference owner. Dial out participants will not be dialed if the conference owner is a SIP user.

None.

XMA-4803 In the Conference Monitor page, the online participants in the Conference Status pane is incorrect.

XMA-4798 When you schedule guests for anytime conferences, they are incorrectly listed as external participants.

None.

XMA-4732 When you integrate with a DMA system, some endpoints registered to the DMA erroneously display as VBP systems in the VBP monitoring screen.

None.

XMA-4431 In order to assign an Access Control List to a imported user group, you must have also imported all parent groups.

XMA-4212 For adhoc conferences, the RealPresence Resource Manager system does not display the media type used.

None.









20

XMA-4197 Non-dynamically managed endpoints dialing in from a Polycom VBP system are not displayed properly in the conference monitoring screen.

None.

XMA-4186 The RealPresence Resource Manager system displays an additional participant in a point-to-point call with an endpoint dialing in through a Polycom VBP.

None.

XMA-3459 During an ad hoc conference between two ISDN endpoints, an additional participant is added which changes the conference type.

None.

XMA-3450 When you schedule a direct conference between two ISDN endpoints, an additional external participant displays in the conference monitoring page.

None.

XMA-4969 The filters on the Endpoint Usage Report are sometimes incorrect and display non-dynamically managed endpoints when filtering for dynamically-managed endpoints.

None.

XMA-4936 When configuring remote alerts profiles, the Alert By Network option should read Alert By Network Device.

None.

XMA-4801 In the Conference Monitoring screen, the multipoint bridge icon incorrectly displays in the Bridge column.

None.










21

Where to Get the Latest Product InformationTo view the latest Polycom product documentation, visit the Support page of the Polycom website at http://support.polycom.com

XMA-4759 When paging through a list of endpoints on the Endpoint Monitoring page, the user interface is not clear. The number of available pages to scroll through 1/2 pages should be 1/ 2 pages.

None.

XMA-4696 Although the RealPresence Resource Manager supports only 500 sites, the system mistakenly allows you to add more than that. Adding more than 500 sites is not supported.

None.




© 2013 Polycom, Inc. All rights reserved.

Polycom, Inc. 6001 America Center Drive San Jose CA 95002 USA

No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. Under the law, reproducing includes translating into another language or format.

As between the parties, Polycom, Inc., retains title to and ownership of all proprietary rights with respect to the software contained within its products. The software is protected by United States copyright laws and international treaty provision. Therefore, you must treat the software like any other copyrighted material (e.g., a book or sound recording).

Every effort has been made to ensure that the information in this manual is accurate. Polycom, Inc., is not responsible for printing or clerical errors. Information in this document is subject to change without notice.

22

Trademark Information

POLYCOM® and the names and marks associated with Polycom's products are trademarks and/or service marks of Polycom, Inc., and are registered and/or common law marks in the United States and various other countries.

All other trademarks are the property of their respective owners.

Java is a registered trademark of Oracle America, Inc., and/or its affiliates.

Patent Information The accompanying product may be protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc.

End User License Agreement Use of this software constitutes acceptance of the terms and conditions of the Polycom RealPresence Resource Manager system end-user license agreement (EULA).

The EULA for this product is available on the Polycom Support page for the RealPresence Resource Manager system.

polycom realpresence resource manager system, version 8.0 · polycom® realpresence® resource...

Documents