RELEASE NOTES Version 8.7.1 RealPresence Collaboration ...Version 8.7.1 - New Features List Polycom,...

Version 8.7.1 | October 2016 | 3725-74103-000FRELEASE NOTES

RealPresence® Collaboration Server

1800/2000/4000/Virtual Edition

Copyright© 2016, Polycom, Inc. All rights reserved. No part of this document may be reproduced, translated into another language or format, or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc.

6001 America Center DriveSan Jose, CA 95002USA

Polycom®, the Polycom logo and the names and marks associated with Polycom 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 property of their respective owners. No portion hereof may be reproduced or transmitted in any form or by any means, for any purpose other than the recipient's personal use, without the express written permission of Polycom.

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

End User License Agreement By installing, copying, or otherwise using this product, you acknowledge that you have read, understand and agree to be bound by the terms and conditions of the End User License Agreement for this product. The EULA for this product is available on the Polycom Support page for the product.

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.

Open Source Software Used in this Product This product may contain open source software. You may receive the open source software from Polycom up to three (3) years after the distribution date of the applicable product or software at a charge not greater than the cost to Polycom of shipping or distributing the software to you.

Disclaimer While Polycom uses reasonable efforts to include accurate and up-to-date information in this document, Polycom makes no warranties or representations as to its accuracy. Polycom assumes no liability or responsibility for any typographical or other errors or omissions in the content of this document.

Limitation of Liability Polycom and/or its respective suppliers make no representations about the suitability of the information contained in this document for any purpose. Information is provided "as is" without warranty of any kind and is subject to change without notice. The entire risk arising out of its use remains with the recipient. In no event shall Polycom and/or its respective suppliers be liable for any direct, consequential, incidental, special, punitive or other damages whatsoever (including without limitation, damages for loss of business profits, business interruption, or loss of business information), even if Polycom has been advised of the possibility of such damages.

Customer Feedback We are striving to improve our documentation quality and we appreciate your feedback. Email your opinions and comments to [email protected].

Polycom Support Visit the Polycom Support Center for End User License Agreements, software downloads, product documents, product licenses, troubleshooting tips, service requests, and more.

mailto:[email protected]

http://support.polycom.com/

Polycom, Inc. 1

Content

Version 8.7.1 - New Features List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Products Tested with This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Conferencing Options in Collaboration Server Virtual Edition . . . . . . . . . . . . . 13

Polycom Solution Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Resources and Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Virtual Edition Host Server Hardware Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17RealPresence Collaboration Server, Virtual Edition Hardware Profile . . . . . . . . . . . . . . . . . . 17

CPU Reservations for Licenses Purchased . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Soft Blade Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

RMX Web Client and RMX Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Windows 7™ Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Internet Explorer 8 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Version 8.7.1 - Upgrade Package Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Collaboration Servers 1800/2000/4000 - Software Upgrade Procedures . . . . . . 27Upgrade Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Collaboration Server (RMX) 2000/4000 Hardware / Software Version Support . . . . . . . . 30

Safe Upgrade Paths to Version 8.7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Upgrading from Version 8.4 / 8.5 to 8.7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Additional/Optional System Considerations After Upgrade . . . . . . . . . . . . . . . . . . . . . . . . 35

Collaboration Server Virtual Edition - Software Upgrade Procedures . . . . . . . 37Upgrade Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Content

Polycom, Inc. 2

Upgrading to Version 8.7.1 from Version 8.5 and On . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Upgrading to Version 8.7.1 from a Version Earlier than 8.5 . . . . . . . . . . . . . . . . . . . . . . . 38

Version 8.7.1 Detailed Descriptions of New Features . . . . . . . . . . . . . . . . . . . . . 40Network and System Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Polycom® RealPresence Clariti™ Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

New VE Hosts and Increased Capacity Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Conferencing Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Personal Layout in Lecture Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Legacy Content in Multiple Content Transcoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Lock/Unlock Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Conference locking via XML API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

NoiseBlock™ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Override Mute Participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Polycom Labs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Lab Features Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Miscellaneous Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

NTLMv2 Support for LDAP Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Dynamic Bandwidth Adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Configure Timeout between End of Chairperson IVR message and First DTMF Key . . . 49

Skype for Business Related Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

RealConnect for Microsoft Office365 via Skype for Business . . . . . . . . . . . . . . . . . . . . . . 50

Panoramic Layout in Skype for Business . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Add Polycom Participants into Skype for Business Conference Roster . . . . . . . . . . . . . . 53

Skype for Business Audio/Video Participants Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Mute Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

RDP Content Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Main MCU and Soft Blades - What are They? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

MCU Operation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Modular MCU Implementation Aspects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Deployment of Soft Blades in a Modular MCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Soft Blade Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Modular MCU Components Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Monitoring Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

MMCU Impact on Participant Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Faults and Active Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

System Operation Description for Deployment and Monitoring . . . . . . . . . . . . . . . . . . . . 64

MMCU Components Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

IP Address Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Content

Polycom, Inc. 3

RDP Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

RealConnect Call Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Direct Call Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Common Behavior - RealConnect / Direct Call Modes . . . . . . . . . . . . . . . . . . . . . . . . 68

Enabling RDP Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Monitoring RDP Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Modular MCU Resource Consumption and Management . . . . . . . . . . . . . . . . . . . . . . . . 70

Resource Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Port Usage for Skype for Business Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Modular MCU Security Aspects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Modular MCU Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Logger Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Logging Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Logs at the Soft Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Filtering Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Modular MCU Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Virtual Edition MCU Upgrade Storage Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 80

Monitor Soft Blades Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Corrections and Known Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Corrections between Version 8.6 and Version 8.7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Known Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

RMX Web Client Installation - Troubleshooting Instructions . . . . . . . . . . . . . . 105Procedure 1: Ending all Internet Explorer Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Procedure 2: Deleting the Temporary Internet Files, Collaboration Server Cookie and Collab-oration Server Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Deleting the Temporary Internet Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Deleting the Collaboration Server Cookie . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Deleting the RMX/Collaboration Server ActiveX Object . . . . . . . . . . . . . . . . . . . . . . 110

Procedure 3: Managing Add-ons Collisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Procedure 4: Add the Collaboration Server to the Internet Explorer Trusted Sites List . 111

Procedure 5: Browser Hosting Controls (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Addenda to Release Notes - Polycom Lab Features . . . . . . . . . . . . . . . . . . . . . 115Addendum to Release Notes Polycom Lab Feature - Discussion Mode Layout . . . . . . . . . . 115

Description of Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

To Enable and Disable this Polycom Lab Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Content

Polycom, Inc. 4

Addendum to Release Notes Polycom Lab Feature - Exclude Inactive-Video Participants from Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119



Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Addendum to Release Notes Polycom Lab Feature - Using Video Clips for IVR Services . . 122



Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Addendum to Release Notes Polycom Lab Feature - Popup Site Name on Participant Join/Leave 126



Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Version 8.7.1 - New Features List

Polycom, Inc. 1


The following table lists the new features in Version 8.7.1.

Version 8.7.1 - New Features

Category Feature Name Description

Card Mode/Platform

MPMRx RMX1800

Virtual Edition

Network and System

System New VE Hosts and Increased Capacity Limitations

Additional Host platforms (Core types) can be used to deploy RealPresence Collaboration Server, Virtual Edition.

Collaboration Polycom® RealPresence Clariti™ Support

RealPresence Collaboration Server 1800/Virtual Edition is part of the RealPresence Clariti solution.


Polycom, Inc. 2

Conferencing

Conferencing Personal Layout in Lecture Mode

Personal Layout of the operator can be modified in conferences defined to operate in Lecture Mode.

Suppress conference entry tone for operators entering/leaving conferences

A new system flag to suppress entry/exit tone when the operator participant joins or leaves the conference.

Legacy Content in Multiple Content Transcoding

The Send Content to Legacy Endpoints option in the Conference Profile - Video Quality dialog, can be either checked or unchecked when using Multiple Content Resolutions (Content Transcoding).

Lock/Unlock conference Locking and unlocking conferences can now done via Web GUI, RMX Manager, and XML API, in addition to the previous DTMF code.

Override mute participants

Participants can unmute themselves regardless of the reason they were muted. Enable overriding mute participants function requires system flag setting.

Polycom Labs Polycom enables customers examining experimental features which might be later incorporated into the Collaboration Server.

Each of Polycom Lab features is described in a separate Addendum at the end of this document.



Card Mode/Platform

MPMRx RMX1800

Virtual Edition


Polycom, Inc. 3

Miscellaneous

Security NTLMv2 for LDAP connection

Support for NTLMv2 has been added for LDAP connections. The authentication protocol will be negotiated with preference given to NTLMv2.

WebRTC Dynamic Bandwidth Adaptation

RealPresence Collaboration Server, Virtual Edition can dynamically adapt the bandwidth for the MCU-bridged WebRTC conference according to the congestion level.

IVR Configure Timeout between End of Chairperson IVR message and First DTMF Key

Administrator can configure timeout between Chairperson IVR message and first input DTMF digit through system flag.



Card Mode/Platform

MPMRx RMX1800

Virtual Edition


Polycom, Inc. 4

Lync / Skype for Business

Skype for Business

Support Office365 federation

The Collaboration Server supports federation with Microsoft Office365.

This enables customers with Skype for Business, but no Polycom infrastructure, to invite into Skype for Business conferences non-Skype for Business users, where both user types may enjoy complete Skype for Business/Polycom experience, respectively.

Using Skype for Business panoramic layout to send more video streams from standard endpoints

Supports sending Panoramic Layout to AV MCU in a RealConnect Cascaded Conference.

Add Polycom participants in Skype for Business client conference roster

Including Polycom participants in the general Skype for Business participant list, thus enables Skype for Business users to see list of standard endpoints connected to the conference and disconnect them by Organizer

Skype for Business Audio and Video participants count

In the RealConnect conference, the total number of Audio/Video participants of Skype for Business and Non-Skype for Business can be counted in the Audio/Video participants indication in the conference layout.

Mute Audience In the AVMCU conference, originator of the conference can selectively to mute all participants or only mute Skype for Business participants by setting a system flag.



Card Mode/Platform

MPMRx RMX1800

Virtual Edition


Polycom, Inc. 5

Note: 8.7.1 will be the last release which will support Lync clients dialing directly into RMX meeting room (without RealPresence DMA). All future releases will support only RealPresence DMA VMRs for Lync Direct Dial use case

Soft Blades for RDP Content (Modular MCU)

Modular MCU Deployment and Monitoring

Deployment of soft blades, and changes in system monitoring.

RDP content Support for RDP content to Skype for Business endpoints in both direct and RealConnect calls.

Resource Management and Report

Resource consumption, and separating report for Main MCU and soft blades.

Security Aspects Open ports on Main MCU and on soft blades.

Logger Functionality Effects on Logger functionality in multiple machines environment.

Upgrading Upgrading Main MCU and soft blades.



Card Mode/Platform

MPMRx RMX1800

Virtual Edition

Products Tested with This Release

Polycom, Inc. 6


The RealPresence Collaboration Server (RMX) 1800/2000/4000/Virtual Edition system is tested extensively with a wide rang of products. The following list is not a complete inventory of compatible equipment. It indicates the products that have been tested for compatibility with this release.

Note: Supported Products

You are encouraged to upgrade all your Polycom systems with the latest software before contactingPolycom 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 findthe Current Polycom Interoperability Matrix.

Device RMX 2000/4000 RMX1800 Virtual Edition

Gatekeepers/Proxies

Polycom® RealPresence®

Resource Manager10.0 10.0 10.0


Collaboration Server (RMX®) Gateway

8.7.1 8.7.1 8.7.1


DMA® (Hyper-V)6.4


Resource Manager (Hyper-V)

10.0


Collaboration Server 800 (Hyper-V)

8.7.1


DMA® 70006.4 6.4 6.4


DMA®, Virtual Edition6.4 6.4 6.4


Web Suite Experience Portal

- - 2.1


Web Suite Services Portal- - 2.1

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


Polycom, Inc. 7

Polycom® RealPresence® Platform Director™

- - 2.0

Polycom VBP V11.2.13RC2 V11.2.13RC2 V11.2.13RC2


Access Director™

- - 4.2.3.1

Avaya Scopia® ECS Gatekeeper

8.3.0.103.0 8.3.0.103.0 8.3.0.103.0

Acme Packet 3820 ECZ7.3.0 Patch 2 (Build 75)

3820 ECZ7.3.0 Patch 2 (Build 75)

3820 ECZ7.3.0 Patch 2 (Build 75)

BroadWorks AS version Rel_21.sp1_1.551

AS version Rel_21.sp1_1.551

AS version Rel_21.sp1_1.551

Cisco TelePresence ISDN GW 3241

2.2 (1.111) 2.2 (1.111) 2.2 (1.111)

Cisco TelePresence MCU 4505

4.5 (1.85) 4.5 (1.85) 4.5 (1.85)

Cisco 5310 MCU 4.5 (1.85) 4.5 (1.85) 4.5 (1.85)

Microsoft Lync 2013 server 5.0.8308.956 5.0.8308.956 5.0.8308.956

Microsoft Skype for Business Server 2015 (volume license key installed)

6.0.9319.235, 6.0.9319.259

6.0.9319.235, 6.0.9319.259

6.0.9319.235, 6.0.9319.259

Microsoft Exchange 2013 CU12 15.00.1178.004 CU12 15.00.1178.004 CU12 15.00.1178.004

Sonus SBC - V05.00.02-R000

Recorders


Media Suite Hardware Edition

2.6 2.6 2.6


Media Suite Virtual Edition2.6 2.6 2.6

MCUs, Call Managers Network Devices and Add ins

Polycom®

ContentConnect™ Server1.5.1.185 1.5.1.185 1.5.1.185

Avaya Scopia® 100 Gateway P10

5.7.2.0.25 5.7.2.0.25 5.7.2.0.25

Avaya Aura® Session Manager

6.3.4.0.634014 6.3.4.0.634014 6.3.4.0.634014



Polycom, Inc. 8

Avaya Aura® Communication Manager

R016x.03.0.124.0 R016x.03.0.124.0 R016x.03.0.124.0

Cisco Unified Communications Manager

10.5.2 / 11.5 10.5.2 / 11.5 10.5.2

Cisco TelePresence Server 4.2(4.18) - -

Cisco TelePresence Video Communication Server

X8.7 X8.7 X8.7

IBM Sametime Server Sametime 9.0.1 version Sametime 9.0.1 version Sametime 9.0.1 version

Siemens OpenScape SBC V8R0.28.0 V8R0.28.0 V8R0.28.0

Siemens OpenScape Voice V8R0.34.4 V8R0.34.4 V8R0.34.4

Virtual Machines for RealPresence Collaboration Server VE Deployment

VMWare vSphere (vCenter) Client

N/A N/A 6.0

Endpoints

Polycom® HDX® 3.1.11 3.1.11 3.1.11

Polycom® Group Series 5.1.2, 6.0 5.1.2, 6.0 5.1.2, 6.0

Polycom® CMA® Desktop 6.2.5 6.2.5 6.2.5

Polycom® CMA® Desktop for MAC

6.2.5 6.2.5 6.2.5


Mobile for Apple® iOS3.6 3.6 3.6


Mobile for Android™3.6 3.6 3.6


Desktop for Windows®

3.6 3.6 3.6


Desktop for Mac®

3.6 3.6 3.6

Polycom RealPresence Debut

1.1.61447 1.1.61447 1.1.61447

Polycom RealPresence Trio

5.4.3.2007 5.4.3.2007 5.4.3.2007

Polycom® VVX® 1500 5.5.0 5.5.0 5.5.0

Polycom® VVX® 300/400 5.5.0 5.5.0 5.5.0

Polycom® VVX® 500/501 5.5.0 5.5.0 5.5.0

Polycom® VVX® 600/601 5.5.0 5.5.0 5.5.0



Polycom, Inc. 9

Polycom® Sound Point® IP 601

3.1.7 3.1.7 3.1.7

Polycom® SoundPoint® IP 650

4.0.7 4.0.7 4.0.7

Polycom® SoundStation® IP 7000

4.0.9 4.0.9 4.0.9

Polycom® Touch Control (for use with HDX)

OS1.17.0-38 / TP1.17.0-58

OS1.17.0-38 / TP1.17.0-58

OS1.17.0-38 / TP1.17.0-58

Polycom® Touch Control (for use with RealPresence Group Series)

OS6.0.0-903 / TP 6.0.0-280845

OS6.0.0-903 / TP 6.0.0-280845

OS6.0.0-903 / TP 6.0.0-280845

Polycom RealPresence Touch

OS 2.0.0-198 TP6.0.0-280928

OS 2.0.0-198 TP6.0.0-280928

OS 2.0.0-198 TP6.0.0-280928

Polycom® CMA® Desktop 5.2.6 5.2.6 5.2.6

Polycom® CX500 / CX600 4.0.7577.4487 4.0.7577.4487 4.0.7577.4487

Polycom CX5500 1.2.0 1.2.0 1.2.0

Polycom CX8000 1.00.11.066 1.00.11.066 1.00.11.066

Avaya Scopia® XT5000 8.3.2.534 8.3.2.534 8.3.2.534

Avaya Scopia® XT7000 8.3.2.225 8.3.2.225 8.3.2.225

Avaya one-X® Deskphone S3.171b S3.171b S3.171b

Avaya one-X® 1000 Communicator

6.2.10.03-FP10 6.2.10.03-FP10 6.2.10.03-FP10

Avaya 1000 Series Video Conferencing Systems

4.8.3(23) 4.8.3(23) 4.8.3(23)

Avaya Flare® Experience for Windows Devices

1.1.3.14 1.1.3.14 1.1.3.14

Avaya Desktop Video Device

1_1_2_020002 1_1_2_020002 1_1_2_020002

Avaya Flare® Experience for iPad Devices

2.0.4 2.0.4 2.0.4

BroadTouch Business Communicator for Desktop

- - 21.2.2.24

BroadTouch Business Communicator for iOS

- - 21.2.1.1799(Tablet)

21.5.1.5305(Mobile)

BroadTouch Business Communicator for Android

- - 21.1.4.5334(Tablet)

21.4.4.5334(Mobile)



Polycom, Inc. 10

Cisco TelePresence System EX90

7.3.6 7.3.6 7.3.6

Cisco TelePresence Integrator C20

7.3.6 7.3.6 7.3.6


7.3.6 7.3.6 7.3.6


7.3.6 7.3.6 7.3.6

Cisco TelePresence SX10 8.1.1, 8.2.1 8.1.1, 8.2.1 8.1.1, 8.2.1



Cisco E20 4.1.7 4.1.7 4.1.7

Cisco TelePresence System 3010

1.10.13(5) 1.10.13(5)

Cisco TelePresence System 1300

1.10.13(5) 1.10.13(5)

Cisco TelePresence TX9000

6.1.10(7) 6.1.10(7)

Cisco TelePresence TX1310

6.1.10(7) 6.1.10(7)

Cisco TelePresence System 500-37

6.1.10(7) 6.1.10(7)

Cisco TelePresence System 500-32

1.10.13(5) 1.10.13(5) 1.10.13(5)

Cisco TelePresence IX5000 8.0.6(7) 8.0.6(7) 8.0.6(7)

Cisco DX70 / DX80 /DX650 10.6.1 10.6.1 10.6.1

Cisco Jabber for Windows 11.1 11.1 11.1

Cisco Jabber for Mac 11.1 11.1 11.1

Cisco TelePresence System 1700 MXP

F9.3.4 F9.3.4 F9.3.4

Cisco TelePresence System Edge 95 MXP

F9.3.4 F9.3.4 F9.3.4

Huawei TE30 1.2.100 1.2.100 1.2.100

Huawei TE40 1.10.100 1.10.100 1.10.100



Polycom, Inc. 11

IBM Sametime Connect client

9.0.1 9.0.1 9.0.1

IBM Sametime Lotus client 9.0.1 9.0.1 9.0.1

IBM Sametime Web AV client (SVC)

9.0.1 9.0.1 9.0.1

IBM Sametime Web AV client (AVC)

9.0.1 9.0.1 9.0.1

LifeSize Room 4.7.22(3) 4.7.22(3) 4.7.22(3)

LifeSize Icon 600 2.9.1.(2001) 2.9.1.(2001) 2.9.1.(2001)

LifeSize Express 220 5.0.9(2) 5.0.9(2) 5.0.9(2)

LifeSize Team 220 5.0.9(2) 5.0.9(2) 5.0.9(2)

Microsoft Skype for Business 2016

16.0.4318.1000, 16.0.7127.1021

16.0.4318.1000, 16.0.7127.1021

16.0.4318.1000, 16.0.7127.1021

Microsoft Skype for Business 2015/Lync 2013

15.0.4809.1000 15.0.4809.1000 15.0.4809.1000

Microsoft Lync2010 client 4.0.7577.4498 4.0.7577.4498 4.0.7577.4498

Microsoft Lync MAC Client 14.3.3 14.3.3 14.3.3

Microsoft Skype for Business Client (Android)

6.4.0.5 6.4.0.5 6.4.0.5

Microsoft Skype for Business Mobile Client (iOS)

6.5.0.177 6.5.0.177 6.5.0.177

Microsoft Lync Client (Android)

5.6.3.15 5.6.3.15 5.6.3.15

Microsoft Lync Client (iOS) 5.7 5.7 5.7

Radvision Scopia XT1000 2.5.416 2.5.416 2.5.416

Siemens OpenScape Desktop Client

V7 R1.46.18 (70.1.46.0018)

V7 R1.46.18 (70.1.46.0018)

V7 R1.46.18 (70.1.46.0018)

Siemens OpenStage desktop phones

V3 R3.40.1 SIP 150701(openstage 60)

V3 R3.24.0 SIP 140911(Openstage80)





Sony PCS-XG80 2.45, 2.46 2.45, 2.46 2.45, 2.46



Polycom, Inc. 12

Sony PCS-XG100 1.50.20, 1.60 1.50.20, 1.60 1.50.20, 1.60

Tandberg 150 MXP L6.1 L6.1 L6.1

For more information about partner product interoperability, refer to the partner deployment guides.


Conferencing Options in Collaboration Server Virtual Edition

Polycom, Inc. 13


The following table summarizes the conferencing capabilities and options available in the different Conferencing Modes.

Features CP Only Mixed CP & SVC SVC Only

Reservations

Operator Conferences

Entry Queues * * *

Dial Out

Cascading **

IVR

Reduced IVR set for SVC endpoints

Permanent Conferences

LPR *** ***

Auto Redial

Content

All Content Settings,

All Content Protocols

Graphics Only, H.264 Cascade & SVC Optimized

Graphics Only, H.264 Cascade & SVC Optimized

Presentation Mode

Lecture Mode

Same Layout

Layout Selection

AVC endpoints only

Layout set to Auto Layout and defined on the endpoint

Skins

AVC endpoints only

Encryption

Recording

AVC recording only


Polycom, Inc. 14

* Entry Queue & Destination Conference must have the same profile (i.e. SVC only to SVC only, Mixed CP and SVC to Mixed CP and SVC)

** Only Basic Cascading is available

*** For AVC, the LPR error resiliency is used, for SVC endpoints other error resiliency methods are used.

Site Names

AVC endpoints only

Managed by the endpoint (not via MCU)

Message Overlay

Features CP Only Mixed CP & SVC SVC Only

Polycom Solution Support

Polycom, Inc. 15

Polycom Solution Support

Polycom Implementation and Maintenance services provide support for Polycom solution components only. Additional services for supported third-party Unified Communications (UC) environments integrated with Polycom solutions are available from Polycom Global Services and its certified Partners. These additional services will help customers successfully design, deploy, optimize and manage Polycom visual communications within their UC environments.

Professional Services for Microsoft Integration is mandatory for Polycom Conferencing for Microsoft Outlook and Microsoft Office Communications Server integrations. For additional information and details please see http://www.polycom.com/services/professional_services/index.html or contact your local Polycom representative.

Resources and Feedback

Polycom, Inc. 16

Resources and Feedback

To find support and to report findings, use the following resources:

Polycom Support and Resources

Polycom Support For support please contact the Polycom Team at [email protected]

Polycom Test Systems Go to http://www.polycom.com/videotest for a list of worldwide numbers that you can use to test your video conferencing system.

mailto:[email protected]

http://support.polycom.com/PolycomService/support/us/support/documentation/video_test_numbers.html

Virtual Edition Host Server Hardware Profile

Polycom, Inc. 17


RealPresence Collaboration Server, Virtual Edition Hardware ProfileThis section provides information on the minimal Virtual Machine host settings and configuration, some of which are manual, required for the deployment of RealPresence Collaboration Server, Virtual Edition.

The described configuration is not mandatory; however, failing to follow it might result in degraded video and audio performance. Due to differences between hardware and VM environments, the performance information below is provided for guidance purposes only, and does not represent a guarantee of any kind by Polycom.

An example for a typical deployment is a 32 logical cores machine at 2.9GHz.

Note: Dedicated VM Server

To maximize audio and video quality Polycom strongly recommends a dedicated VM server per Collaboration Server.

Deployment Settings - Minimum / Typical

Component Minimum Deployment Settings Typical Deployment Settings

vCPU 25000 MHz Reservation 90000 MHz Reservation

Memory 16 GB Reservation 16 GB Reservation

Network Adapter (NIC) 2 x 1Gbit 2 x 1Gbit

Hard Disk (Thin Provision) 30 GB 30 GB

Performance 14 SD ports or 7 HD ports 60 SD ports or 30 HD ports

Note: vCPU

For Intel CPUs, when Hyperthreading is enabled, the numbers above refer to logical cores (vCores) and not physical ones.

Note: Network Interface Card

Depending on the environment, the virtual machine might need a Network Interface Card (NIC) from the host dedicated for the virtual machine. For more information, refer to your VMware administrator.


Polycom, Inc. 18

CPU Reservations for Licenses PurchasedThe Administrator is required to change the number of cores per socket so that the total number of cores reflects the CPU cores required for the purchased licenses.

The table below demonstrates the more common/likely machines. Other systems might require some experimentation.

For more information, refer to RealPresence Collaboration Server 1800/2000/4000/Virtual Edition Getting Started Guide.

Soft Blade PrerequisitesThe minimum requirements for deploying Soft Blade are: 4 vCPU, 8GB RAM, 60 GB HDD.

For more information on platforms and capacities of Main MCU (virtual edition) and Soft Blade, see New VE Hosts and Increased Capacity Limitations

Number of Cores Required for Licenses Purchased

Number of Licenses Purchased

CPU Configuration

Dual Intel E5-269032 cores

Dual Intel E5-2680

32 cores*

Dual Intel E5-2650

32 Cores*

Dual Intel E5-262024 Cores

Dual Intel X5660

24 Cores*

5 ports 5 5 7 8 8

10 ports 10 11 14 16 16

15 ports 16 17 21 24 24

20 ports 21 23 29 NA NA

25 ports 26 29 NA NA NA

30 ports 32 NA NA NA NA

* These numbers are estimates only, and may require adjustment.

NOTE: Hyperthreading

These numbers assume that hyperthreading is enabled in the physical server’s BIOS.If hyperthreading is disabled, the above numbers are approximately halved.

NOTE: Over-allocation of Cores

Do not over-allocate cores.

RMX Web Client and RMX Manager

Polycom, Inc. 19

RMX Web Client and RMX Manager

The RMX Web Client and RMX Manager applications can be installed in an environment that meets the following requirements:

● Minimum Hardware – Intel® Pentium® III, 1 GHz or higher, 1024 MB RAM, 500 MB free disk space.

● Workstation Operating System – Microsoft® Windows® XP, Windows® 7, and Windows® 8.

● Network Card – 10/100/1000 Mbps.

● Web Browser - Microsoft® Internet Explorer® Version 7, 8, 9, and 10.

● RMX Web client and RMX Manager are optimized for display at a resolution of 1280 x 800 pixels and a magnification of 100%

The following table lists the environments (Web Browsers and Operating Systems) with which the RMX Web Client and RMX Manager applications are supported.

Collaboration Server Web Client/RMX Manager Environment Interoperability Table

Web Browser Operating System

Internet Explorer 7 Windows Vista™

Windows 7

Internet Explorer 8 Windows 7

Internet Explorer 9 Windows 7 and Windows 8

Internet Explorer 10* Windows 8

Note: Windows 10

Only RMX Manager can be used with Windows 10, and following preview features are not supported through RMX Manager:• View Participant Sent Video (AVC Only)

• Preview and add Motion slide to IVR services

Windows 7™ Security Settings

Polycom, Inc. 20


If Windows 7 is installed on the workstation, Protected Mode must be disabled before downloading the software to the workstation.

To disable Protected Mode:

1 In the Internet Options dialog, select the Security tab.


Polycom, Inc. 21

2 Clear the Enable Protected Mode check box for each of the following tabs:

Internet

Local intranet

Trusted sites

3 After successful connection to Collaboration Server, the Enable Protected Mode check boxes can be selected to enable Protected Mode for the following tabs:

Internet

Local intranet

Internet Explorer 8 Configuration

Polycom, Inc. 22


When using Internet Explorer 8 to run the RMX Web Client or RMX Manager applications, it is important to configure the browser according to the following procedure.

To configure Internet Explorer 8:

1 Close all browsers running on the workstation.

2 Use the Windows Task Manager to verify that no iexplore.exe processes are running on the workstation. If any processes are found, click End Task to end them.

3 Open Internet Explorer but do not connect to the MCU.

4 In the Internet Explorer menu bar select Tools > Internet Options, and select the General tab.


Polycom, Inc. 23

5 In the Browsing history section, click Delete.

The Delete Browsing History dialog is displayed.

6 Select the Temporary Internet files and Cookies check boxes, and click Delete to delete the files and return.

7 In the Internet Options dialog, click Settings.

The Temporary Internet Files and History Settings dialog is displayed.


Polycom, Inc. 24

8 Click View objects.

The Downloaded Program Files folder containing the installed Program Files is displayed.

9 Select the EMAClassLoader.dll file and press the keyboard Delete key, or right-click the EMA.ClassLoader.dll file, and select Delete.

10 Close the Downloaded Program Files folder and the Temporary Internet Files and History Settings dialog.

11 In the Internet Options dialog, click OK to save the changes and close the dialog.

Installation Notes

Polycom, Inc. 25

Installation Notes

In specific network conditions; that is, when:

● The enterprise-facing interface IP of the firewall (that is, the interface to the Intranet) and the IP address assigned to the RMX media card are in the same subnet AND

● ICMP redirect is enabled on the default gateway,

Use RMX Manager to set up a static route to the TURN server. This ensures that media traffic is always routed through the default gateway, which prevents AVMCU calls from being disconnected.

Version 8.7.1 - Upgrade Package Contents

Polycom, Inc. 26

Version 8.7.1 - Upgrade Package Contents

The version 8.7.1 upgrade package must be downloaded from the Polycom Resource Center and includes the following items:

● lan.cfg file

● LanConfigUtility.exe

● RealPresence Collaboration Server 1800/2000/4000/VE Documentation

RealPresence Collaboration Server 1800/2000/4000/VE Version 8.7.1 Release Notes

RealPresence Collaboration Server 1800/2000/4000/VE Getting Started Guide

RealPresence Collaboration Server 1800/2000/4000/VE Administrator Guide

RealPresence Collaboration Server (RMX) 1800/2000/4000 Hardware Guides

Installation Quick Start Guides for RealPresence Collaboration Server (RMX) 1800/2000/4000

RMX Open Source Licenses

● External DB Tools

RealPresence Collaboration Server (RMX) 1800/2000/4000 External Database API Programmer’s Guide

Sample Scripts

● RMX API Kit Version 8.7.1

RealPresence Collaboration Server API Version 8.7.1 Release Notes

RealPresence Collaboration Server XML API Overview

RealPresence Collaboration Server XML API Schema Reference Guide

MGC to RMX XML API Conferencing Comparison

Polycom XML Tracer User’s Guide

XML Schemas

Polycom XML Tracer application

● Translations of RealPresence Collaboration Server 1800/2000/4000/VE.

Getting Started Guide:

French, German, Japanese, Russian, Simplified Chinese, Hebrew and Portuguese

Hardware Guide:

French, German, Japanese, Korean, Russian, Simplified Chinese, Spanish

To view the latest Polycom product documentation, visit the DOCUMENTS & DOWNLOADS section of the Polycom website at http://support.polycom.com.

Collaboration Servers 1800/2000/4000 - Software Upgrade Procedures

Polycom, Inc. 27


Upgrade Guidelines● In specific network conditions; that is, when:

The enterprise-facing interface IP of the firewall (that is, the interface to the Intranet) and the IP address assigned to the RMX media card are in the same subnet AND

ICMP redirect is enabled on the default gateway

Use RMX Manager to set up a static route to the TURN server. This ensures that media traffic is always routed through the default gateway which prevents AVMCU calls from being disconnected.

● Ensure that the Control Unit memory size is at least 1024MB. If memory size is 512MB, DO NOT perform the upgrade procedure. Contact Polycom Support.

● To upgrade to 8.7.1 with MPMRx card(s), perform the following procedures:

1 Upgrade the MCU to software version 8.7.1 following the specific upgrade procedures for your current version.

IMPORTANT UPGRADE NOTES: Customers not requiring specific Skype for Business features should remain on the Generally Available (GA) RPCS versions of 8.6.x or 8.5.x

• RealPresence Collaboration Server (RPCS) 8.7.1 is focused around O365 support and Skype for Business improvements (only customers requiring specific Skype for Business features should upgrade)

• RPCS 8.7.1 is not expected to improve the performance of SVC calls

• Customers can choose to use the new RPCS “Soft Blades” topology if Microsoft RDP content support is required

• Customers who are currently using Polycom ContentConnect for sharing content should continue to use Polycom ContentConnect for content sharing

Content Sharing Note: Any participant who is sharing content should first STOP/discontinue sharing content before another participant begins sharing content.

Upgrade Precautions

• It is essential you use the Backup Configuration function prior to upgrading your MCU. For more information see the RealPresence Collaboration Server 1800/2000/4000/Virtual Edition Administrator Guide, Software Management.

• When upgrading it is recommended that you upgrade from the latest maintenance release of the version you currently have.


Polycom, Inc. 28

2 Collaboration Server (RMX) 2000/4000 systems shipped with MPMx media cards are not supported from software versions 8.6 and on. Therefore, If the MCU contains MPM/MPM+/MPMx cards, make sure these cards are disabled.

3 Replace the existing cards with the MPMRx card(s).

4 In the Hardware Monitor screen, click Reset to reset the MCU.


Polycom, Inc. 29

To check the MCU memory size:

» In the RMX Web Client / RMX Manager go to Administration > System Information.

● If Windows7™ is installed on the workstation, Protected Mode must be disabled before downloading the Collaboration Server software to the workstation. For more information see Windows 7™ Security Settings.

● To maximize conferencing performance, especially in high bit rate call environments, a 1 GB connection is recommended for each LAN connection.

● If the default POLYCOM user is defined in the RMX Web Client, an Active Alarm is created and the MCU status changes to MAJOR until a new Administrator user replaces the default user.


Polycom, Inc. 30

Collaboration Server (RMX) 2000/4000 Hardware / Software Version SupportThe Collaboration Server (RMX) 2000/4000 must used with the correct software version:

Both Control Modules BRD2534B-L0 / BRD2535B-L0 include USB and VGA ports on the front panel.

RMX 2000 system with CNTL 2000 Module BRD2534B-L0

RMX 4000 system with CNTL 4000 Module BRD2534B-L0


Polycom, Inc. 31

Safe Upgrade Paths to Version 8.7.1The RMX includes a safety mechanism to ensure that a viable and safe software version installation is selected on an RMX. It ensures that the current RMX software version and the new software installation are matched to an internal logic table, and enables or rejects the software installation. When an incorrect or non-viable version upgrade/downgrade path is attempted, an alarm and fault are activated on the RMX.

The following table lists the software versions that are approved for upgrade by Safe Upgrade process for Version 8.7.1.

If your RMX version is not listed above, refer to the table below for intermediate and safe upgrade paths to Version 8.7.1.

Software Version RMX 1800 RMX 2000 RMX 4000

8.6 8.5 8.4 8.3 (See note below) 8.2 (See note below) 8.1.8 (See note below) 8.1.5 (See note below) 8.1 (See note below) 7.8 (See note below) 7.7 7.6/7.6.1 7.5.0J/7.5.1J 7.2/7.2.x 7.1 7.0.x/7.0.2C 7.0 6.x 5.x 4.7.2


Polycom, Inc. 32

The following table lists the upgrade paths to Version 8.7.1.

Note: Upgrade from maintenance releases

• When upgrading to version 8.7.1 from versions 7.8, 8.1, 8.2, and 8.3, it is essential that you upgrade from the following maintenance releases (or later) of the version currently installed: 7.8 - RMX_7.8.0.246.131 8.1.7 - RMX_8.1.7.37.033 8.2 - RMX_8.2.0.85.007 8.3 - RMX_8.3.0.148

If these maintenance releases (or later) are not installed, an upgrade to the latest maintenance release must be performed before upgrading to version 8.7.1. This is of particular importance for systems with 1024MB of memory.

• If you are upgrading from V7.0.1 or earlier please refer to the upgrade section of the version’s release notes for more information about upgrading to V8.3 / V8.4.

• If your current version is 2.x, 3.x or 4.x, DO NOT upgrade to Version 8.7.1. Contact Polycom Support for the appropriate upgrade paths.

Current Version

First Intermediate Upgrade

Second Intermediate Upgrade

Third Intermediate Upgrade New Version

Version Key Version Key Version Key Version Key

8.6 8.7.1 Yes

8.5 N/A N/A N/A 8.7.1 Yes

8.4 N/A N/A N/A 8.7.1 Yes

8.3 N/A N/A N/A 8.7.1 Yes

8.2 N/A N/A N/A 8.7.1 Yes

8.1 N/A N/A N/A 8.7.1 Yes

7.8 N/A N/A N/A 8.7.1 Yes

7.7 N/A N/A N/A 8.7.1 Yes

7.6/7.6.1 N/A N/A N/A 8.7.1 Yes

7.5.0J/7.5.1J N/A N/A N/A 8.7.1 Yes

7.2 / 7.2.1 / 7.2.2 N/A N/A N/A 8.7.1 Yes

7.0.1 / 7.0.2 / 7.0.3 / 7.1

N/A N/A N/A 8.7.1 Yes

7.0 7.0.3 No N/A N/A 8.7.1 Yes

6.0.2 7.0.3 Yes N/A N/A 8.7.1 Yes

6.0 / 6.0.1 6.0.2 No 7.0.3 Yes N/A 8.7.1 Yes

5.0.2 7.0.3 Yes N/A N/A 8.7.1 Yes

5.0 / 5.0.1 5.0.2 No 7.0.3 Yes N/A 8.7.1 Yes


Polycom, Inc. 33

You can disable the safety upgrade mechanism by changing the default setting of the ENFORCE_SAFE_UPGRADE system flag to NO.

To prepare for the upgrade:

1 If the Collaboration Server is used with a RealPresence DMA system, disable the DMA functionality:

a Log into the DMA that handles call transfers for the Collaboration Server.

b Select Network > MCU > MCUs.

c Select the MCU, and choose either Stop Using or Busy Out.

Verify that all conferences, including permanent conferences, have been terminated.

Upgrading from Version 8.4 / 8.5 to 8.7.1

To install MCU software Version 8.7.1:

1 On the Collaboration Server menu, click Administration> Software Management > Software Download.

2 Browse to the Install Path, selecting the Version 8.7.1.x.x.bin file in the folder where Version 8.7.1 is saved, and click Install.

3 The Install Software allows following the files copying progress.

At the end of the Copying Files process the system displays an indication that the software copying procedure is Done.

Note: Incorrect Version Upgrade Description

When an incorrect or non viable version upgrade/downgrade is attempted, an alarm and a fault are raised on the Collaboration Server.

Once you click OK, the Collaboration Server software installation procedure is aborted and a system alert activates in the Faults List:

During any upgrade or downgrade software version installation when the Safe Software Version Installation warning has been activated, your current browser session blocks any new installation attempt. This applies to all software versions, except for version 7.6 which enables version downgrades. As a workaround close and then re-open a new browser session, which enables you to start a new software version installation.


Polycom, Inc. 34

4 Once you click OK, the Install Software indicates that Software Loading is in progress.

A series of Active Alarms are displayed indicating the progress of the upgrade process.

The Install Software indicates that IPMC Burning is in progress.

A further series of Active Alarms are displayed indicating the progress of the upgrade process.

The upgrade procedure takes approximately 20 minutes.

Note:

Sometimes, when updating the Version 8.7.1 license key, the system displays an active alarm.

Ignore this Active Alarm and complete this installation procedure.


Polycom, Inc. 35

A system message alert may be displayed, click Next/Cancel.

Connection to the Collaboration Server is terminated and you are prompted to reopen the browser.

5 Approximately 10 minutes after receiving this message, close and reopen the browser.

6 Enter the IP address of the Collaboration Server Control Unit in the browser’s address line, and press Enter to reconnect to Collaboration Server.

If the browser displays a message indicating that it cannot display the requested page, close and reopen the browser and connect to the Collaboration Server.

The version number in the Welcome screen has changed to 8.7.1.

7 In the RMX Web Client Welcome screen, enter your User Name and Password, and click Login.

In the Main Screen an MCU State indicator displays a progress indicator showing the time remaining until the system start-up is complete.

To use the new features such as Operator Assistance and Gateway Sessions the IVR Services must be updated. For more details, see Additional/Optional System Considerations After Upgrade.

8 If the Collaboration Server is used with a RealPresence DMA system, enable the DMA functionality:

9 Log into the DMA that handles call transfers for the Collaboration Server.

10 Select Network > MCU > MCUs.

11 Select the MCU and choose Start Using.

12 Verify that the version number is updated signifying that the upgrade is complete.

Additional/Optional System Considerations After UpgradeUpgrading the system can result in changes to default configurations system behaviors:

● Permanent Conferences must be manually re-scheduled.

● IVR Services should be checked after upgrading from earlier versions (V4.0 / V6.0 / V7.x / V7.6.1) to ensure that changed or additional DTMF codes do not conflict with previously defined DTMF codes.

● Enable Gathering check box in the Profile Properties > Gathering Settings dialog is not selected by default for preexisting Profiles.

● SIP Proxy Registration is configured the Conference Profile > Network Services dialog beginning with version 7.1.

If a browser environment error appears, close all the browser sessions, and reconnect to the Collaboration Server. If the error message reappears, either run the automatic troubleshooter utility or manually preform the suggested troubleshooting procedures. For more details, see Known Limitations.


Polycom, Inc. 36

● Media Encryption is enabled by a Conference Profile setting from version V7.6.1, replacing the ALLOW_NON_ENCRYPT_PARTY_IN_ENCRYPT_CONF System Flag. Modified the profile to meet your environment’s encryption requirements.

● Automatic Muting of Noisy AVC-based Endpoints is not automatically enabled in existing Profiles and has to be manually enabled, if required. In new Profiles that are created after the upgrade, auto mute of noisy endpoints option is enabled by default.

● RealPresence DMA in the environment requires that the value of the flag MAX_CONF_PASSWORD _REPEATED_CHAR System Flag value be set to 4 system for compatibility from version 7.7.

● RMX Manager for the specific version installed should be downloaded and installed. For more information see RMX Manager Application in the RealPresence Collaboration Server 1800/2000/4000/Virtual Edition Administrator Guide.

For more information refer to the Release Notes detailing upgrades from the specific versions.

Collaboration Server Virtual Edition - Software Upgrade Procedures

Polycom, Inc. 37


A successful upgrade requires prior preparation. These steps help ensure a smooth upgrade with minimal downtime.

To prepare for the upgrade:

1 Download the Version 8.7.1 software from the Polycom Resource Center web site.

2 If the Collaboration Server is used with a RealPresence DMA system, disable the DMA functionality:

a Log into the DMA that handles call transfers for Collaboration Server.


c Select the MCU and choose either Stop Using or Busy Out.

3 Verify that all conferences, including permanent conferences, have been terminated.

Upgrade ProceduresDue to the licensing method greatly altering from version 8.5, upgrading from versions earlier than 8.5 to Version 8.7.1 require using a different procedure than the one used for upgrading from Version 8.5 and on.

Below, both procedures are described.

Upgrading to Version 8.7.1 from Version 8.5 and OnThe method of upgrading the Virtual Edition MCU is similar in look and feel to that of its hardware based counterparts.

In addition the MCU remains active during the upgrade, and can host conferences, until the reboot required to complete the upgrade procedure.

To upgrade the Virtual Edition MCU:

1 Backup the configuration file:

a Select Administration > Software Management > Backup Configuration.

• If Windows7™ is installed on the workstation, Protected Mode must be disabled before downloading the Collaboration Server software to the workstation. For more information see Windows 7™ Security Settings.

• To maximize conferencing performance, especially in high bit rate call environments, a 1 GB connection is recommended for each LAN connection.

• If the default POLYCOM user is defined in the RMX Web Client, an Active Alarm is created and the MCU status changes to MAJOR until a new Administrator user replaces the default user.


Polycom, Inc. 38

b In the Backup Configuration window, click Browse to select a backup directory.

c Click Backup to back all configurations in the directory.

2 On the RMX menu, select Administration> Software Management > Software Download.

3 Browse to the Install Path, selecting the .upg file for upgrade, in the folder where Version 8.7.1 is saved, and click Install.

The installation of the upgrade proceeds. A progress bar is displayed while the files are copied and the software is installed.

When the installation completes, a dialog prompts the administrator to reset the MCU to complete the upgrade.

4 Reset the MCU, at your convenience, to complete the upgrade (until reset, the previous version is operational). For more information on Collaboration Server reset, see RealPresence Collaboration Server Administrator Guide, Administration and Utilities chapter.

Upgrading to Version 8.7.1 from a Version Earlier than 8.5The procedure described below is comprised of the following phases:

● Installing the RealPresence® Platform Director™.

● Backup of current Collaboration Server configuration files.

● Installation (from scratch) of Collaboration Server Version 8.7.1.

● Licensing via the Platform Director.

● Restoring previous configuration file values.

To Upgrade to Version 8.7.1 from a Version Earlier than 8.5:

1 Install the Platform Director.

The Platform Director is included with all Virtual Edition products, and is available at the Polycom Support Site for download.

http://support.polycom.com/PolycomService/support/us/support/network/index.html

2 Backup the configuration file:

a Select Administration > Software Management > Backup Configuration.

b In the Backup Configuration window, click Browse to select a backup directory.

c Click Backup to back all configurations in the directory.

3 Download the VE V8.7.1 image from the Support Site: http://support.polycom.com/PolycomService/support/us/support/network/collaboration_conferencing_platforms/realpresence_collaboration_server_ve.html

The file to download has an .ova extension.

4 Reboot the machine.

Note: Collaboration Server Requires Licensing to Work

The Collaboration Server stops working at this point, and must be added to the Platform Director Environment.

http://support.polycom.com


Polycom, Inc. 39

5 Create a New Virtual Instance of the VE.

For information see RealPresence® Platform Director™ Administrator Guide under: http://supportdocs.polycom.com/PolycomService/support/global/documents/support/setup_maintenance/products/network.

6 Restore the configuration file:

a Select Administration > Software Management > Restore Configuration.

b In the Restore Configuration window, click Browse to select the backed up configuration file.

c Click Restore.

7 If the Collaboration Server is used with a DMA, enable the DMA functionality:

a Log into the DMA that handles call transfers for the Collaboration Server.


c Select the MCU and choose Start Using.

8 Verify that the version number is updated signifying that the upgrade is complete.

Version 8.7.1 Detailed Descriptions of New Features

Polycom, Inc. 40


Network and System FeaturesThe system features in the version 8.7.1 release are:

● Polycom® RealPresence Clariti™ Support

● New VE Hosts and Increased Capacity Limitations

Polycom® RealPresence Clariti™ SupportRealPresence Collaboration Server 1800/Virtual Edition is available as part of Polycom® RealPresence Clariti™, a Polycom collaboration infrastructure offer that features simplified concurrent user licensing and add-on options. RealPresence Clariti customers should consult with their Polycom representative to ensure they have the correct licensing information before upgrading.

Polycom RealPresence Clariti and Virtual Edition customers who have a Polycom RealPresence Resource Manager System version 10.0 or later must use the RealPresence Resource Manager System to license their product. If you have not deployed a RealPresence Resource Manager System or if you have not upgraded your RealPresence Resource Manager System to version 10.0 or later, you must license your product using the RealPresence Platform Director System version 3.0.

RealPresence Collaboration Server 1800 customers cannot use RealPresence Resource Manager or RealPresence Platform Director for licensing, you must license your system with activation key.

In the solution, the real capacity of RealPresence Collaboration Server 1800/Virtual Edition still relies on other RealPresence Clariti components, for example RealPresence DMA.

For installing and licensing instructions of RealPresence Collaboration Server 1800/Virtual Edition, refer to RealPresence Collaboration Server 1800/2000/4000/Virtual Edition Getting Started Guide.

New VE Hosts and Increased Capacity LimitationsNew platforms (Quad AMD Opteron 6380 and Dual E5-2690v3) can be used to deploy RealPresence Collaboration Server, Virtual Edition.

The following table lists RealPresence Collaboration Server, Virtual Edition capacities on different reference platforms:

Note: RealPresence Resource Manager v10.0 or RealPresence Platform Director v3.0

If your deployment includes RealPresence Resource Manager 10.0 or later, you cannot use RealPresence Platform Director 3.0 to license your product.


Polycom, Inc. 41

The following table lists the Soft Blade (on its own reference platforms) resource capacities:

Conferencing FeaturesConferencing features added in version 8.7.1 are:

● Personal Layout in Lecture Mode

● Legacy Content in Multiple Content Transcoding

● Lock/Unlock Conference

● NoiseBlock™

● Override Mute Participants

● Polycom Labs

Resource Capacity in Non-Mixed and Mixed Modes by Platform and License Mode (RealPresence Clariti/ [a-la-carte])

Port Type

RealPresence Collaboration Server Virtual Edition

Non-Mixed Mode Mixed Mode

Quad AMD Opteron 6380 @ 2.5GHz64 Cores

Dual E5-2690v3 @ 2.6GHz48 Cores

Dual E5-2690 @ 2.9GHz32 Cores



Quad AMD Opteron 6380 @ 2.5GHz64 Cores

Dual E5-2690v3 @ 2.6GHz48 Cores




AVC 1080p60 8 10 10(Asy) NA NA 8 10 10(Asy) NA NA

AVC 1080p30 16 21 15 NA NA 16 21 15 NA NA

AVC 720p30 33 42 30 15 7 33 42 30 15 7

AVC SDp30 66 84 60 30 15 66 84 60 30 15

AVC CIFp30 66 84 60 30 15 66 84 60 30 15

Audio 396 504 360 180 90 300 300 300 150 75

SVC (& SAC) 300[165] 300 [210] 300 [150] 150[75] 75[35] 210[165] 210[210] 200[150] 100[75] 50[35]

1080 SVC (&SAC)

210[165] 210[210] 150[150] 75[75] 37[35] 210[165] 210[210] 150[150] 75[75] 37[35]

WebRTC VGA/SD

22 28 20 10 5 22 28 20 10 5

Numbers in square brackets denote a-la-carte licensing mode while all others denote RealPresence Clariti licensing mode.

Soft Blade Resource Capacity by Platform

Port TypeDual E5-2690v3@ 2.6GHz 8 Cores

Dual E5 -2620@ 2.0GHz 16 Cores

Dual [email protected] 8 Cores

RDP 21 33 16


Polycom, Inc. 42

Personal Layout in Lecture ModeBeginning with this version, Personal Layouts can be modified in conferences defined to operate in Lecture Mode. In previous versions Personal Layout was disabled for conferences operating in Lecture Mode.

The Personal Layout of the operator can be modified, allowing the operator to view the video of a participant designated to be the next lecturer. The designated participant can be advised about camera settings, etc. before being assigned by the operator as the new lecturer.

The Personal Layout of the current Lecturer cannot be modified.

In cascaded conferences personal layouts can be modified while in Lecture Mode, but only for participants that are hosted on the local MCU.

DTMF code “0”, entered from a remote control or other device will return a user’s endpoint to the conference layout. All other Click&View DTMF codes are ignored while the conference is in Lecture Mode.

If Send Content to Legacy Endpoints is checked in the conference profile, participants with endpoints that do not support the meeting’s Content settings can view Content using the people video channel.

For more information, refer to RealPresence Collaboration Server 1800/2000/4000/Virtual Edition Administrator Guide, Lecture Mode and Personal Conference Manager (PCM) sections.

Legacy Content in Multiple Content TranscodingBeginning with this version, the Send Content to Legacy Endpoints option in the Conference Profile - Video Quality dialog, can be either checked or unchecked when using Multiple Content Resolutions (Content Transcoding).

In previous versions, the Send Content to Legacy Endpoints option was checked and disabled when using Multiple Content Resolutions and could not be unchecked.

Lock/Unlock Conference

Locking or unlocking a conference could previously only be carried out via a digital DTMF code. Locking and unlocking a conference can now be enabled or disabled via:

● Web GUI

● RMX Manager

● XML API

To lock a conference via Web GUI or RMX Manager:

1 1 In the Conference pane, right-click the conference name.

Note: Feature Not Supported in Conference Running via DMA

This feature is only supported when the DMA is not acting as the MCU manager, and participants dial-in directly to the MCU and not via VMR.

Note: Locking and Unlocking Permissions:

You must be logged in as a chairperson, operator, or administrator to access this feature.


Polycom, Inc. 43

2 In the drop-down menu, select Lock Conference.

To unlock a locked conference via Web GUI or RMX Manager:

1 To unlock a locked conference via Web GUI or RMX Manager:

2 1 In the Conference pane, right-click the conference name.

3 In the drop-down menu, select Unlock Conference.

Reference Number Description

1 Lock conference

Caution: Conference Locking via Web GUI or RMX Manager hides Participant List

Locking the conference via Web GUI or RMX Manager hides the list of conference participants in the Participants pane.


Polycom, Inc. 44

Conference locking via XML API

A new boolean element, SET_LOCK, was added to trans_conf_2.xsd schema.

Setting its value to TRUE locks the conference.

It’s default value is FALSE - unlocked.

NoiseBlock™NoiseBlock™ is a mechanism based on heuristic algorithm, which differentiates human speech from other non-speech background noises which come from endpoints.

Reference Number Description

1 Unlock conference

Notification of Locked (Unlocked) Conference:

• If the conference is locked, a voice prompt informs users that the conference is secured and they cannot join. Also, there is no display of participants taking part in the conference.

• If the conference is unlocked, a voice prompt informs users that they are free to join the conference and all participants taking part in the conference are displayed.

• If lock/unlock is enabled in the MCU and without any interaction with a Lync cascaded conference, both the Polycom and Lync sides of the conference restrict adding new participants.


Polycom, Inc. 45

The NoiseBlock feature performs the following actions:

1 Attenuates the audio of endpoints emitting non-speech background noises

2 Enhance the conferencing experience

3 Avoid endpoints which emit background noises to mistakenly become the active speaker, which might result in diversion of the meeting’s focus from the real speaker.

NoiseBlock does not guarantee exact identification of non-speech originated sounds. This may result, in some cases, with non-speech sounds not being identified as such. As a result, no attenuation of that endpoint audio is carried out. Sounds with the noise frequency, such as applause and background music, may also be muted.

When the endpoints are automatically muted by the MCU, no indication is displayed in the RMX Web Client or RMX Manager, as the system doesn’t consider it as a deliberate mute.

The following table summarizes the state of the NoiseBlock feature depending on the ENABLE_SELECTIVE_MIXING flag value (Default YES) and the Auto mute noisy endpoints setting (Default the check box is selected) in the Profile Properties - Audio Settings:

Pre-requisites

● It is supported in CP conferences and in Mixed CP and SVC conferences.

● It affects only AVC-based and audio only endpoints (non-SAC endpoints). It does not affect SVC-based endpoints.

● In a mixed CP and SVC conferences, audio can be blocked only towards AVC-based endpoints. If the noisy endpoint is SVC-based, its audio channel is not sent to the AVC-based endpoints, but it is sent to the other SVC-based endpoints.

● When upgrading from a version prior to 8.1, the Auto mute noisy endpoints option is not automatically selected.

In Profiles created after the upgrade, the Auto mute noisy endpoints option is automatically selected.

● You need to manually add the ENABLE_SELECTIVE_MIXING system flag, and enable/disable the function by change the value to YES/NO. MCU reset is not required when changing the system flag value.

Conditions for enabling/disabling the automatic muting of noisy endpoints

ENABLE_SELECTIVE_MIXING Value Auto mute noisy endpoints Setting NoiseBlock State

YES check box selected Enabled

YES check box cleared Disabled

YES Unknown, for example, the conference is started from the DMA

Enabled

NO check box selected Disabled

NO check box cleared Disabled

NO Unknown, for example, the conference is started from the DMA

Disabled


Polycom, Inc. 46

● If your conferencing environment includes Polycom DMA, the conferences started from the DMA do not include the NoiseBlock parameter as it is not part of the DMA Profiles. In such a case, when the parameter setting is unknown, the system enables/disables the NoiseBlock according to the system flag setting - if the flag is set to YES, it is enabled in the conference.

To enable and disable Auto mute noisy endpoints:

1 In a new or existing Conference Profile, select the Audio Settings tab

2 Select/clear the Auto mute noisy endpoints check box according to your preference.

3 Click OK.

Override Mute ParticipantsIf the system flag OVERRIDE_MUTE_ALL is set to YES, participants can unmute themselves by entering the DTMF code 123 regardless they were muted by Administrator, Chairperson (*86), or themselves (*6)

The OVERRIDE_MUTE_ALL system flag value is NO by default and must be manually added to the system configuration.

Note: Only if the chairperson dials *5 and any endpoint dials the configured override mute all DTMF, the override DTMF continues to function without the need of OVERRIDE_MUTE_ALL flag.


Polycom, Inc. 47

Polycom LabsPolycom enables examining experimental features of Polycom RealPresence Collaboration Server. These features may be later incorporated as constant features, but at this point are neither tested nor supported.

Only an Administrator and the SUPPORT users may access the experimental features, provided the Collaboration Server is in experimental mode.

Experimental features activation does not require system restart, and take effect immediately on newly created conferences.

Inactivated features cannot be viewed or examined.

To activate the experimental features:

1 In the Collaboration Server main menu select Setup > Polycom Labs.

2 Select Enable Polycom Lab Features to enable experimental mode.

3 Select the check box of the feature(s) you wish to enable.

4 Click OK to confirm.

At this point, the selected lab features may be activated vie their respective activation points in the UI.

Lab Features Guidelines

● Experimental Features may be enabled both via User Interface, as described above, or via XML API.

Warning

Do not activate any of the lab features in Collaboration Servers used at production sites. Any attempt to do so is at your own peril.


Polycom, Inc. 48

● The User Interface displays the list of available Lab features according to the Interface / RMX Manager version, and not according to the Collaboration Server version. Therefore, the used Interface / RMX Manager should match the current Collaboration Server version, to allow enabling new Lab features.

In that context, if the Interface / RMX Manager version is higher than that of the Collaboration Server, the newer options are displayed, though the Collaboration Server does not support them.

● Enabling a Lab feature merely results in display of feature related check box in Profile/Conference Properties dialog. Selecting the check box at the conference/profile level activates the feature for that specific conference, or new conferences launched using this specific profile.

● Disabling Lab Features only inactivates them, but preserves their respective check boxes values. Thus, should the Lab Features be re-activated in general, their respective status from before the general inactivating is resumed.

However, ongoing conferences retain the Lab features activation and status from their creation point.

● Lab Features settings are preserved during Backup & Restore operations, even when involving upgrading to a higher version, in which case an adjustment of the appropriate system flags and/or setting is performed.

● When Lab Features are enabled, conferencing profiles defined in the MCU are preferred to those defined in the DMA.

● In cascaded environments, the Administrator should verify the Lab Features settings across all the cascaded MCUs are the same.

Each of the Lab features in this version is described in an attached addendum:

● Addendum to Release Notes Polycom Lab Feature - Discussion Mode Layout

● Addendum to Release Notes Polycom Lab Feature - Exclude Inactive-Video Participants from Layout

● Addendum to Release Notes Polycom Lab Feature - Using Video Clips for IVR Services

● Addendum to Release Notes Polycom Lab Feature - Popup Site Name on Participant Join/Leave


Polycom, Inc. 49

Miscellaneous FeaturesThe general features added in version 8.7.1 are:

● NTLMv2 Support for LDAP Connections

● Dynamic Bandwidth Adaptation

● Configure Timeout between End of Chairperson IVR message and First DTMF Key

NTLMv2 Support for LDAP ConnectionsSupport for NTLMv2 has been added for LDAP connections. The authentication protocol will be negotiated with preference given to NTLMv2.

Dynamic Bandwidth AdaptationIn a WebRTC bridged conference, RealPresence Collaboration Server, Virtual Edition, implements dynamic bandwidth adaption for conference connections in up-link and down-link streams according to real-time change of congestion levels to achieve an acceptable video quality. The dynamic bandwidth adaption mechanism includes:

● Receiving goog-remb (Receiver Estimated Maximum Bitrate) RTCP-FB and changing the specified outgoing stream(s) to the specified bandwidth.

● Generating goog-remb according to the detected congestion level.

● Improving the endpoints’ packet loss detection; the retransmitted Video packets are sent with a different payload type.

Configure Timeout between End of Chairperson IVR message and First DTMF KeyAdministrator can configure the timeout between conference Chairperson IVR message and the first Chairperson’s DTMF key through TIMEOUT_BETWEEN_IVR_AND_FIRST_DIGIT system flag.

The flag must be manually added to the System Configuration and its value modified as follows:

Flag Name

Value / Description

99 (default) 1-10 0

TIMEOUT_BETWEEN_IVR_AND_FIRST_DIGIT

99 doesn’t stand for the specific timeout value. If 99 is configured, the timeout will be identical to the existing timeout value (same as in previous versions).

Any configured value indicates the timeout in seconds.

If 0 is configured, the chairperson can join the conference immediately after the chairperson message.


Polycom, Inc. 50

Skype for Business Related FeaturesIn version 8.7.1, support for the following features is added:

● RealConnect for Microsoft Office365 via Skype for Business

● Panoramic Layout in Skype for Business

● Add Polycom Participants into Skype for Business Conference Roster

● Skype for Business Audio/Video Participants Count

● Mute Audience

RealConnect for Microsoft Office365 via Skype for Business

Polycom RealConnect enables conferences with both standard endpoints connected to Polycom RealPresence Platform (RPP) and Skype for Business clients connected to a Skype for Business conference on MS AVMCU.

There are two available modes:

● Enterprise mode - RPP is registered to the same Skype for Business deployment hosting the Skype for Business conference.

● Federation - RPP is federated to the Skype for Business deployment hosting the Skype for Business conference, which is mainly useful for Service Providers, as it enables single RPP deployment to support multiple Skype for Business environments.

The RealConnect (cascading with AVMCU) conferencing methodology is now enhanced, to encompass Office365 Online. Through this enhancement, meeting organizers using Office365 Online, can natively invite participants using standard devices (such as H.323/SIP) to the meeting, with no changes made in their regular work flow.

When sending a Skype for Business meeting invite, the sent message contains the Sf URL (see 1 at the sample invite below). This URL is utilized by Sf clients and web-based endpoints, which Click-To-Join to attend the conference.

When the meeting invite organizer has dial-in conferencing capabilities for audio participants, the meeting invite includes a conference ID (2 at the sample below), and a dial-in number.


Polycom, Inc. 51

However, SIP/H.323 endpoints cannot utilize the Sf URL to join the conference. For that purpose, Polycom created the One-Touch-Dial, whose purpose is to pull from Exchange Online the data of the endpoint’s scheduled meetings for the coming day, and in combination with the DMA, produce a One-Touch-Dial-managed VMR, specific to the link in the meeting invite, which is sent to the endpoint.

Two scenarios are supported for connecting standard endpoints with Office365 Online conferences:

● The meeting organizer has no dial-in conferencing capabilities - The meeting invite contains no dial-in number or a conference ID.

● The meeting organizer has dial-in conferencing capabilities - The meeting invite contains a dial-in number and a conference ID.

In the first scenario, only endpoints supporting Click-to-Join can attend the meeting; currently Polycom GS and HDX, and some of the new Cisco endpoints.

In the second scenario, at the time of the meeting, Skype for Business/Skype clients and web clients use the URL to join the meeting, while standard endpoints connect the VMR, which utilizes a separate Click-To-Join mechanism to connect the conference. At that point a conference is established on the RealPresence Collaboration Server using the generated VMR, and matching the link supplied in the meeting invite, to which non-http oriented endpoints can connect.

Non-web endpoints can join the conference provided they are connected to One-Touch-Dial-managed meeting rooms.

Legend

Element Number Description

1 Sf URL

2 Conference ID (applicable when an audio service is enabled)


Polycom, Inc. 52

When a voice service is used, audio endpoints dial the access number supplied in the meeting invite, and are then prompted to enter the Conference ID included there as DTMF code, at which point they are connected to the conference.

In that scenario, the prefix + Conference ID combination may be used as a VMR, provided at least one One-Touch-Dial-managed VMR, even if only a virtual one, is invited to the meeting.

Note, that an organization should define a few dedicated One-Touch-Dial-managed VMRs for that purpose. A single VMR might compromise security/classification purposes within the organization.

Mostly, all meetings initiated by an organizer use the same link. Thus, since the scheduled meetings of the coming day are pooled together, and the VMR is available some time before the meeting is due, invitees from other meeting might join earlier meetings via the VMR. To prevent that, in cases where the Sf organizer wishes to ensure the privacy of a specific meeting, the Organizer should request a specific URL for the meeting, instead of the general URL (determined in the meeting properties).

Panoramic Layout in Skype for BusinessSkype for Business supports sending Panoramic layout in addition to main video layout.

RealPresence Collaboration Server 1800/2000/4000/Virtual Edition supports Panoramic layout only in cascaded conference in order to send multiple speakers to Skype for Business AV MCU in addition to sending the first speaker in the main video layout. Participants connecting to RealPresence Collaboration Server 1800/2000/4000/Virtual Edition can be seen by Skype for Business clients connecting to AV MCU through Panoramic layout. Telepresence (Polycom ITP and CISCO TIP systems) participants can also be sent through Panoramic layout.

Panoramic layout can display on Skype for Business clients connecting to Skype for Business server, which supports MS-SVC and RTV.

The Panoramic layout aspect ratio is 20:3, which is composed by four 5:3 layout cells shown as below:

Panoramic layout consumes one HD720p30 port on RealPresence Collaboration Server 1800/2000/4000/Virtual Edition, and the resource allocation is not affected by LYNC_AVMCU_1080p30_ENCODE_RESOLUTION system flag and resource/video optimization.

Either adding AV_MCU_PANORAMIC_LAYOUT_ENABLED and setting it to YES on RealPresence Collaboration Server 1800/2000/4000/Virtual Edition or selecting Conference Template > Polycom MCU General Settings > Advanced Settings > Enable panoramic layout on DMA can enable the Panoramic layout. For more information, refer to DMA documents on RealPresence Distributed Media Application (DMA) Support Site.

The Panoramic layout displays according to following rules:

● The first speaker displays only in the main video layout, the other speakers display in the Panoramic layout. The only exception is that the first speaker is in ITP/TIP. In this case, the main cell of the ITP/TIP displays in the main video layout, and all ITP/TIP cells (including the main cell) display in the Panoramic layout.

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

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


Polycom, Inc. 53

● If no sufficient resource is available for Panoramic cells or AV MCU doesn’t support Panoramic layout, the participants will display in the main video layout instead.

● Participants appear from center cells to both sides.

● If the Telepresence room is added to the Panoramic layout, the participants in the main cell will be shifted to the left.

● No speaker notation is available.

● Once the Panoramic layout displays, it ignores MLA control to RMX Telepresence room switch and Speaker Priority mode.

Add Polycom Participants into Skype for Business Conference RosterWhereas previously, in a RealConnect conference between RealPresence Collaboration Server and Skype for Business conference, only a single cascaded link was shown in the Skype for Business conference roster, currently all standard Polycom endpoints connected to the RealPresence Platform solution, are now listed in the Skype for Business conference roster. This change, also allows the Skype for Business meeting organizer to individually disconnect these participants.

Two system flags can be added for enabling and configuring the function respectively:

● ENABLE_POLYCOM_EPS_IN_LYNC_ROSTER

Default: DISABLED

Range: DISABLED, ENABLE_IGNORE_ORGANIZER, ENABLE_CONSIDER_ORGANIZER.

ENABLE_CONSIDER_ORGANIZER – enables Polycom endpoints in Lync roster, Polycom endpoints will be disconnected from the conference when it deletes endpoints from the roster.

ENABLE_IGNORE_ORGANIZER – enables Polycom endpoints in Lync roster, Polycom endpoints will not be disconnected from the conference when it deletes the endpoints from the roster.

DISABLED – disables Polycom endpoints in Lync roster.

● POLYCOM_EPS_DISPLAY_NAME_PREFIX_IN_LYNC_ROSTER

Default: “Polycom/”

By configuring the prefix, all Polycom endpoints joining through the RealPresence Collaboration Server are listed with a combined prefix to make their being both recognized and aggregated.

Skype for Business Audio/Video Participants CountBoth the Non-Skype for Business and Skype for Business Audio/Video participants connected to cascaded conference through AVMCU can be counted in the Audio/Video participants indication in the conference layout.

The maximum number of Skype for Business Audio/Video participants can be counted is decided by the value of MAX_COUNT_LYNC_PARTIES system flag. The system flag value range is from 0 to 99, and the default value is 20. If the system flag value is set to 0, no Skype for Business participants will be included in the count.

Mute AudienceIn the AVMCU conference, originator of the conference can selectively to mute all participants or only mute Skye for Business participants by setting


Polycom, Inc. 54

MSFT_AVMCU_MUTE_AUDIENCE_TRIGGERS_MUTE_ALL_BUT_ME_IN_RMX_CONFERENCE to YES (Default) and NO respectively.

● When the system flag is set to YES and originator selects Mute Audience, all participants are muted and originator is un-muted. An audio plays on and notifies all participants that the call is being muted.

● When the system flag is set to NO and originator selects Mute Audience, only Skype for Business participants are muted, Polycom participants and originator are un-muted. No audio notification plays on in this case.

RDP Content Media

Version 8.7.1 adds support for RDP content. For that purpose the RealPresence Collaboration Server infrastructure is enhanced as described below.

Main MCU and Soft Blades - What are They?RealPresence Collaboration Server provides support for RDP (Remote Desktop Protocol) content, a content sharing technology used by Microsoft Lync/Skype for Business, and is an alternate technology to current content sharing methods. Customers with MPMRx or RMX 1800 MCUs can add RDP support for their users by implementing a Modular MCU infrastructure and incorporating soft blades.

For this purpose, Polycom extended the Collaboration Server infrastructure to include:

● A Main MCU - May be either RealPresence Collaboration Server, Virtual Edition, or one of the hardware MCUs, that is, RealPresence Collaboration Server 1800/2000/4000. A hardware Main MCU cannot be populated with MPMx media cards.

● Soft Blades - Polycom soft blade proprietary software installed on a virtual machine (currently only VMWare machines). Each soft blade is assigned to a Main MCU.

The soft blade is aimed at providing the new RDP content media to Microsoft Lync clients, via a Translator residing within it, for each RDP content connection. The purpose of the Translator is translating the standard H.264-based content the RealPresence Collaboration Server to sent to endpoints, into RDP content format, and vice versa.

It is important to note however, that this change in the infrastructure is not imperative should RDP content not be required, and the former infrastructure can be maintained, and is actually the default state of the MCU (see MCU Operation Mode).

Note: Lync and Skype for Business Equivalence

In the following descriptions, Lync and Skype for Business are used interchangeably.


Polycom, Inc. 55

This Modular MCU (MMCU) infrastructure is illustrated below.

MCU Operation Mode

The ENABLE_MODULAR_MCU system flag, along with the IP services existing in the system, indicate the MCU mode with respect to the Modular MCU infrastructure. This flag is visible, and modifying it requires restart for it to take effect.

Possible states:

● NO (default) - If there is no WebRTC IP service, MMCU is completely inactive; if there is - MCU is in Modular MCU mode, and supports internal (residing on Main MCU) translators for WebRTC.

● MIX (recommended) - System is in partial MMCU mode; existing WebRTC IP service enables internal WebRTC Translators, and existing Lync RDP IP service enables external (residing at soft blades) translators for RDP content. If no such IP services exist, the corresponding translator is not supported.

● YES - System is in MMCU mode; existing Lync RDP IP service enables external translators for RDP content. If no such IP services exit, the corresponding translator is not supported.

Modular MCU Implementation AspectsFollowing, are the descriptions for the various aspects necessarily comprising the new MMCU infrastructure:

● Deployment of Soft Blades in a Modular MCU

Note: When upgrading from version 8.6.3 to 8.7.1.

When upgrading RealPresence Collaboration Server 1800/2000/4000/Virtual Edition from version 8.6.3 to 8.7.1, the system flag will not exist in the System Flags dialog. Please manually add the system flag and then reboot the system to make this flag active.


Polycom, Inc. 56

● Modular MCU Components Monitoring

● RDP Content

● Modular MCU Resource Consumption and Management

● Modular MCU Security Aspects

● Modular MCU Logger

● Modular MCU Upgrade Process

Deployment of Soft Blades in a Modular MCUA soft blade is deployed on a virtual machine.

A single Main MCU may control up to 20 soft blades.

Attempting to assign a soft blade to a Main MCU with full soft blade assignment, results in generating a fault event on the Main MCU, indicating the maximum number of soft blades was reached for this particular Main MCU.

Soft Blade Prerequisites

● The virtual machine must use VMWare.

● All the MMCU components should be located on a single premise (co-located).

● For Main MCU and Soft Blade Host server settings, see Virtual Edition Host Server Hardware Profile

To deploy an MMCU from an existing MCU, go through the following phases:

1 To turn your current MCU into a Main MCU, set its ENABLE_MODULAR_MCU system flag value to MIX (recommended) or YES. For more information, see MCU Operation Mode.

Add system flag MMCU_BLOCK_TR_ABORTED MMCU and set the value to NO to enables the recovery mechanism.

2 To install the soft blades, download from Polycom support site the soft blade OVA file (includes Operating System, a console wizard, and a Salt minion).

In the support site, there are two OVA files. The Soft MCU OVA file contains caxis-mcu, whereas the one for the soft blade contains rppbase, and is also significantly smaller sized.

3 Deploy OVA file through vSphere client > File > Deploy OVA Template.

4 Log via putty into the intended soft blade machine via the console wizard, with polycom as both username and password, to display the Minion Setup menu.

Note: OVA File Directives

• Deploy one OVA file at a time.

• If the Main MCU is a Collaboration Server VE, verify both the Main MCU and the soft blade OVA files are the latest, which may entail a required upgrade of the Main MCU.


Polycom, Inc. 57

5 If soft blade IP address is allocated by the DHCP server, skip to next step, otherwise select Exit to main menu in this menu, and there set the static value of the soft blade IP.

For more information, see Network Setup Modes - IP Network Services chapter, in RealPresence Collaboration Server 1800/2000/4000/Virtual Edition Administrator Guide.

6 In the Minion Setup menu, select Minion Configuration, and press Enter.

7 Enter the Main MCU IP address, and press Enter.

A message appears, indicating you should wait for the PFX file, containing the password, from the Main MCU (master).

In parallel, the soft blade appears as a new Translator.<unique ID> on the Main MCU System Monitor with a Pend Authentication status, and no IP address.

Note: Main MCU IP Address

For all RealPresence Collaboration Server acting as Main MCU, use only the Management IP.


Polycom, Inc. 58

8 Once the soft blade IP address appears on the System Monitor, right-click the soft blade, and select Accept.

9 When prompted, enter a password of your choice.

The password you entered is sent in a PFX file to the soft blade, and the soft blade Status changes to Soft Blade Pend Authentication.

10 At the soft blade console wizard, enter the password received in the PFX file (from the previous step), and press Enter.

The soft blade automatically reboots.

In the System Monitor at the Main MCU, the soft blade Status changes to Installing. At this point its deployment begins, and assuming a smooth process through Installing and Initializing, the soft blade Status at the System Monitor becomes Ready, which indicates the soft blade is now operational.

11 Create in your machine the appropriate IP services as required. For more information, see IP Network Services - SIP Servers Dialog

12 Add system flag MMCU_BYPASS_ENABLE_RDP and set it to YES.

13 Select Enable MS RDP content. For more information, see Polycom MCU Video Quality Dialog on DMA

14 Change cascade link (Polycom participants) from Attendees to Presenters in Skype for Business. For more information, see Change a Cascade Link (Polycom Participants) from an Attendee to a Presenter in Skype for Business.

Modular MCU Components MonitoringProvided the Collaboration Server is in MMCU mode, the System Monitor replaces the Hardware Monitor in the RMX Management pane.

Note: Removing a Soft Blade at this Phase

To Remove the soft blade at this point, select Reject; selecting Delete removes it from the Main MCU System Monitor only temporarily, and once another Salt message from the soft blade to the Main MCU is received, the soft blade reappears in the System Monitor.


Polycom, Inc. 59

The Main MCU rhythmically (fixed - every 30 seconds) verifies each of the soft blades proper operation, and monitors its status.

To launch the system Monitor:

1 In the RMX Management pane, click System Monitor to display the list of machines comprising the MMCU.

The System Monitor is displayed, with the Main MCU at the top, followed by the list of its assigned soft blades.

2 Double-click on any of the MMCU machines to view its specific component information as follows:

Double-clicking a hardware Main MCU (Collaboration Servers 1800/2000/4000), results in displaying its Hardware Monitor.

Note: Monitoring Applicability

The monitoring applies to the connection between the endpoint and the Translator, and not to any internal communications.

Legend

Number Description

1 Main MCU

2 Soft blades


Polycom, Inc. 60

Double-clicking a soft Main MCU (Collaboration Server Virtual Edition), results in displaying the VM Monitor, which includes information on the cores, clock frequency, memory, storage, and CPU model.

Double-clicking one of the soft blades, results with displaying the soft blade Monitor, with similar information, as well as the soft blade use percentage, and the number of active Translators.


Polycom, Inc. 61

From this point:

Right-click Active Translators, and select View Properties, or double-click Active Translators, to display the list of Translators on this soft blade, aggregated according to their type.

If the soft blade information cannot be viewed, since the soft blade is in one of the dysfunctional states in the State Machine, an error message pops-up, indicating soft blade details cannot be viewed.

If the soft blade resources are all consumed, an Active Alarm is generated indicating no resources are available on this soft blade.

Click the Up-Arrow on the monitor until the original System Monitor is displayed.

3 Right-click on the Main MCU to display its properties.

Or

Right-click on any of the soft blades to select one of the currently available actions for this soft blade.

Monitoring Guidelines

● Only an Administrator user may perform actions or changes on any of the soft blades.

● All columns specific to MMCU mode are hidden while not in MMCU mode, for Main MCU, soft blades and participants.

Note: Monitoring Dependency on MCU Infrastructure

When not in MMCU mode, the MCU operates as it used to before this infrastructure was created: soft blades are not visible, and Main is replaced by RMX (for HW MCUs).


Polycom, Inc. 62

MMCU Impact on Participant Monitoring

The MMCU infrastructure impacts not only in the general system operation, but also the participant monitoring in general, as well as the Participant Properties - General tab.

When monitoring conference participants, the participant type is indicated by the Alias Name.

Legend

Number Description

1 2222_content (Alias Name rdp_MMcuUser) - A direct RDP content participant.

MMcuUser (001) Prog13s.net (Alias Name mmcuuser001.I) - Its Translator.

2 AS_MCU_Party (Alias Name AS_MCU_Party) - A RealConnect RDP content participant.

AV_MCU_Party (Alias Name mmcuuser002.I) - The RealConnect cascaded link.


Polycom, Inc. 63

In the Participant Properties - General tab, when in MMCU mode, and for participants using a Translator (such as RDP content), the Participant Properties reflect the soft blade IP address, as well as the Translator ID and type, which reflect the endpoint type, thus making the Endpoint Type field at the top (disabled) irrelevant.

Note that a Translator ID equaling 0, denotes a non-Translator participant, since it is either AVC or SVC.

In addition, viewing a specific Translator Properties (or double-clicking it), results in opening the Participant Properties for the participant serviced by that Translator, meaning the information reflects the endpoint and not the translator itself.

Also, no Translator information is displayed for WebRTC participants in 8.7.1, since in that version, these participants are handled by the main MCU, and not by Translators residing in soft blades.


Polycom, Inc. 64

Faults and Active AlarmsWhen an attempt is made to assign a soft blade to a Main MCU with full soft blade assignment, a fault event is generated indicating the maximum number of soft blades was reached for this Main MCU.

In the Main MCU, there are two generated Active Alarms:

● When the Main MCU cannot communicate with the soft blade application, though it does manage to ping it- Soft Blade <name> status has changed to Faulty.

● When the Main MCU cannot communicate with the soft blade application, nor ping it- Soft Blade <name> status has changed to Disconnected.

System Operation Description for Deployment and MonitoringThe MMCU infrastructure operates mostly independently, though at its starting point, it depends on the Administrator user intervention. In addition, the Administrator may intervene at some points, to effect a change in soft blade operation.

The table below describes the soft blade operation, and the states in which the Administrator can intervene to affect it, in the form of a State Transition Machine (STT).


Polycom, Inc. 65

Soft Blade Monitoring States

Soft Blade State State MeaningSoft Blade/Administrator Operation While in State Soft Blade New State

Authentication Phase

Pend Authentication

Soft blade awaits Administrator password.

Administrator performs Accept, and enters password.

Soft Blade Pend Authentication

Administrator performs Reject. Rejected

Administrator performs Delete.

Note: If the console wizard is active at the soft blade, the soft blade re-appears in System Monitor (Salt ping). Use Reject for complete deletion.

Soft blade erased **


Soft blade awaits Administrator password at soft blade.


Installing

Administrator performs Reject. Rejected

Administrator performs Delete. *** Soft blade erased **

RejectedSoft blade awaits the Administrator next action.



Administrator Delete. Soft blade erased **

Operational Phase

InstallingThe Soft blade installation is launched

Installation is successfully completed. Initializing

Installation fails. Faulty

InitializingInitializing the Soft blade

Initialization is successfully completed. Ready

Initialization fails. Faulty (ping)

Disconnected (no ping)

ReadySoft blade is operational.

Administrator performs Restart *** Ready (on success)

Faulty (on failure)

Administrator performs Disable. * Disabled

No communication with Blade, ping Faulty

No communication with Blade, no ping Disconnected


Operational Phase Error Handling

DisabledOngoing conferences continue, no new ones.

Administrator performs Enable. Ready



Polycom, Inc. 66

Initiating a Restore to Factory Defaults operation on a soft blade, results in the soft blade requiring re-authenticating before resuming its normal operation (see the Pend Authentication state in the State Machine above).

Using Backup of an operational MMCU, to Restore on a different machine, requires re-authentication of the assigned soft blades.

MMCU Components Restart

The MMCU system strives to return to the state it was in at the point of restart, or improve it, whether the restart was performed on the Main MCU or on one of the soft blades.

The most significant point of improvement being when a soft blade had a Disconnected status before its restart, and could be pinged right after it, in which case it goes through the process described above from its starting point, and ends either as Ready or Faulty.

There is however a single irregular behavior, if the soft blade was in Soft Blade Pend Authentication state prior to the Main MCU restart. In this case, following this restart, due to the lack of Salt ping, the soft blade is perceived by the Main MCU as Disconnected, and is displayed as such. Thus, once the Administrator enters the password at the soft blade, the soft blade is ready to continue from Soft Blade Pend Authentication (and not from Disconnected), and its state becomes Installing.

Disconnected

No communication with soft blade, and no ping.

Generates Active Alarm indicating soft blade status changed to Disconnected.

Soft blade is alive following restart, but installation is not complete.

Installing

Soft blade is alive following restart, and installation is complete.

Initializing

Administrator performs Delete, which turns off the Active Alarm.

Soft blade erased**

Faulty

No communication with soft blade but ping succeeds. Internal recovery ran to verify installation and configuration.

Generates Active Alarm indicating soft blade status changed to Faulty.

Administrator performs Restart for a service, and restart is successfully completed. ***

Ready (on successful Restart)

Faulty (on failed Restart)

Administrator performs Rescue, triggering re-installation of internal package followed by reboot.

Installing

Administrator performs Disable. Disabled

Administrator performs Delete. Soft blade erased**

No ping Disconnected

** Once a soft blade is erased, re-adding it requires re-authentication from the starting point.*** Warning to ongoing conferences is generated.

Soft Blade Monitoring States

Soft Blade State State MeaningSoft Blade/Administrator Operation While in State Soft Blade New State


Polycom, Inc. 67

During restart of:

● Soft Blade - The Main MCU modifies the Soft Blade state to Disconnected.

● Main MCU - All conferences and Translators, on both Main MCU and soft blades, are disconnected.

IP Address Management

The soft blades initial IP address is provided by the DHCP server. An Administrator user is then required to log on using the console wizard, and configure the Main MCU (Salt master) IP address mode, either as DHCP or as static.

However, the soft blades management is independent of their IP addresses. Therefore, following restart, though some of the soft blades may be assigned a new IP address by the DHCP server during their Initialization state, the Main MCU is not affected by that change - the soft blades are recognized in the system, and are assigned a state relevant to their state before restart. For example, if a soft blade already passed both authentication states, it does not require re-acceptance by the Administrator.

If a new soft blade is assigned an IP address which was previously assigned to a currently Disconnected soft blade, it goes through the authentication phases from the beginning. The Disconnected machine, when it becomes operable, is reassigned a new IP address by the DHCP server, though during its Disconnected state it does appear in the list of soft blades in the UI.

When a soft blade is re-assigned to an alternate Main MCU, until deleted from its original Main MCU, it is considered as Disconnected by this MCU.

RDP Content

Skype for Business clients can share content using a Remote Desktop Protocol (RDP). Standard endpoints does not support RDP and hence it uses the H.239 (for H.323 endpoints) or BFCP (for SIP endpoints). In order to enable content sharing between Skype for Business clients and standard room endpoints, RealPresence Collaboration Server can be used (when configured to work in Modular MCU mode).

Two use cases are supported for content sharing:

● RealConnect Mode - Collaboration Server calls the AS-MCU

● Direct Call Mode - Lync client calls a VMR

Both cases require RealPresence Collaboration Server configured to MMCU mode.

RealConnect Call Mode

RealConnect’s capability to translate between RDP and H.264, and vice versa, is embedded in the MMCU and is referred to as RealConnect Mode or Gateway Mode. A single transcoding resource, between the VMR (Polycom conference) and the ASMCU is required. This resource resides on a soft blade MMCU.

Note: IP Address Type

Currently, only IPv4 address type is supported for soft blade IP addresses.

Note: IP Address Type

Currently, only IPv4 address type is supported for soft blade IP addresses.


Polycom, Inc. 68

● RealConnect Mode is used to connect the ASMCU the Polycom VMR (Virtual Meeting Room).

● If the are insufficient resources for a RDP-content translator, content will not be shared between Polycom endpoints and Lync clients.

● In the event of soft blade failure the MCU will recover RealConnect content calls if another soft blade is available.

● In the event of MCU fail-over, RealConnect content calls will be recovered immediately after the MCU recovers the A/V RealConnect call.

Direct Call Mode

RDP content can be shared in the Direct Call mode, in which Skype for Business clients share the content directly and Polycom clients still share the RDP content through RDP translator in the Soft blade.

● A transcoding resource is allocated to each direct call from a Skype for Business client to the VMR.

● The MMCU allocates transcoding resources to RDP content for each Skype for Business client connected to a VMR

● DMA routes Skype for Business content calls to the same MCU where the A/V call is being hosted.

● In cases of MCU fail-over, only non-encrypted Skype for Business A/V calls can be re-established. Recovery requires a re-invite, including the exchange of keys for the encrypted call, which is not supported by Skype for Business clients.

● If there are insufficient resources for a RDP-content translator, whether content is sent through the people video channel depends on the setting of the Send Content to Legacy Endpoints check box in the Profile - Video Quality dialog. In this case, Skype for Business clients will not be able to share content.

● RDP Content calls are not supported on MMCUs that do not have an encryption license.

● In the event of soft blade failure the MCU will recover Direct Calls if another soft blade is available. If the content was being shared by the Skype for Business client, the content will be shared again by the Skype for Business client.

Common Behavior - RealConnect / Direct Call Modes

● In the event of MCU failure DMA will attempt to find another MMCU on which to create the content stream. For RealConnect calls there are two calls to the Skype for Business side of the topology. The first call is to subscribe or notify. The second call, created when content is shared, is to establish the content media channel. The subscription call is created when the a/v call is created. If successful, a Content Gateway call is established immediately after the call to the ASMCU is established. If another MMCU is not found, the conference is created on a non-modular MCU without RDP content capability resulting in Polycom and Skype for Business clients not being able to share content.

● ICE credentials are updated on the system in both RealConnect and Direct Call modes for both on-premise and federated environments.

● Ongoing calls may be disconnected, however the system recovers automatically from the following failures:

ICE Server

Skype for Business Server

Note: Transcoded content call

The transcoded content call reaches the main MCU.


Polycom, Inc. 69

Enabling RDP Content

Enabling RDP content needs configurations on DMA and IP Network Service.

Polycom MCU Video Quality Dialog on DMA

Select Enable MS RDP content on DMA through Polycom MCU Video Quality > Content Video Definition.

IP Network Services - SIP Servers Dialog

If the SIP Server Type is configured to Microsoft, an additional information box for the Translator SIP Proxy is displayed.

hn

Note: Enable MS RDP on DMA

Before enabling MS RDP on DMA, make sue no ContentConnect server is configured in DMA.

Number Parameters Values

1 SIP Server Type Microsoft

2 Transport Type TLS


Polycom, Inc. 70

Change a Cascade Link (Polycom Participants) from an Attendee to a Presenter in Skype for Business

Content can only be shared by the cascade link who are presenters and not attendees in the Skype for Business.

To change a cascade link from an Attendee to Presenter in Skype for Business:

1 Click Meet Now

2 Click Invite More People and select cascade link of VMR for the meeting.

3 Click Open Participant List, verify if VMR cascade link is in the Presenters list.

4 If VMR cascade link is in the Attendees list, right-click the cascade link from the list and select Make a Presenter.

Monitoring RDP Content

Both RealConnect (RDPConnect) and Direct Call Mode (RDPDirect) translators can be monitored using the System Monitor.

For more information about Monitoring see Modular MCU Components Monitoring

Modular MCU Resource Consumption and ManagementSome changes in the resource consumption and resource report result from the changes introduced into the Collaboration Server infrastructure.

There is an inherent difficulty in estimating the resource usage, since it may be due to either one of the Main MCU, one of the soft blades, or both.

In addition, the Translator consumes soft blade cores according to the type of media/endpoint.

Resource Weight Factoring in Resource Management

A resource weight is the amount of resources required for any Translator of a certain type. Resource weights are constant across the MMCU system per each Translator (media/endpoint) type, and a table containing these values resides at the TC, to enable resource allocation planning.

In addition, each Translator consumes H.264 resources of identical resolution on the Main MCU.

The TC allocates Translators on each soft blade, taking into account the resource weight of the required Translator type, until a pre-defined upper threshold is reached, at which point Translators allocation moves to the next soft blade in the system. Each soft blade reports to the TC on its own resource availability/usage, thus the TC acts as a resource manager for the Translators (only).

3

RDP-content data:

Parameters Translator SIP Proxy Values

Server Address DMA server name/address

SIP Authorization Name Optional. DMA server authorization name.

SIP Password Optional. DMA server password

Number Parameters Values


Polycom, Inc. 71

The Main MCU resource management remains as it was.

Resource Report

Two separate resource reports are available, as before, only now they are separated into a report on the Main MCU, and a report on the soft blades assigned to that Main MCU. These reports are:


Polycom, Inc. 72

● The bar-graph representation:

This report can be viewed by selecting, in the RMX Menu, Administration > Resource Report.

● Constant resource report at the Collaboration Server Status Bar:

Resource Report With no Translators Used on Soft Blade

Resource Report With Translators Used on Soft Blade

These numbers are reported for resource balancing purposes via XML API, as before.

Note that in the Main MCU, AVC HD720p30 is used as the measuring unit in the resource report, whereas in the soft blades, cores in terms of GHz is used, which allows for easy calculation of the number of soft blades requiring allocation.

Note: Voice Resource Report

The previous Voice resource report is removed, since it is only applicable to systems with MPMx media cards, which is not supported from version 8.6.


Polycom, Inc. 73

Upon each soft blade initiation, its computing power is calculated, and is aggregated by the TC with the computing power of the other soft blades in the MMCU, to yield the general soft blades resource pool usage information.

The TC also keeps track of the resource pool on the Main MCU, to be able to pass on this information to external entities.

Port Usage for Skype for Business Client

Following table shows port usage for Skype for Business client.

Legend

Number Description

1 Soft blades aggregated resources

Note: Disabled Soft Blades Resources

A Disabled soft blade is presented as having 0 resources, unless Translators were already running on it at the point of Disabling, in which case it’s maximum resources are considered as the used resources at that point.

Port Usage for Skype for Business Client by Resolution

Resolution Port Usage

720p 1

1080p 2

Note: 1 additional audio port will be consumed per participant for the connection between RealPresence Collaboration Server and Soft Blade.


Polycom, Inc. 74

Modular MCU Security AspectsThe MMCU model ensures security is preserved in a few levels:

● Salt and soft blade APIs

● SIP signaling connections - Both between the Collaboration Server and the soft blade, and between the soft blade and the DMA.

● Media - Both between the Collaboration Server and the soft blade, and between the soft blade and the endpoint.

When the Administrator wants to accept a soft blade currently in Pend Authentication state, it is required to install a self-signed certificate (default) with the properties:

● Common Name - The host name to which the certificate was generated. Since this is a self signed certificate, this name is the soft blade name as it appears in the soft blade monitoring.

● Certificate expiration period - 10 years.

The Administrator then enters the soft blade password.

All unused ports are blocked by the firewall. The tables below list the ports in use, both in the Main MCU and in each of the soft blades.

Note: Maximum Skype for Business clients in the direct call mode

If not limited by the resources or licenses, RealPresence Collaboration Server can support maximum of 100 Skype for Business clients in the direct call mode.

Main MCU Open Ports

Port Number Usage State

TCP 22 ssh Open

25 smtp

Filtered (answer TCP syn)110 pop3

52072

UDP 123 ntpOpen / Filtered

81 ports

API 1st Connection 4505,4506 Salt APIUnconfigurable

API 2nd Connection 10020 Soft blade API


Polycom, Inc. 75

Modular MCU LoggerThe Logger aggregates and standardizes the logging at the soft blade, or as they are sometimes related to, Translator Machines. It also allows the Main MCU to gather the Translators/soft blades logs from a centralized gathering point.

Logger Guidelines

● The Main MCU writes logs into the regular Main MCU log file, including API messages sent to the soft blades.

● All logging operations use the same infrastructure elements, thus are consist across the MMCU various components.

Logs Format

In all soft blades, logs are formated as

D:<Date and time stamp> E:<Entity> P:<Process> U:<Unit> L:<Log level> SN:<#> Lcnt:<code location>

where:

Soft Blade Open Ports

Type Port Number Protocol

RTP/RTCP 49152 - 65535 UDP / TCP

SSH 22 TCP

SIP 5060 UDP / TCP

SIP TLS 5061 UDP / TCP

API 1st Connection32768 - 61000 TCP

API 2nd Connection

Log Component Description and structure

Date and time stamp Date and time of log generation, in the format dd/mm/yy-hh:mm:ss.ms

Entity System entity generating the log

Process Soft blade application process generating the log

Unit Unit generating the log


Polycom, Inc. 76

Logs generated with ERROR/FATAL logging level are immediately sent to the Logger of the TC at the Main MCU as faults, as well as logged on the soft blade.

Logging Configuration

All logging performed at the soft blades, share the same configuration, especially their logging level, and are configurable via the Main MCU, although the Main MCU may use different logging configuration. Nevertheless, the system initial state, is that of the Main MCU sharing its default logging configuration (INFO) with the soft blades.

In normal situations, INFO is the logging level. To obtain detailed logs, logging level at both the Main MCU and the soft blades should be set to TRACE/DEBUG.

Logging volume varies according to the logging level. However, it is designed so that, assuming a total of 15GB storage, approximately one month worth of logs can be stored.

To determine the configuration settings for the soft blades:

1 In the Collaboration Server main menu, select Administration > Tools > Logger Configuration.

Log level Logging level at the point of log generation. One of:

• TRACE

• DEBUG

• INFO (default)

• WARN

• ERROR

• FATAL

# Log message serial number

Code location Code file name, and line number

Log Component Description and structure


Polycom, Inc. 77

2 Click Customize for the Local Log File.

A new check-box for soft blades logging is displayed, with the same logging level and the same processes selected. You can modify both the logging level and the process selection.

3 Click OK to save and return to the Logger Configuration dialog, and then OK to exit.

Logs at the Soft Blades

The soft blade log files are located under /opt/polycom/Translator/Logs.

There are two types of logs at the soft blades:

● Call logs

● General logs

Call Logs

Each such log file is dedicated to a single participant in a conference, and is named

Log_SN<log serial #>_FMD<1st msg date>_FMT<1st msg time>_LMD<last msg date>_ LMT<last msg time>_C<Conf ID>_P<Party ID>_SZ<size>_SU<1st log in process? Y/N>_CF<Compression format>_NFV<File version>_ RT<File retrieved? Y/N>_<process name>.log

Example: Log_SN0000000023_FMD04112015_FMT142815_LMD04112015_LMT142815_C0000110_P0000001_SZ0000130_SUY_CFzlib_NFV02_RTN_WebRtcWrapper50103.log

Each file is limited to 1MB, thus there may be more than one file for a conference-participant combination.

Note: Salt Logs Location

Salt logs are stored in a dedicated folder under that location.


Polycom, Inc. 78

General Logs

All logs pertaining to information unrelated to conferences. Upon soft blade startup the first log file is created. Each such log file is limited to 1MB, and is named

Log_SN<log serial #>_FMD<1st msg date>_FMT<1st msg time>_LMD<last msg date>_ LMT<last msg time>_SZ<size>_SU<1st log in process? Y/N>_CF<Compression format>_NFV<File version>_RT<File retrieved? Y/N>_<process name>.log

Example: Log_SN0000000023_FMD04112015_FMT142815_LMD04112015_LMT142815_ SZ0000130_SUY_CFzlib_NFV02_RTN_Container50103.log.

Logging volume varies according to the logging level. However, it is designed so that, assuming a total of 15GB storage per soft blade machine, approximately one month worth of logs can be stored.

Filtering Logs

● Logs from all MMCU machines, may be filtered according to any combination of the following criteria:

A specified time stamp/interval - Mandatory

A specific conference

A specific participant in a conference

● The resulting log files are stored in the Main MCU, under MMCU/Logger/Collector FS as follows:

CollectInfo_<begin date&time>-<end date&time>.tgz - A log file for the Main MCU.

A folder named Blades, for log files filtered from all the soft blades. Under this folder there are:

Folders named Translator.<ID>, for each of the soft blades log files.

A folder named Translator.777777, for log files filtered from the local Translators (i.e. Translators residing on the Main MCU, such as for WebRTC).

● Each of the filtered log files is limited to 100MB.

● Furthermore, when a filter specifies a conference/participant, for which one of the involved soft blades is down, the user is notified that the returned logs are partial (for a conference), or cannot be supplied (for a participant in the specified conference).


Polycom, Inc. 79

To filter logs according to conference and/or participant:

1 In the RealPresence Collaboration Server main menu, select Administration > Tools > Information Collector.

2 Determine the time frame of the desired logs.

3 To filter the logs of a specific conference beginning within this time frame:

a Click Select Conference.

b Select the conference to use for the filter, and click OK.

The time frame you previously selected, is modified to that of the selected conference; for an ongoing conference, the end time is determined to be the current time.

4 To filter the logs of a specific participant in the selected conference:

a Click Select Participants.

b Select the participant to use for the filter, and click OK.

5 Determine the location in which the filtered logs are stored, by entering it or via Browse.

6 Click Collect Information to generate the appropriate log files.


Polycom, Inc. 80

Error Handling

Should a failure occur at one of the soft blades - from best case scenario of the Collaboration Server application level, down to the worst case scenario of the soft blade machine termination - all retrievable log files are sent to the Main MCU, accompanied by a notification listing the files which could not be retrieved.

Modular MCU Upgrade ProcessThe MCU and its soft blades can be upgraded together with one upgrade software (*.bin for RMX 1800/2000/4000, *.upg for RealPresence Collaboration Server, Virtual Edition), all soft blades will be upgraded automatically during the MCU reboot.

The whole procedure will take extra minutes in this release, and you can monitor the soft blades upgrade status on the MMCU System Monitor pane.

To upgrade the MCU from any versions earlier than version 8.5 to version 8.7.1, the intermediate upgrade to 8.5, 8.6 or the maintenance releases of both versions is needed.

Virtual Edition MCU Upgrade Storage Requirements

If the MCU is RealPresence Collaboration Server, Virtual Edition, sufficient storage for MCU and its soft blades is required:

●For MCU storage requirements, see Virtual Edition Host Server Hardware Profile.

● For soft blades storage requirements, see Soft Blade Prerequisites.

In case of insufficient storage, the upgrade will not start, and an active alarm “Insufficient storage space for upgrade” will be raised.

Monitor Soft Blades Upgrade

The MCU and its soft blades upgrade process can be monitored through the RMX Management > MMCU System Monitor.

● If soft blades upgrade normally, Upgrading displays in each soft blade row.

Following table shows other soft blades status and behaviors:

Soft blade status and expected behavior

Status Behaviors

Pending authentication No action.

Once the MCU is authenticated it will be upgraded.

Soft blade pending authentication

No action.

Once the soft blade is authenticated it will be upgraded.

Rejected Remain rejected.

Initializing Start upgrade.


Polycom, Inc. 81

● If any soft blades failed to be upgraded, Upgrade failed displays in the MCU row.

During the MCU reboot process, once the MCU is verified as an invalid system, the MCU will use the previous version software instead and issue an active alarm, in this case, the soft blades will be downgraded automatically to match the MCU version.

You can manually install the new version software on soft blades, which failed to be upgraded. For information of installing soft blades, see Deployment of Soft Blades in a MCU.

Only the soft blades are upgraded successfully will work actively with the MCU.

Ready Start upgrade.

Faulty Start upgrade.

Disconnected No action.

Disabled Start upgrade.

Soft blade status and expected behavior

Status Behaviors

Corrections and Known Limitations

Polycom, Inc. 82


Corrections between Version 8.6 and Version 8.7.1

Collaboration Server 1800/2000/4000/Virtual Edition Version 8.7.1 - Corrections

Issue ID Category DescriptionDetected in

Version

BRIDGE-23491

Audio When connecting Group Series 500 to RealPresence Collaboration Server (MPMRX), lip-sync error and audio clipping occur. Setting ENABLE_SELECTIVE_MIXING to Yes causes audio clipping in some cases.

8.6.1

BRIDGE-13083

Audio Audio from EX90 endpoint ceases after session refresh (15 minutes after connection). Endpoint is registered to VCS and connects to VMR via external IVR VEQ.

8.3.2

BRIDGE-18483

Audio The NoiseBlock feature malfunctions during audio cuts. 8.5

BRIDGE-21123

Audio Endpoints do not receive audio after Audio Codec is changed after RE-INVITE on RMX with MPMx media cards

8.5.3

BRIDGE-21122

Audio When following re-invite, the audio codec is modified by the Collaboration Server, endpoints do not receive the audio.

8.5.3

BRIDGE-22535

Audio Random participant can be heard by some participants but not heard by others in the same VMR.

8.5.3

BRIDGE-21065

Cascading Auto Scan stops functioning during a Cascading Conference on RealPresence Collaboration Server.

8.5.3

BRIDGE-21429

Cascading In an 4Mbps AVC Only H.264 cascade-optimized conference with 59 endpoints on each MCU running at a 1Mbps line rate, after a 15 minute delay, content can be shared but on the other side of the cascade a black screen appears, or content cannot be shared until some endpoints disconnected.

8.5.2

BRIDGE-22417

Cascading In an audio-only cascading conference, RealPresence Access Director participant needs to be set to Slave to make audio flow is bidirectional; otherwise the audio flow will be unidirectional to the default Master (automatically set).

8.6.3

BRIDGE-22638

Cascading In a cascaded conference, sharing content consumes excessive bandwidth then line rate configured in conference profile.

8.5.2

BRIDGE-22918

Content In a cascading link, when a lecture is set to “Change To Content Token Owner”, other participant can still share content.

8.5.4HF


Polycom, Inc. 83

BRIDGE-21384

Content Polycom GS 500 in a conference fails to share content to Tandberg, Aethra and V700 endpoints in another conference with same conference profile.

8.5.3HF

BRIDGE-22943

Content In a conference with 1920 kbps line rate, content shared from Sony PCS-XG100 is not displayed on both near-end and far-end.

8.5.4

BRIDGE-21828

Content Sharing content to participant in a cascading conference fails, a blue screen displays instead.

8.5.3

BRIDGE-21699

Content When content is being shared in a Polycom RealConnect conference, a participant joining the conference causes content stops to all participants including LifeSize unit, and no one can send content.

8.6.2

BRIDGE-20177

Content Content shared via RealPresence Web Suite, is displayed twice to RealPresence Web Suite clients (if Legacy content is enabled on the RealPresence Collaboration Server).

8.6

BRIDGE-22478

Content Content cannot be shared in HD1080p when there is a mix of participants with and without HD1080p enabled in same conference on RMX using MPMRx media cards.

8.6.2

BRIDGE-21965

Content Video Quality deteriorates after sharing Content when using RMX with MPMx media cards.

8.5.2

BRIDGE-21280

Content H.263 Content transmission rate is too slow for endpoints connected at 128kbps on RMX1800 and RMX using MPMx media cards.

8.5.3HF

BRIDGE-23193

Content After moving a Lync and CSS client from a conference with password to another conference without password, while a Group Series endpoint is sharing the content in the latter conference, the Lync and CSS client cannot receive the content until the Group Series restart the content..

8.5.4

BRIDGE-23247

Diagnostic When logging in RealPresence Collaboration Server (MPMRx) with password “&aaaa9999%aaa9999#”, Hardware Monitor displays abnormal.

8.5.4

BRIDGE-21601

Diagnostic After a Logger Diagnostic File has been retrieved, and implementing the retrieving again, “Error in retrieving log file” message is reported.

8.6.2

BRIDGE-22286

Encryption HDX in 384K RMX call shows packet loss on transmitted audio and video, when Siren22 audio protocol is used in a 384 kbps conference with AES encryption ON, when using RMX with MPMx media cards.

8.5.3

BRIDGE-22424

Encryption Call from HDX via Acme SBC to DMA VMR using “Encrypt When Possible” setting fails with call rejected by RMX.

8.5.4



Version


Polycom, Inc. 84

BRIDGE-22713

Gateway When both audio and video participants indications are enabled for RealPresence Collaboration Server, video participants joining from another Gateway in the VMR are not counted and shown on other participant’s screen. Audio Gateway participants are counted correctly.

8.6.2

BRIDGE-21592

Gateway GW service ignores ** in dial string to route call to ISDN-voice connection and instead prompts for destination number on RMX with MPM+ media cards.

8.6

BRIDGE-22920

Gateway Gateway call from SIP endpoint to ISDN-Video endpoint fails. 8.6.3

BRIDGE-23415

General After a conference profile is created without Telepresence selected, and a participant’s layout is changed from conference layout to personal layout, RealPresence Collaboration Server (MPMRx) prompts error: “Failed to delete participant: Personal layout is managed internally in Telepresence mode.”

8.6.3

BRIDGE-23802

General Endpoints undergo crash and get disconnected from RealPresence Collaboration Server.

8.5.6

BRIDGE-21604

General Core Dump file generated on ConfParty on RMX using MPMx / MPMRx media cards. No calls were lost.

8.5.3

BRIDGE-22399

General Core dumps seen in Faults List on RMX using MPMx media cards. 8.5.3HF

BRIDGE-22967

General RealPresence Collaboration Server, Virtual Edition fills its root filesystem fast until a reboot.

8.6.3

BRIDGE-22759

General Unable to change personal layout in participant’s properties dialog. 8.6.3HF

BRIDGE-23067

General After configuring TCP Fixed Ports on IP Network Service of RMX 4000, RMX 4000 fails to update the configuration and "Invalid TCP Ports" alarm is generated.

8.6.3

BRDIGE-23024

General "Registration failed for some Conference" alarm shows every 15 minutes on

8.6.3

BRIDGE-23245

General After a RMX 1800 without DSP card being upgraded from v8.5.1.16 to v8.6.3.29, the system shows itself with three DSP cards incorrectly.

8.6.3

BRIDGE-22926

General After RealPresence Collaboration Server dialing out to an endpoint and the endpoint user selecting “ignore incoming call” manually, the RealPresence Collaboration Server still attempts to redial endpoint.

8.5.3

BRIDGE-22445

General RMX using MPMRx media cards rebooted with message "Internal MCU resetMcmsDaemonMcmsDaemon reset due to WD policy decision: Process failed [0:0] : ConfParty".

8.5.3HF



Version


Polycom, Inc. 85

BRIDGE-591

General When selecting one of the last three colors from the Message Overlay color drop down menu, the color selection is not implemented during the conference.

7.8.0

BRDIGE-19443

General Green and purple artifacts on AVC endpoints’ layout following a speaker change from SVC to AVC, in a 2M mixed conference with 80% load (whether line rate or configurations), and 5 SIP SVC plus 11 H.323 AVC endpoints connects.

8.6

BRIDGE-8365

General When changing the HD720p60 Resource Optimize values, Kbps values for Base Profile changes from 1920 to 2560 and High Profile changes from 2560 to 2048.

8.2

BRIDGE-22727

General Disconnected participant remains in Meeting Room. Meeting Room cannot be deleted and additional participants cannot connect to Meeting Room when using RMX with MPMx media cards.

8.5.4

BRIDGE-22590

General Core dump generated and Major Status Alarm raised: “Initialization of ice stack failed SipProxyIce Server Unavailable”, ongoing calls were impacted when using RMX with MPMx media cards.

8.5.4HF

BRIDGE-21898

General A major Alarm “No LAN connection port 1”, though Multiple Network Services is enabled, and only three ports are configured/connected.

8.5.3HF

BRIDGE-22096

General RealPresence Collaboration Server drops all calls, and “ 8751ConfPartyMedia is recovering” displays in Fault List.

8.6

BRIDGE-22547

General H.264 high profile check box is not shown on General tab of Conference profiles when creating the New Conference Profile.

8.6.3

BRIDGE-22701

General RealPresence Collaboration Server, Virtual Edition uses too much disk space, and the free space keeps decreasing. Major alarm reporting the remaining free disk space displays in Fault list.

8.6.2

BRIDGE-21567

General After configuring a new signal/media IP on RMX then restarting it, the system becomes inaccessible until a hard reboot.

8.5.2

BRIDGE-22622

General After the conference ID is deleted and meeting room is saved, “Internal communication error” displays followed with RMX 1800 restarting.

8.6.2

BRIDGE-17718

General On RealPresence Collaboration Server 1800, when Diffserv is selected as the QoS type, the documented default DSCP values are not actually used.

8.6

BRIDGE-21177

General H.323 call doesn’t connect to RMX when RiverBed Steelhead WAN Optimizer is in use.

8.5.3

BRIDGE-22513

General Keep- Alive fails and DSP crashes when using RMX with MPMRx media cards.

8.5.3

BRIDGE-22524

General / Meeting Room

Meeting Room “Duration” parameter is not stable on RMX hardware and virtual MCUs.

8.5.4



Version


Polycom, Inc. 86

BRIDGE-22649

General When a user displays the Click & View menu and disconnects, the next caller to connect sees the Click & View menu when using RMX Virtual Edition MCU.

8.6.3

BRIDGE-22340

General ICE does not function if the Management DNS setting is not configured on RMX using MPMx media cards.

8.5.4

BRIDGE-21125

General H.323 participants disconnected with MCU INTERNAL PROBLEM alert on RMX with MPMx media cards.

8.5.6

BRIDGE-21402

General Participants Status is “Disconnecting” in the Conference List, and the conference cannot be deleted when using RMX with MPMx media cards.

8.5.2

BRIDGE-21651

General Core dump of MFA is generated. 8.5.3HF

BRIDGE-22631

General RMX 2000 with MPMRx media cards rebooted and came back online following a system crash and Core Dump.

8.6.3

BRIDGE-22630

General RMX 2000 with MPMRx media cards rebooted and came back online following a system crash and Core Dump.

8.6.3

BRIDGE-21161

General Core dump was generated by RMX. 8.6

BRIDGE-22469

H.323 Core Dump generated when RMX using 2 MPMX cards crashed during conference.

8.5.3

BRIDGE-21520

Hardware After Multiple Service is configured on RMX 4000 system, RTM-LAN ports status in Hardware Monitor is not correct. The ports status is Standby instead of Active.

8.5.3HF

BRIDGE-22749

HD In a multi-participant conferences on RealPresence Collaboration Server 2000, using resolutions higher than 720p, a thin pink line randomly appears on participants video, despite speaker toggling.

8.5.3 HF1

BRIDGE-5325

Interoperability Green screen is displayed for 2 - 3 seconds when connecting HDX 9000 endpoint to RMX using DTLS Encryption with AES 128 SHA1_80. Call then proceeds normally.

8.1

BRIDG-7056

Interoperability CTS endpoint disconnects from the conference after the performing hold and resume while the conference was locked/ secured by the conference chairperson.

8.1.6

BRIDGE-18913

Interoperability Call bit rate setting in Conference Profile on a RMX Virtual Edition MCU does not correctly limit the call connection bit rate in calls from a HDX endpoint.

8.4

BRIDGE-23314

Interoperability When an OTX call is connected to the RealPresence Collaboration Server (MPMRx), which is in Speaker Priority mode, the active speaker’s one-camera room view displays in each of the three screens.

8.5.3



Version


Polycom, Inc. 87

BRIDGE-23278

Interoperability Call from HDX via ACME SBC to DMA VMR with encryption set to whenever available fails because the call is rejected by the RealPresence Collaboration Server.

8.5.4

BRIDGE-23449

Interoperability Call speed and resolution mismatch between RealPresence Desktop and VSW high profile of RealPresence Collaboration Server.

8.5.10

BRIDGE-15236

Interoperability At times, Collaboration Server VE connects Cisco endpoints over H.323 to a 4M CP conference, with these endpoints connected as "connected with problem."

8.5

BRIDGE-20916

Interoperability WebRTC calls to a bridge fail with Chrome 45 (Canary), and users receive a “You have been disconnected from the meeting” message

8.6.1

BRIDGE-21195

Interoperability WebRTC call using Chrome 45 disconnects during transition from full-mesh mode to bridged mode.

8.6.2

BRIDGE-22909

Interoperability Importing address book from one RealPresence Collaboration Server to another will result in various groups no longer present in the address book.

8.5.10

BRIDGE-23227


8.5.3

BRIDGE-23154

Interoperability RealPresence Collaboration Server loses connection with RealPresence DMA, all calls drop.

8.6.3

BRIGE-23227


8.5.3

BRIDGE-13131

Interoperability Polycom CX500 and CX600 IP phones disconnect after joining a call via dial out from a meeting room created on RealPresence Collaboration Server (RMX) 1800.

8.4

BRIDGE-22387

Interoperability Hung calls experienced from MGC cascade, and participant or conference with a participant cannot be deleted when using RMX with MPMRx media cards.

8.5.3HF

BRIDGE-21365

Interoperability RPX or TPX ITP room containing HDXs as the last participant isn't automatically terminated from the conference on RMX 2000 when using RMX with MPMx or MPMRx media cards.

8.5.2

BRIDGE-16755

Interoperability RPIS is registered to CUCM and RMX is registered to RealPresence DMA. Rarely, after RPIS dials into a RMX conference configured with Prefer TIP and Speaker Priority, the RPIS transmits 720p video primarily but transmits 1080p video secondarily.

8.4



Version


Polycom, Inc. 88

BRIDGE-18777

Interoperability In a combined RealPresence Collaboration Server 4000 and CUCM (Cisco MCU) conference, CTS and TX TelePresence endpoints move from a Virtual Entry Queue (VEQ) to a Virtual Meeting Room (VMR), both on the RealPresence DMA, fails - TX was disconnected, and CTS video froze.

8.6

BRIDGE-21317

Interoperability WebRTC calls to a bridge fail with Chrome 46 (Canary), and users receive a “You have been disconnected from the meeting” message.

8.6.1

BRIDGE-21426

Interoperability Cisco MXP endpoint does not receive Content if it joins an RMX Meeting Room that already has Content shared by another Cisco endpoint into the conference on RMX with MPMx media cards. Issue gets solved by stopping and re-sending Content.

8.4.2

BRIDGE-21458

Interoperability While Content is being shared from the Cisco side during cascading with Cisco Codian MCU and RMX with MPMx media cards, the endpoint on the RMX side displays a blue screen.

8.5.3

BRIDGE-21946

Interoperability UDP Audio/Video ports open after codec fails on RMX with MPMRx media cards.

8.5.3HF

BRIDGE-21714

Interoperability HDX endpoint is disconnected from SVC/AVC conference on RMX using MPMRx media cards.

8.5.3

BRIDGE-18692

Interoperability Sametime Audio Only calls disconnect from RMX with MPMRx media cards.

8.6

BRIDGE-18913

Interoperability Call bit rate setting in Conference Profile on a RMX Virtual Edition MCU does not correctly limit the call connection bit rate in calls from a HDX endpoint.

8.4

BRIDGE-21451

Interoperability CallSignalAddress in ARQ for inter-cluster call is incorrect when using RMX with MPMx or MPMRx media cards.

8.5.2

BRIDGE-22383

IP Second IP network service could not be added using RMX Web Client or RMX Manager on RMX 1800.

8.5.3HF

BRIDGE-23619

ISDN RMX 2000 cannot receive ISDN-Video calls but can receive ISDN-Voice calls.

8.5.4

BRIDGE-21941

ISDN Cellular phone dialing into a conference running on RealPresence Collaboration Server 1800, as an ISDN-voice endpoint via an Entry Queue, does not hear IVR request for password, though message was heard in the EQ, and could DTMF.

8.5.2

BRIDGE-22415

IVR DTMF tones, in phone calls to a Virtual Entry Queue, are not accepted by RMX Appliance and Virtual MCUs.

8.5.4

BRIDGE-6587

IVR In the IVR Service after rebooting a Collaboration Server VE, the “enable welcome message” check box becomes unchecked and the welcome audio message is not played.

8.1.7



Version


Polycom, Inc. 89

BRIDGE-21052

IVR DTMF in calls to a Virtual Entry Queue are not received by RMX using MPMx media cards.

8.5.3

BRIDGE-22458

IVR Cannot delete participant from the Entry Queue when using RMX. 8.5.3

BRIDGE-22591

IVR Participants’ endpoints do not forward the "Invite Participant” DTMF code in ISDN calls on RMX Appliance and Virtual MCUs.

8.5.3

BRIDGE-13130

MPM “Card voltage problem” alarm resulting from removal of MPMRx media card with Normal status from RMX 2000 is not cleared when the media card is reinserted.

8.3 Inc 1, 8.3

BRIDGE-23690

MPM Endpoints are unable to transmit audio when they land on MPM card 2.

8.5.3

BRIDGE-21740

MPM MPMRx card undergoes DSP crash and reboot. 8.5.3

BRIDGE-21765

MPM MPMx media card undergoes unexpected powers off problem. 8.5.2

BRIDGE-21797

MPM When MPMx card is stuck in startup state, all calls fail until RMX reset.

8.5

BRIDGE-23161

MPM Participants cannot hear each other in a call lands on MPM card 2 fails.

8.5.3

BRDIGE-23106

Multilingual In the RealConnect conference, if the Site Name of Lync participant includes Latin ISO character, that is “é”, the character displays as “?”.

8.6.3

BRIDGE-23381

Partners - Microsoft

If a RealConnect conference including both of Skype for Business participant and RealPresence Desktop participant, RealPresence Collaboration Server participants receive frozen video.

8.6.3

BRIDGE-22907


In a DMA VMR conference, blur video displays on RealPresence Group Series that is registered to Skype for Business Front End server.

8.6

BRIDGE-23524


When the Lync 2013 client with CSS plug-in connecting to the RealPresence Collaboration Server VMR, the client cannot see the message overlay.

8.5

BRDIGE-18779


Connection cannot be established from an ISDN endpoint over a SIP gateway to a Lync client.

8.5

BRIDGE-23814


In the CAA RealConnect call, when Skype for Business client clicks mute/unmute, sometimes IVR and mute/unmute don’t function.

8.6.4

BRIDGE-19451


ContentConnect failed to resume following network failure, in a meet-now (ad-hoc) conference initiated by a Lync client, and using a Virtual Meeting Room (VMR) to connect to non-Lync clients.

8.6



Version


Polycom, Inc. 90

BRIDGE-19560


Failed to RealConnect a Polycom endpoint to a Skype for Business conference, with Encryption set to Off, in the Service provider topology, and using the organization prefix associated with the CAA of that organization, and the conference ID.

8.6

BRIDGE-22849


When using RealConnect, Trio endpoint connected to the AVMCU receives no video or low resolution video on RealPresence Collaboration Server.

8.5.4

BRIDGE-21214


RealPresence Collaboration Server cannot establish RealConnect call from HDX to Lync meeting room successfully.

8.5.2

BRIDGE-21439


Audio level transmitted to Lync 2013 AVMCU is lower than audio level transmitted to Lync participants when using RMX Virtual Edition.

8.5.3

BRIDGE-23099


RealConnect participants/CSS GW is disconnected from RealPresence Collaboration Server (MPMRx).

8.6.3HF

BRIDGE-22091


During a Polycom RealConnect conference, Lync participants cannot view non-Lync video participants.

8.5.3

BRIDGE-21299


Intermittent "Picture in Picture" effect displayed on room systems when Lync Client becomes active speaker when using RMX Virtual Edition MCU.

8.6

BRIDGE-20874


Collaboration Server RealConnect cascaded link remains muted, though Presenter of Lync conference unmuted the audience.

8.5.6

BRIDGE-21590


ContentConnect failed to resume following network failure, in a meet-now (ad-hoc) conference initiated by a Lync client, and using a Virtual Meeting Room (VMR) to connect to non-Lync clients.

8.6

BRIDGE-21439

Partners Audio level transmitted to Lync 2013 AVMCU is lower than audio level transmitted to Lync participants when using RMX Virtual Edition.

8.5.3

BRIDGE-21296

Partners Lync 2013 clients always send video at 320x176, resulting in poor quality video received by RMX using MPMx media cards.

8.5.3

BRIDGE-21817

Partners Sometimes in 1 or 2 simultaneous RealConnect calls the AVMCU displays “Connecting” status and does not transition to “Connected” when using RMX with MPM+ media cards. A core dump is generated.

8.6.2

BRIDGE-23556

Recording Start recording a RealConnect conference by the HDX remote control fails.

8.5.3

BRDIGE-22438

Recording Recording doesn’t start after clicking “Start Recording” on RMX Web UI, instead the recording starts after clicking “Stop Recording”.

8.6

BRIDGE-23554

Reservation Conflict conferences can be wrongly reserved, although the conference won’t be launched.

8.6.3



Version


Polycom, Inc. 91

BRIDGE-22802

Reservation When creating a reservation or changing other configurations of a reservation, the duration value changes itself.

8.6.3

BRIDGE-22656

Reservations Reservation conference is suspended after system reboot when using RMX.

8.5.3

BRIDGE-21355

Reservation Changing the end time of a reserved conference with RMX Manager doesn’t work on RMX(X) system.

8.5.3

BRIDGE-21470

Reservations Reservation conference is suspended after system reboot when using RMX with MPM+ media cards.

8.5.3

BRIDGE-21085

Resource Capacities

RMX 4000 reports four ports in use while it is idle. 8.5.3HF

BRIDGE-21586

Resource Capacities

When sufficient TCP video ports are available and 33 SD H.264 connections (including endpoints and recordings) are on RMX 1800, RMX 1800 cannot dial out and create an additional H.323 connection.

8.5.3

BRIDGE-22225

Resource Capacities

Audio calls transferred from a VEQ to a Mixed-Mode VMR consume video resources instead of audio resources in conference on RMX using MPMx, MPMx, MPM+ media cards.

8.5.2

BRIDGE-19480

Resource Capacity

Incorrect port usage metrics are displayed for RMX1800-0. 8.6

BRIDGE-21344

RMX Web Client/General

Layout Type drop down menu under Media Sources does not offer Personal Layout options for any Profiles other than Factory Video Profile

8.5.3HF

BRIDGE-22419

RMX Web Client

Login page is blank and administrator cannot login on RMX 1800 and RMX using MPMRx media cards.

8.6

BRIDGE-21310

RMX Manager RMX Manager on RMX using MPMx media cards, if left running, prevents workstation from coming out of sleep mode.

8.3

BRIDGE-23445

Security Vulnerabilities exist because of Root unmask value. 8.6

BRIDGE-23304

Security Soft MCU TCP port 10020 is open incorrectly. 8.6

BRIDGE-20409

Security Vulnerabilities exist in cURL and libcurl from version 7.40.0 to 7.42.1.

8.6

BRIDGE-23447

Security Vulnerabilities are in OpenSSH versions 7.0 and older. 8.6.2

BRIDGE-22004

Security Unregistered SIP participants dial into the meeting room with dial string containing the correct password, but RMX IVR displays invalid password.

8.5.3



Version


Polycom, Inc. 92

BRIDGE-22984

Security After the Secured Communication is enabled, RealPresence Collaboration Server fails to save the entered H.323 authentication user name and password. The user name and password fields are still empty after reboot.

8.6.3

BRIDGE-21420

Security TURN Server Password is displayed by RMX Manager for 8.6.1 when Web RTC is configured for Web Suite on RMX with MPMRx media cards.

8.6.1

BRIDGE-21900

Security Exchange integration configuration cannot be updated on RMX Appliance and Virtual Edition MCUs.

8.6.2

BRIDGE-21832

Security Cisco devices receive Content from RMX before they have entered the conference passcode, on RMX with MPMx media cards.

8.3

BRIDGE-22717

Security RMX appliance and virtual MCUs are no longer able to display the Address Book of the Resource Manager when connected using port 443 after upgrading Resource Manager from v8.2.1 to v8.4.1.

8.6.3

BRIDGE-5744

SIP Meeting Room status remains as 'Registered' in SIP Registration field of RMX UI after SIP Server is set to 'Off'. Meeting Room previously registered to LSC with LSC info and OCSP specified. Setup: RMX: IPv6 mode; Ultra Secure Mode; Secure Communication enabled; Certificates loaded.

8.1.4

BRIDGE-21120

SIP After SIP registration completed, due to the inappropriate timer, RealPresence Collaboration Server displays SIP registration and software asserts errors, and then followed by registration OK.

8.5.6

BRIDGE-21969

Software Version

RMX 1800 does not attempt contact the NTP server after being configured.

8.5.2

BRIDGE-21358

Software Version

Software Assert errors are displayed after upgrade to 8.5.3.66_1010.12 on RMX using MPMx media cards.

8.5.3

BRIDGE-9369

Video In a 4096 kbps conference with site names and message overlay enabled whose Video Quality is set to Motion, the next on an HDX using 4CIF resolution saw stretched text while endpoints using other resolutions received correctly proportioned text

8.1.5

BRIDGE-20209

Video Rarely, following a massive load, decoders operation might be compromised, resulting in inability of HDX AVC endpoints to view video, with only the blue background displayed, when these endpoints dial into a conference hosted by Collaboration Server, Virtual Edition.

8.6

BRIDGE-20916

Video WebRTC calls to a bridge fail with Chrome 46 (Canary), and users receive a “You have been disconnected from the meeting” message.

8.6.1

BRIDGE-21209

Video Only on RMX 1800, in a SVC conference with 100 SVC endpoints being connected, freezing video and duplicated cells are observed.

8.6.1



Version


Polycom, Inc. 93

BRIDGE-20209

Video Rarely, following a massive load, decoders operation might be compromised, resulting in inability of HDX AVC endpoints to view video, with only the blue background displayed, when these endpoints dial into a conference hosted by Collaboration Server, Virtual Edition.

8.6

BRIDGE-22529

Video Video from Lync 2010 clients freezes on RMX 1500 shortly after joining RealConnect VMR. Users have to stop and restart video.

8.5.3

BRIDGE-22755

Video After 512Kbps and Video Quality Optimized being configured, Group Series/HDX connects to Collaboration Server with 4CIF instead of 720P.

8.6.3

BRIDGE-22897

Video RMX 1800 with 1920 kbps Motion conference profile configured doesn't send video in correct frame rate, that is 60fps.

8.5.10

BRIDGE-17468

Video Delay of 2-3 seconds experienced between layout changes on RMX 1800.

8.6

BRIDGE-22755

Video After 512Kbps and Video Quality Optimized being configured, Group Series/HDX connects to Collaboration Server with 4CIF instead of 720P.

8.6.3

BRIDGE-22529

Video Video from Lync 2010 clients freezes on RMX 1500 shortly after joining Polycom RealConnect VMR. Users have to stop and restart video.

8.5.3



Version


Polycom, Inc. 94

Known Limitations

Collaboration Server 1800/2000/4000/Virtual Edition Version 8.7.1 - Known Limitations

Issue ID Category Description Found in Version

Workaround

BRIDGE24458

Audio When Music mode and stereo are enabled on Group Series, Group Series receiving stream displays incorrectly as G.719 instead of G.719 stereo while both of Group Series transmitting stream and RealPresence Collaboration Server receiving/transmitting stream displays correctly as G.719 stereo.

8.7.1

BRIDGE-24596

Audio In the RealConnect conference, no audio is in the encrypted RealPresence DMA VMR after Group Series endpoints stopping the call and rejoining the VMR. The RealPresence Collaboration Server is MPMRx system.

8.7.1

BRIDGE-23540

Audio Rarely in a WebRTC conference, Audio bleed is observed from a conference to another after long conferences, over two hours.

8.6.3 Set ENABLE_SIRENLPR to NO.

BRIDGE-23787

Cascading After the single participant leaving a meeting room, participants in another meeting room can hear music (that is the music only plays when a single participant stays in a conference) over the cascading link.

8.6.3

BRIDGE-24101

Cascading No content sharing is observed even when a cascade link is established in DMA VMR call.

8.7.1

BRIDGE-24145

Cascading In a cascade for bandwidth conference, RealPresence Series endpoints shown as "Connected with Problem" and then the call gets disconnected.

8.7.1

BRIDGE-24534

Cascading In a cascade environment with chairperson's password and participant's password enabled the Slave participants in the conference get stuck on the welcome slide and cannot see the remote participants view on entering the conference password.

8.7.1

BRIDGE-23804/

BRIDGE-23581

Content Content might be frozen or disappear if available bandwidth goes down due to packet loss.

8.7.1

BRIDGE-23193

Content After moving a Lync and CSS client from a conference with password to another conference without password, while a Group Series endpoint is sharing the content in the latter conference, the Lync and CSS client cannot receive the content until the Group Series restart the content.

8.5.4

BRIDGE-24366

Content When switching to new content in a bridged conference, previously shared content is still visible for a short period.

8.7.1


Polycom, Inc. 95

BRIDGE-24410

Content The WebRTC clients are able to snatch content where the RealPresence endpoint is set as the Content Token Owner on RMX manager.

8.7.1

BRIDGE-24543

Content CTS fails to display content when connected to a conference where content is already shared.

8.7.1

BRIDGE-24522

Content When RealPresence Debut snatches content from endpoints connected in VMR, no content found at Cisco's endpoint in the Prefer TIP conference.

8.7.1

BRIDGE-24545

Content OTX300 fails to start sharing content when connected with DMA through TIP VMR from both endpoints.

8.7.1

BRIDGE-22123

Content In a conference, H.323/SIP endpoints cannot snatch content token from ISDN endpoint currently sharing content, and vice versa.

8.6 Stop sharing content by one endpoint before trying to share content by another endpoint.

BRIDGE-8132

Content Content cannot be shared when dialing-out from a CP only conference with content set to H.263 & H.264 to Tandberg Edge95 (MXP) endpoints over H.323.

8.2

BRIDGE-22982

Content When RealPresence Desktop H.323 client joins an AVC conference, in which Cisco SX80 is sharing content to Cisco C90 and Cisco C40, the RDP can receive the content, but Cisco C90 and C40 no longer receive the content.

8.7.1 Stop and start the content on Cisco SX 80

BRIDGE-24100

Content In the RealPresence DMA VMR conference, Mac Lync client is not able to receive the content from Polycom endpoints. Content shared from MAC client is successfully received on Polycom endpoints.

8.7.1

BRIDGE-24661

Content In the RealConnect and WebRTC conference, MAC Lync client is not able to send content after it had received content from others before.

8.7.1

BRIDGE-18609

Diagnostics At times Web access to MCU is blocked due to anti-virus policy.

8.5.2 Log in though RMX Manager (though prevents Diagnostic mode).

BRIDGE-24228

FECC Avaya XT700 FECC does not functioning properly in a multipoint call on RMX1800.

8.7.1



Workaround


Polycom, Inc. 96

BRIDGE-23432

FECC LifeSize Icon endpoint FECC does not functioning properly in a multipoint call.

8.6.4, 8.7.1

BRIDGE-24178

FECC Cisco MX300 FECC does not functioning properly in a multipoint call.

8.7.1

BRIDGE-24239

FECC The FECC fails with the Huawei TE30 in H323 call connected to RMX.

8.7.1

BRIDGE-23280

Encryption Moving participants between encrypted conferences fails on Virtual MCU.

8.7.1

BRIDGE-24725

General Following MIB OIDs are not responded with correct values or the OIDs are invalid on RealPresence Collaboration Server, Virtual Edition:

serviceConferenceServerTotalVoicePorts, serviceConferenceServerTotalVoicePortsUsed. serviceConferenceServerTotalPortsUsed, hardwareOverallStatus.

8.7.1

BRIDGE-24461

General Soft blades get stuck in “Software blade Pending Authentication State” when the soft blades are attached to RMX 1800.

8.7.1 Reboot RMX 1800.

BRIDGE-23520

General RealPresence Mobile fails to stay in the conference more than 15 seconds and doesn't see participants' video.

8.7.1

BRIDGE-23295

General SIP and H.323 endpoints connecting to RMX 1800 through a VMR were able to see the join screen and hear the welcome prompt but then they get disconnected from the call.

8.7.1

BRIDGE-23390

General In a mixed CP and SVC conference, the SVC endpoints use a higher rate than the rate is negotiated.

8.7.1

BRIDGE-23824

General After MCU failover, a participant is lost from the Lync VMR with RDP content enabled and the sharing content doesn't work.

8.7.1

BRIDGE-23962

General New core file was detected as httpd received an abort signal and crashed the system.

8.6.3

BRIDGE-24484

General When participant joins or leaves the conference, displaying participant site name with Red background is alarming.

8.7.1

BRIDGE-24150

General Several RealPresence Group Series endpoints connecting to RMX 1800 are in “Connected with Problem” state and IP Network Services are not accessible.

8.7.1



Workaround


Polycom, Inc. 97

BRIDGE-24580

General After connecting 200 audio calls to VMR with 1920 Kbps and CP and SVC mixed settings, then disconnecting the calls, core dump files are created on RealPresence Collaboration Server (MPMRx).

8.7.1

BRIDGE-24582

General When multiple RealPresence Desktop endpoints dial into VMR with 1024 Kbps line rate, CP and SVC mixed conference mode and Encryption when possible settings, packet losses, video freeze and green patches as the content are observed on RealPresence Collaboration Server (MPMRx).

8.7.1

BRIDGE-24632

General RealPresence Collaboration Server (MPMRx) crashes in the secure when available VEQ.

8.7.1

BRIDGE-24615

General Call drops on RealPresence Collaboration Server (MPMRx) prior to high CPU and memory usage showing in the Faults list.

8.7.1

BRIDGE-24604

General Core dump occurs when RMX 1800 with three DSP cards system is under a moderate load for several hours.

8.7.1

BRIDGE-13704

General Video freezes and audio fails when concurrently uploading a large file (more than 100MB).

8.2

BRIDGE-18142

General When an RMX 2000 is configured for “Separate Management Network” and is also configured to use 802.1X authentication on its IP Network Service interface, the status reported in the LAN List in the Hardware Monitoring pane may be inaccurate, showing the 802.1X Status as “Not Configured” and the 802.1X Method as “Off” even though 802.1X is configured.

8.6 802.1X status can be determined by examining the status of the port at the 802.1X server.

BRIDGE-12768

General In an SVC Mode conference, Group Series and RealPresence Desktop endpoints, dialing directly to an “Encrypt when Possible” VMR, are connected as Non-encrypted. When dialing via a Virtual Entry Queue they are erroneously connected as Encrypted. Occurs when SIP Transport type is TCP.

8.4

BRIDGE-23007

General During a CP conference running at a line rate of 4MB, Tandberg 1700 (MXP) endpoints registered to a DMA fail to receive content from a Tandberg Edge95 (MXP) endpoint.

8.2

BRIDGE-23286

General During conference on RMX (MPMRx) all participants disconnected followed by a card crash. A MCU Internal Problem event is then reported.

8.7.1



Workaround


Polycom, Inc. 98

BRIDGE-22216

General During a CP conference, Radvision Scopia XT1000 & XT5000 endpoints registered to the DMA and connected via SIP share content via the video channel and not the content channel.

8.5

BRIDGE-24504

H.323 RealPresence Debut falls back to audio when content sharing is stopped in the H.323 call connected to RMX.

8.7.1

BRIDGE-24230

Interoperability

Content sharing from Cisco MX300 doesn’t work when conference template is set to use H.264 High Profile content

8.7.1 Do not check High Profile content in the conference template.

BRIDGE-24217

Interoperability

Cisco MX300 endpoint is unable to join in H.323 encrypted AVC VMR - This happens if the encryption key selected is 2048

8.7.1 Set MX300 Encryption KeySize to Max1024bit in the endpoint's System Configuration page.

BRIDGE-24570

Interoperability

When dialing from Secure VMR through Secure VEQ, Cisco CTS and TX endpoints get disconnected.

8.7.1

BRIDGE-24760

Interoperability

Call drops during a cascade conference due to RealPresence Collaboration Server, Virtual Edition sending 500 internal errors to DMA.

8.7.1

BRIDGE-24906

Interoperability

Cisco TIP-enabled endpoints can’t hear IVR messages for 10-15 seconds after dialing to VEQ or VMRs.

8.7.1

BRIDGE-24570

Interoperability

Cisco CTS and TX endpoints are unable to join conferences through secure or secure when possible VEQ.

8.7.1

BRIDGE-24691

Interoperability

Only in the Speaker Priority RMX conference, Cisco three-screen Telepresence systems display far site endpoint video on the left screen instead of center screen.

8.7.1

BRIDGE-24692

Interoperability

After Cisco Telepresence System 1300 performs hold and resume in the Encryption when possible VMR call, flicking noise and frozen/bad video is on Cisco Telepresence System 3010, Cisco Telepresence System 1300 and Cisco Telepresence TX9000 Series.

8.7.1

BRIDGE-24243

Interoperability

In Soft MCU, when connected to multiple conference through WebRTC client using Chrome on Mac, the user receives a frozen video of other participants in the conference.

8.7.1



Workaround


Polycom, Inc. 99

BRIDGE-24283

Interoperability

In an AVC conference, when RMX dials out to HDX and Avaya 10XX, the Avaya 10XX endpoint receives poor quality video.

8.7.1

BRIDGE-24409

Interoperability

The RealPresence Web Suite endpoints cannot connect through iPAD/ Android tablets in a mixed conference.

8.7.1

BRIDGE-23268

Interoperability

Cisco Telepresence IX5000 left and right screens are not shown in the Prefer TIP conference.

8.7.1

BRIDGE-23253

Interoperability

In the WebRTC conference, Chrome participant observes other participants' video lagging 3 seconds to audio and other participants observes Chrome participant with frozen and broken up video. If WebRTC client uses Firefox, there is no such problem.

8.7.1

BRIDGE-23577

Interoperability

In the SVC conference, RealPresence Group Series cannot receive content from other endpoint.

8.7.1

BRIDGE-23463

Interoperability

In the SVC conference which consists of RealPresence Mobile endpoints, RealPressence Desktop endpoints and RealPresence Group Series endpoints, the RealPresence Group Series displays as black cell on other endpoints.

8.6.4,

8.7.1

BRIDGE-23795

Interoperability

Failed to add RealPresence Collaboration Server instance to RealPresence Resource Manager when certificate validation is enabled.

8.6

BRIDGE-24046

Interoperability

After holding and resuming the 384/512/768 Kbps call on RMX 1800, RealPresence Group Series 310 is connected in 64 Kbps resulting in layout doesn’t show in video on near and far ends.

8.6.3

BRIDGE-24093

Interoperability

When RealPresence Group Series 700 and RealPresence Debut endpoints share content using RealPresence Desktop paired device, the content sharing doesn't work properly and RealPresence Debut content is not displayed to some endpoints in the conference call.

8.7.1

BRIDGE-24204

Interoperability

When sharing content from RealPresence Desktop to Cisco Telepresence SX10 in the VMR call, the content is transmitted in people channel for Cisco Telepresence SX 10.

8.7.1

BRIDGE-24179

Interoperability

When RPCS conference call is place on Hold and then resumed it results in the content stream to freeze on the last frame sent even if the content sharing is stopped.

8.7.1



Workaround


Polycom, Inc. 100

BRIDGE-24181

Interoperability

When Content Sharing is initiated from any endpoint in the VMR; the overall video stability of the call is affected and the transmitting video is lost from the system that initiates content. Endpoints also sometimes experienced permanent video freezing and loss of system functionality.

8.7.1

BRIDGE-24199

Interoperability

Connecting to Prefer TIP Speaker Priority Conferences the Polycom room systems are connected to only one video stream instead of all three.

8.7.1

BRIDGE-24547

Interoperability

In the Telepresence conference, OTX 300 sees CTS 500 video and rest of its two screens are black, but CTS 500 only sees the main camera video from OTX 300.

8.7.1

BRIDGE-24569

Interoperability

Cisco CTS and TX endpoints are unable to connect to Secure when possible VEQ.

8.7.1

BRIDGE-24584

Interoperability

After multiple times content sharing and snatching among Lync, RealPresence Group Series, RealPresence Desktop and RealPresence HDX clients, the H.323 registered RealPresence HDX is unable to receive content but it is still able to share content.

8.7.1

BRIDGE-24588

Interoperability

After RMX 1800 dialing out an H.323 call and HDX connecting to RMX 1800 with H.263, then RealPresence Group Series snatching the content from RealPresence HDX, content freezes on the RealPresence HDX.

8.7.1 Reboot RealPresence HDX.

BRIDGE-24590

Interoperability

RealPresence Debut receives black video from RealPresence Group Series in the SVC conference on the RealPresence Collaboration Server (MPMRx) system.

8.7.1

BRIDGE-24591

Interoperability

When sharing content from TX9000 in the Prefer TIP CP conference on the RealPresence Collaboration Server (MPMRx) system, video layout is disrupted.

8.7.1

BRIDGE-24667

Interoperability

All RealPresence Group Series register to RealPresence DMA via TLS SIP and dial into an Encryption possible VMR from VEQ.

When one RealPresence Group Series performs Hold and Resume, the RealPresence Group Series sees the black video and all others receive frozen video and no audio from the RealPresence Group Series.

8.7.1

BRIDGE-24634

Interoperability

After RMX 1800 without DSP card dialing out to RealPresence Group Series and Tandberg MXP via H.323, bad video displays on Tandberg MXP.

8.7.1

BRIDGE-24295

Interoperability

The Cisco C series and SX series receives poor audio quality with no video when connected to RMX conference through the Cisco 3241 gateway with RMX 1800.

8.7.1



Workaround


Polycom, Inc. 101

BRIDGE-24293

Interoperability

Poor audio quality with no video is received when connected to RMX conference through the Radvison Scopia P10 gateway with RMX 1800.

8.7.1

BRIDGE-1408

Interoperability

When dialing into a VMR from VVX only with voice, and the call is transferred to HDX, then HDX joins the VMR at 64Kbs rate, sometimes HDX can hear conference but other participants cannot hear voice from HDX.

7.8.0

BRIDGE-24099

Interoperability

Sometimes, no video is received by the RealPresence Debut if it dials into a Prefer TIP VMR after the Cisco DX80.

8.7.1

BRIDGE-23287

Interoperability

During 6Mbps AVC conference, when RMX (MPMRx) dials out to HUAWEI TE40 SIP Videoconferencing endpoint, endpoint connects and remains in IVR Welcome screen but disconnects from conference after I minute. Problem does not occur when endpoint dials in to RMX or if conference line rate is reduced to 4Mbps.

8.7.1

BRIDGE-19523

Interoperability

In a combined Collaboration Server 4000 and CUCM (Cisco MCU) conference, CTS and TX TelePresence endpoints move from a Virtual Entry Queue (VEQ) to a Virtual Meeting Room (VMR), both on the DMA, fails - TX was disconnected, and CTS video froze.

8.6

BRIDGE-21760

Interoperability

Repeated connection/disconnection (more than 10) of 5-10 ITP endpoints to a 4Mbps ITP conference on RealPresence Collaboration Server 2000, results in conference end, and MPMRx media card reboot.

8.5.3 HF

BRIDGE-15976

ISDN Collaboration Server using MPMx cards cannot dial out to an H.261 ISDN endpoint at bit rate exceeding 320Kbps.

8.7.1

BRIDGE-24702

ISDN ISDN card loses connection with RMX 1800, and ISDN calls can be processed.

8.7.1

BRIDGE-23725

IP Calls might not connect in a TCP-only federated environment when a Lync-registered RealPresence Group system is in one domain and a VMR is in a different domain.

7.6.1

BRIDGE-24711

IVR Sometimes, DTMF doesn’t work after participant entering password to join a conference.

8.7.1

BRIDGE-24253

IVR While moving from a Virtual Entry Queue (VEQ) to a Virtual Meeting Room (VMR), the endpoint receives an invalid conference ID IVR message after dialing the correct conference ID.

8.7.1



Workaround


Polycom, Inc. 102

BRIDGE-24546

IVR A welcome message or enter conference password IVR is not played when CTS500 dials in to a TIP VMR.

8.7.1

BRIDGE-22068

IVR Connecting a conference on RealPresence Collaboration Server 1800 from RealPresence Desktop via VMRs numbered 72xxx results on IVR message played twice.

8.6.1

BRIDGE-24919


After joining a RealConnect conference, Group Series can hear white noise in the RealPresence DMA VMR.

8.7.1

BRIDGE-23913


Skype for Business "Audience mute" feature does not work properly when using service provider's topology (CAA).

8.6.4

BRIDGE-24648


When the RealPresence Collaboration Server MPMRx system is in the RealConnect environment, video freezes on the Skype for Business client in the RealPresence DMA VMR.

8.7.1

BRIDGE-24352


Skype for Business client undergoes crash after receiving content from another Skype for Business client and clicking Actual Size.

8.7.1

BRIDGE-24213


In a Skype for Business conference, when the RealPresence Trio endpoint registered to DMA performs the Hold and Resume call operation, the content shared by the Skpye for Business client in the conference is lost at Trio's end.

8.7.1

BRIDGE-24635


In a RealConnect call, the Skype for Business and Polycom GroupSeries endpoints can hear the hold music from another Lync registered RealPresence Trio after the RealPresence Trio putting its call on hold.

8.7.1

BRIDGE-24163


Panoramic Layout is not working in CAA RealConnect call.

8.7.1

BRIDGE-24346


When the STUN/Edge server is behind a firewall, in a RealConnect conference, on-line AVMCU cascading link gets disconnected from RealPresence Collaboration Server (MPMRx) after sometime. This is an intermittent issue.

8.7.1 Add static route for TURN/Edge Server in Media card using RMX Manager.

BRIDGE-24679


RealPresence Group Series receives green content when Skype for Business client shares the content in the DMA VMR and RealConnect call.

8.7.1

BRIDGE-24463


Video doesn’t display when Skype for Business Android client escalate the VMR call from Audio to Video.

8.7.1



Workaround


Polycom, Inc. 103

BRIDGE-24611


Skype for Business 2016 client’s video freezes on the RealPresence Group Series in an on-line AVMCU call.

8.7.1

BRIDGE-24666


RealPresence Collaboration Server crashes when it is cascaded to an AVMCU with MultiView disabled.

8.7.1

BRIDGE-24621


After Skype for Business client inviting RealPresence Group Series endpoints into the CAA RealConnect conference then muting the AVMCU cascading link, Skype for Business client still can hear RealPresence Group Series once it becomes active speaker. On-Premise RealConnect conference doesn’t have such issue.

8.7.1

BRIDGE-22070


RealPresence Collaboration Server sends an update to Lync Server every 10 minutes and the update fails.

8.6

BRIDGE-24360


After a Lync client minimizing the shared content of a program in VMR, all participants observe green screen instead of a prompt indicating nothing to see at the moment.

8.7.1

BRIDGE-24440

Resource Capacity

Port usage percentage cannot exceeds 94% due to random disconnection.

8.7.1

BRIDGE-24158

Resource Capacity

Calls on RMX 2000 get disconnected if the port usage is more than 80% and are not able to connect further.

8.7.1

BRIDGE-16746

Resource Capacity

A single media card supports up to 300 SVC participants in a way of supporting 60 conferences and each conference supporting up to 5 participants. In this case, the maximum conference rate is 1.5MB.

8.5

BRIDGE-24448

Recording When RealPresence Desktop dials in to VMR with H.323, the H.323 recording link connected to RMX shows blank video for live streaming/downloaded recording.

8.7.1

BRIDGE-24851

Recording The New Recording Link button gets disabled when another link is clicked from the recording link list of the selected MCU.

8.7.1 Close RMX Manager and reopen it.

BRIDGE-22998

Recording When one H.323 recording link has connected to an RMX conference, another H.323 recording link still can be created and connected to the same conference.

8.6.3

BRIDGE-24455

Security When dialing into a VMR, frozen video of participants connected to another meeting is seen in the call.

8.7.1

BRIDGE-20202

Security When launching a conference from a GS endpoint registered as AS-SIP, on a Collaboration Server 1800 using IPv4 address mode, the endpoint IP address cannot be viewed via Participant Properties > Channel Status - Advanced tab

8.6



Workaround


Polycom, Inc. 104

BRIDGE-22072

Security Reboot required following new CRL installation on Collaboration Server 2000, for new CRL to take effect.

8.6 Reboot RMX periodically to ensure that the latest CRLs take effect.

BRIDGE-22113

Security At times, when either modifying DNS address from IPv4 to IPv6, or modifying shelf management IPv6 address, Collaboration Servers with MPMRx media card failed to restart either completely or in a timely manner.

8.6

BRIDGE-8004

SIP SIP endpoints may intermittently disconnect after a conference has run for more than 30 minutes.

8.2

BRIDGE-670

Software version

Manual connection can take up to 30 seconds to begin in 2048kbps conference, with manual dial out to over 80 participants.

7.8.0

BRIDGE-23466

Video When an SVC endpoint gets connected to RealPresence Desktop conference or RealPresence Mobile conference, the video quality of the call is distorted.

8.7.1

BRIDGE-23346

Video Sharing content from RealPresence Desktop results in frozen people video thumbnails

8.7.1

BRIDGE-10140

Video VSX receives no video in SIP call registered to DMA. 8.3

DOC-1402

Document Defect

Lack of information on CPU, RAM and Hard Disk requirements for deploying RealPresence Collaboration Server, Virtual Edition on new supported platform, Dual E5-2690v3 @ 2.6GHz 48 Cores, 42 HD ports.

8.7.1

DOC-1306

Document Defect

Deploying OVA with one NIC (Default) into RealPresence Collaboration Server, Virtual Edition instance works. The minimum deployment settings of NIC 2 X 1 needs be verified.

8.7.1



Workaround

RMX Web Client Installation - Troubleshooting Instructions

Polycom, Inc. 105


If a Browser Environment Error occurs, close all the Internet Explorer sessions and reconnect to the MCU.

If the problem persists, you can run the Automatic Troubleshooting Utility or perform the Troubleshooting Procedures manually.

The Manual Troubleshooting Procedures include several procedures that can be performed in order to solve the connection error. At the end of each procedure, check if you can connect to the MCU and if the problem persists, perform the next procedure.

The following troubleshooting procedures can be performed manually:

● Procedure 1: Ending all Internet Explorer Sessions

Note: GUI Usage in Maximum Security Environments

Use of the RMX Web Client is not recommended in Maximum Security Environments.Management using the RMX Manager is the recommended method.

NOTE: Certificates in Secured Mode

In Secured Mode (https://), the DNS name specified in the Collaboration Server’s Certificate must correspond with that of the DNS Server used by the Client that is connecting to the RMX


Polycom, Inc. 106

● Procedure 2: Deleting the Temporary Internet Files, Collaboration Server Cookie and Collaboration Server Object

● Procedure 3: Managing Add-ons Collisions

● Procedure 4: Add the Collaboration Server to the Internet Explorer Trusted Sites List

● Procedure 5: Browser Hosting Controls (Optional)

Procedure 1: Ending all Internet Explorer Sessions

In some cases, although all the Internet Explorer sessions were closed, the system did not end one or several IE processes. These processes must be ended manually.

To end all Internet Explorer sessions:

1 Start the Task Manager, and select the Processes tab.

2 Select an iexplore process, and click End Process.

3 Repeat this process for all iexplore processes currently active.

4 Close the Windows Task Manager dialog.

5 Open the Internet Explorer, and connect to the MCU.

6 If the problem persists, continue with Procedure 2.


Polycom, Inc. 107

Procedure 2: Deleting the Temporary Internet Files, Collaboration Server Cookie and Collaboration Server Object

If at the end of Procedure 1 the error message is still displayed, and you cannot connect to the MCU, perform the following operations:

● Delete the Temporary Internet files

● Delete the RMX/Collaboration Server Cookie

● Delete the RMX/Collaboration Server ActiveX Object

Deleting the Temporary Internet Files

To delete the Temporary files:

1 In the Internet Explorer, select Tools > Internet Options.

2 In the Browsing history pane, click Delete.

The Delete Browsing History dialog opens.

3 It is recommended to delete only the Temporary Internet files.

By default, the Cookies option is also selected. Clear it if you do not want to clear the cookies from your computer.

4 Click Delete.

When the process is complete, the system return to the Internet Options dialog.


Polycom, Inc. 108

Deleting the Collaboration Server Cookie

To delete the Collaboration Server Cookie:

1 In the Internet Options - Browsing History pane, click Settings.

The Temporary Internet Files and History Settings dialog is displayed.


Polycom, Inc. 109

2 Click View files.

The Windows Explorer screen opens, listing Windows Temporary Internet Files.

3 Browse to the Collaboration Server cookie.

The cookie is listed in the format: cookie:user name@Collaboration Server/RMX IP address. For example: cookie:[email protected].

4 Right-click the Collaboration Server cookie and select Delete.

The system prompts for confirmation.

5 Click Yes.

The cookie is deleted.

6 Close the Windows Explorer screen.


Polycom, Inc. 110

Deleting the RMX/Collaboration Server ActiveX Object

To delete the RMX/Collaboration Server ActiveX Object:

1 In the Temporary Internet Files and History Settings dialog, click View objects.

The Windows Explorer screen opens, listing the Windows Downloaded Program Files.

2 Right-click the EMA.ClassLoader.dll, and select Delete.

3 Upon system prompts for confirmation, click Yes.

The Collaboration Server object is deleted.


Polycom, Inc. 111

4 Close the Windows Explorer screen.

5 In the Temporary Internet Files and History Settings dialog, click OK.

6 In the Internet Options dialog, click OK to close it.

7 Close the Internet Explorer session and reopen it.

8 Connect to the Collaboration Server.

If the problem persists, continue with Procedure 3.

Procedure 3: Managing Add-ons Collisions

In some cases, previously installed add-ons, such as anti virus programs can create collisions between applications and prevent the installation of a new add on. Disabling these add-ons may be required in order to install the RMX Web Client.

To disable an add-on:

1 In the Internet Explorer, select Tools > Manage Add-ons.

The Manage Add-ons - Toolbars and Extensions dialog opens.

2 Scroll to the add-on to disable (for example, the anti virus add-on), right-click it and select Disable.

Alternatively, select the add-on and click Disable.

3 Click Close to close this dialog.

4 Connect to the Collaboration Server.

If the problem persists, continue with the Procedure 4.

Procedure 4: Add the Collaboration Server to the Internet Explorer Trusted Sites List

In some cases, local security settings may prevent Internet Explorer from accessing the Collaboration Server.


Polycom, Inc. 112

To add the Collaboration Server to the Internet Explorer Trusted Sites list:

1 In the Internet Options dialog, select the Security tab.

2 Select the Trusted Sites tab.

3 Click Sites.

The Trusted sites dialog is displayed.

4 If the Collaboration Server is using Secure Mode:

a In the Add this website to the zone: field, enter, “https://” followed by the IP address or the DNS name of the Collaboration Server.

b Click Add, and Close

5 If the Collaboration Server is using Standard Security Mode:

a In the Add this website to the zone: field, enter, “https://” followed by the IP address or the DNS name of the Collaboration Server.

b Click Add.


Polycom, Inc. 113

c Clear the Require server verification (https:) for all sites in this zone check-box.

d Click Close.

Procedure 5: Browser Hosting Controls (Optional)

If the RMX Web Client does not load and run after Procedures 1-4 have been performed, the reason may be that .NET Framework 4 or higher is running on the workstation with Managed Browser Hosting Controls disabled.

Managed Browser Hosting Controls is an Internet Explorer operating mode required by the RMX Web Client. By default, .NET Framework 4 and higher are not enabled to support Managed Browser Hosting Controls.

Perform Procedure 5 to:

● Determine whether .NET Framework 4 or higher is running on the workstation.

● Determine whether a 32-bit or 64-bit version of Windows is running on the workstation.

● Enable Managed Browser Hosting Controls if .NET Framework 4 or higher is running on the workstation.

To enable Managed Browser Hosting Controls:

1 Determine whether .NET Framework 4 or higher is running on the workstation.

a On the Windows Desktop, click Start.

b In the Start Menu, click Control Panel.

c In the Control Panel, click Programs and Features.

d Inspect the Programs and Features list for the version of Microsoft .NET Framework Client Profile that is installed.

2 Determine whether a 32-bit or 64-bit version of Windows is running on the workstation:

a On the Windows Desktop, click Start.

b In the Start Menu, click Computer.

c In the Computer Menu, System properties inspect the value of the System type field.

3 Enable Managed Browser Hosting Controls if .NET Framework 4 or higher is running on the workstation.

a Open the Registry.

b Navigate to the Subkey:

32-bit System: HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\.NETFramework

64-bit System: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework

c Add the Dword Value: EnableIEHosting

d Set value of EnableIEHosting to 1.

e Close the Registry.

f Close and re-open Internet Explorer.


Polycom, Inc. 114

NOTE: Internet Explorer 9 with Windows 7

If Browser Error problems persist after performing the above procedures it, is recommended to:

1 Clear the Internet Explorer cache.

2 Add the MCU URL or IP address to the Trusted Sites of Internet Explorer.

3 Reset Internet Explorer’s security level to medium and keep default settings.

Polycom, Inc. 115

Addenda to Release Notes - Polycom Lab Features

Addendum to Release Notes Polycom Lab Feature - Discussion Mode LayoutPolycom Lab features are new technology innovations that may not have undergone all levels of formal testing. We encourage you to try them out, but because they are not fully tested or supported, please don't deploy them in production environments.

Polycom Lab features are experimental and may or may not become official features in a future release.

This brief specification documents the following Polycom Lab Feature.

To find out more about this Polycom Lab feature or provide feedback on this feature, contact Polycom Support.

Description of FeatureThe term Discussion Mode refers to the Collaboration Server ability to identify conferencing scenarios, in which either one or two participants are the main/only speaker(s). In such cases, provided this feature is activated, AVC endpoints in CP Only or mixed CP and SVC conferences, view the conference in either a 1+7 or a 2+8 layout (depending on the number of main speakers), with the main speakers video displayed in the main cell(s), as shown in the table below.

Feature Name: Discussion Mode Layout

Release Feature is Being Tested In: Polycom® RealPresence® Collaboration Server, V8.7.1

Level of Testing Performed To Date: None

Feature Unit Tested

Feature Unit and Product Regression Tested

Full Feature Unit, Product Regression, and Solution Tested

Layouts Used in Discussion Mode

Number of Active Speakers Layout Name Layout

1 1+7

2 2+8


Polycom, Inc. 116

Discussion Mode is triggered once the number of participants reaches a minimum, and one of the participants becomes the active speaker by speaking over a time interval (see System Flags below).

Layout Usage Criteria

● A 1+7 layout is used for single speaker scenarios.

● While a 1+7 layout is used, should another participant become an active speaker, the 1+7 layout is replaced by a 2+8 layout.

● While a 2+8 layout is used, once another participant becomes the active speaker, its video, if exists (i.e. not an audio participant and video is not muted), replaces that of the active speaker preceding the last speaker. If no video is sent for the speaker, both the layout and speakers remain as is.

● While a 2+8 layout is used, and only one participant remains the active speaker, the 2+8 layout is replaced by a 1+7 layout, with the two least active participants moved out of the layout.

● The active speakers do not view their own video, but that of the last active speaker(s).

● At all times, the most recent active speaker is displayed in the top-left cell. The smaller cells are populated bottom up, right to left.

● More than 10 participants do not result in using layouts with larger number of cells.

System Flags

Guidelines to Related Issues

● Recording link layout is not altered, as well as the layout sent to the recording link. The recording link layout displays as many participants as possible, with the recording link cell the first to be discarded.

● Discussion Mode is inactive when in Legacy content mode (i.e. content sent via people video layout).

● In cascading conferences, depending on the value of the system flag FORCE_1X1_LAYOUT_ON_CASCADED_LINK_CONNECTION:

When value is YES - Only the active speaker is sent over the cascading link, where that link is one of the participants in the Discussion Mode layout.

System Flags for Discussion Mode Activation

Flag Name Flag Description

DISCUSSION_DISPLAYED_PARTICIPNATS_TO_START

The minimal visual participants required to trigger Discussion Mode.

Visual participants are video participants with an active video, or one of the two static video participants included in the conference layout.

This system flag required a manual addition to be modified, and immediately affects new conferences (i.e. not reset required).

Default value: 8

Note: A value of 7 results in activating Discussion Mode with 7 participants, with the speaker cell included.

DISCUSSION_MODE_ACTIVE_SPEAKER_FOCUS_INTERVAL

The time interval, in seconds, after which a participant becomes an active speaker, thus the minimum duration for its display in the main cell(s).

This system flag required a manual addition to be modified, and immediately affects new conferences (i.e. not reset required).

Default value: 20 (seconds)

Minimal value: 10 (seconds)


Polycom, Inc. 117

When value is NO - The Discussion Mode layout is sent over the cascading link, and is displayed in the cascading link participant cell.

Interaction with Other Features

● Participants may be assigned a Personal Layout.

● A participant may set its own layout via Click & View.

● Participants layout may be modified via PCM.

● Discussion Mode is applicable in Same Layout scenarios.

● Discussion Mode is inactive in Presentation Mode, Lecturer Mode, and Telepresence Mode.

● When Exclude Static Room from Layout is on:

Static rooms video is the last to be displayed in Discussion Mode layout cells, unless it belongs to either the current or last active speaker.

The DISCUSSION_DISPLAYED_PARTICIPNATS_TO_START system flag counting may take up to two static rooms into account.

To Enable and Disable this Polycom Lab Feature

To enable/disable Discussion Mode:

1 Right-click on a CP Only or Mixed CP and AVC conferencing profile, and select Profile Properties.

or

Right-click on a CP Only or Mixed CP and AVC conference, and select Conference Properties.

2 Select the Video Settings tab.


Polycom, Inc. 118

3 Verify the Auto Layout check-box is selected.

4 Select/De-select the Discussion Mode check-box.

5 Click OK to save settings.

Pre-requisites● This feature is applicable only to AVC endpoints, and to CP Only and Mixed CP and SVC

conferences.

● Conference profile must be set to using Auto Layout (Conference Properties > Video Settings tab).

● All user interface pertaining to this feature appear only if in the dialog below:

Polycom Lab features are enabled in general.

The feature check-box is selected.


Polycom, Inc. 119

ProceduresNone.

Addendum to Release Notes Polycom Lab Feature - Exclude Inactive-Video Participants from LayoutPolycom Lab features are new technology innovations that may not have undergone all levels of formal testing. We encourage you to try them out, but because they are not fully tested or supported, please don't deploy them in production environments.



Feature Name: Exclude Inactive-Video Participants from Layout



Feature Unit Tested



Polycom Labs - general check-box

Feature check-box


Polycom, Inc. 120


Description of FeatureIn many conferences some cells displaying static video can be observed. This may occur either due to the endpoint camera not focusing on people, or when video is disabled.

To enhance user experience, provided this feature is activated, the Collaboration Server preserves mainly significant video in the conference layout, by excluding inactive-video rooms from the conference layout, in both AVC and SVC endpoints.

Presence of static video participants currently connected to the conference, is indicated by the icon.

The table below lists the guideline for static video rooms’ exclusion from the conference layout.

Interactions with Other Features

● Video participants count is unaffected by the exclusion of inactive-video participants from the conference layout. Therefore, so long as there are less than a hundred video participants, their presence is exposed by the count.

● Static video Telepresence rooms are not removed from the conference layout, provided the Telepresence Layout Mode is defined as Speaker Priority.

● Recording link layout is not affected by this feature, however static video rooms have the lowest priority in the recording link layout population.

● This feature is fully compatible with the Discussion Mode Layout feature (see separate addendum).

● This feature is fully compatible with panoramic view:

If panoramic view is comprised of a multitude of endpoints - The same as with Auto Layout.

If panoramic view is comprised of a Telepresence room - The entire room is displayed, regardless of any static video components in the Telepresence room.

Guidelines for Removing Static Room Video from Conference Layout per Endpoint Type

AVC Endpoints SVC Endpoints

Auto Layout is defined by the number of active video participants + maximum of 2 static video participants.

The layout used by the endpoint is determined by the endpoint.

Free cells are populated by static video participants. This feature is active for SVC endpoints in mixed conferences:

• In soft MCU - At beginning of conference

• In HW MCU - Once the first AVC endpoint connects.

Once an endpoint is detected as a static video endpoint, it is removed from the layout upon the next layout change, either participant join/leave, or change in active speaker.

The same applies to static video room becoming active video room.

SVC endpoints request numerous video streams, which populate the layout cells according to the MCU internal considerations, where static video rooms are prioritized lower than active video rooms, unless they represent the current or last active speakers.

So long as the static video room is either the active or last speaker, it remains in the conference layout.


Polycom, Inc. 121

● A participant forced in the layout is always displayed, even if its video is inactive.


To enable/disable excluding inactive-video participants from layout:


or

Right-click on a CP Only or Mixed CP and AVC conference, and select Conference Properties.

2 Select the Video Settings tab.

3 Verify the Auto Layout check-box is selected.

4 Select/De-select the Exclude static-video rooms from layout check-box.



Polycom, Inc. 122

Pre-requisites● This feature is applicable only to CP Only and Mixed CP and SVC conferences.

● Conference profile must be set to using Auto Layout (Conference Properties > Video Settings tab).




ProceduresNone.

Addendum to Release Notes Polycom Lab Feature - Using Video Clips for IVR ServicesPolycom Lab features are new technology innovations that may not have undergone all levels of formal testing. We encourage you to try them out, but because they are not fully tested or supported, please don't deploy them in production environments.




Feature check-box


Polycom, Inc. 123


Description of FeatureWhen connecting a conference running on Polycom RealPresence Collaboration Server via an Entry Queue, a still slide is used, which up until version 8.7.1 could be replaced by a different still slide.

From version 8.7.1, provided Polycom Lab features are enabled, and the motion slides feature is activated, Polycom allows:

● Using a motion slide (video clip) instead of a still slide.

● Replacing the default motion slide Polycom supplies (within both installation and upgrade packages), which is named General_Polycom_Slide_Motion, with a different video slide.

● Receiving motion slides from the DMA for external IVRs.

Video Slides Guidelines

● The motion slide is played for following media types: H.263, H.264, RTV and TIP, and it is not supported for H.264 High Profile.

● Since TIP endpoints are sometimes prone to encountering problems with customizing IVR slides, it is possible to block video slides for TIP endpoints via the ENABLE_MOTION_SLIDE_TO_TIP_EPS system flag (see below), in which case these endpoints cannot view video clips.

● Video clips size is limited to 5M to prevent memory overflow. Thus, up to 10 motion slides per a local IVR may be loaded by the Administrator user.

● Bit rates are preset as described in the table below.

Feature Name: Using Video Clips for IVR Services



Feature Unit Tested



Note: Audio Prompt for Video Slide

The audio prompt to the video slide is taken from the IVR associated with it.

Bit Rate values per Resolution

Resolution Frame Rate Preset Bit Rate (Kbps)

CIF 30 384

SD 30 768


Polycom, Inc. 124

● Users should attempt slide customization for inactive time intervals (i.e. with no active or scheduled conferences) due to the heaviness of the process of the clip customization to MCU video format.

● Video clips for customization are characterized by:

Format - avi, mp4, mov, mpeg only

Resolution - 1080p30 only

Duration - 10 seconds. Up to 30 seconds are accepted, though it is truncated to 10 seconds.

Due to clips cyclic playing, it is recommended to harmonize the clip end and beginning.

Effects - Avoid light effects to prevent imperfect translation to MCU video format.

System Flags

To Enable and Disable this Polycom Lab FeatureSee the last prerequisite below.

Prerequisites● This feature requires CIF as a minimum resolution supported by the endpoint.

● The media type supported by the endpoint may be H.263, H.264 (Base Profile only), RTV, and TIP. H.261 and H.264 High Profile endpoints are not supported.




HD720 30 1024

HD1080 30 2048

System Flags for Motion Slide blocking for TIP Endpoints

Flag Name Flag Description

ENABLE_MOTION_SLIDE_TO_TIP_EPS

Enables displaying motion slides to TIP endpoints.

This system flag required a manual addition to be modified, and if modified, value takes effect immediately (i.e. not requires reset) for new conferences.

Range: YES (default), NO

Note: Set this flag to NO if you experience difficulties in viewing motion slides in TIP endpoints connected to your Collaboration Server.

Bit Rate values per Resolution

Resolution Frame Rate Preset Bit Rate (Kbps)


Polycom, Inc. 125

Procedures

To select a video clip to be used for an IVR service:

1 Select IVR Service Properties > Video Services.

2 From the Video Welcome Slide list, select the video clip to be used for the IVR service.

Feature check-box



Polycom, Inc. 126

Addendum to Release Notes Polycom Lab Feature - Popup Site Name on Participant Join/LeavePolycom Lab features are new technology innovations that may not have undergone all levels of formal testing. We encourage you to try them out, but because they are not fully tested or supported, please don't deploy them in production environments.




Description of FeatureFrom version 8.7, Polycom® RealPresence Collaboration Server provides video AVC endpoints with indication on participant names upon their joining / leaving the conference.

Appearance Properties

Site name (at most times, the participant name), when enabled, appears accompanied by either a ‘+” upon participant joining the conference, or a ‘-’ upon leaving it. by default, when this feature is active, site name appears upon participant joining, but not upon its leaving.

The site name display duration is the same for joining and leaving, and ranges between 5 and 240 seconds with 10 seconds as the default.

Additional participants joining or leaving the conference, result in adding ‘...’ to the currently displayed site name, but no additional site names, as demonstrated below.

Feature Name: Popup Site Name on Participant Join/Leave



Feature Unit Tested




Polycom, Inc. 127

General Guidelines

● The site name display utilizes the message overlay mechanism, thus both are enabled/disabled simultaneously, and conform to identical settings, such as color, font size, and horizontal location.

● Message overlay is replaced by site name upon participant joining/leaving for the specified duration, after which the message overlay display is renewed for static message overlay.

Also, site name display is replaced by message overlay until the next participant joining/leaving.

The same applies to encrypted message overlay.

Site Name Display Triggering

● Both SVC and audio participants, although incapable of viewing the site name, trigger their site name display at the AVC endpoints.

● Content participants do not trigger this feature.

● Lync clients RealConnect-ed to conferences, do not trigger this feature.

● ITP, non-TIP, room triggers this feature, but is considered as a single participant, even in scenarios where the ITP room includes multiple endpoints. In the ITP room itself, the site name is displayed only on its main screen.

TIP enabled conferences are incompatible with this feature.

● Cloud Axis clients trigger display of site name, thus might view duplicate display of site name; one due to the Web client features, the other, due to this feature.

● When MCUs are cascaded, neither the cascading link, nor the cascaded MCU participants, trigger display of site name at the other MCU participants.

● WebRTC clients trigger this feature, however WebRTC endpoints do not display the site name message.

● Recording link participants do not trigger this feature (as there’s already a recording indication), however, site names is sent over the recording link.

The playback link acts exactly the opposite - The link triggers site name display, but the site name is not sent over the playback link video.


Polycom, Inc. 128


To enable/disable site name popup display:


2 Select the Layout Indications tab.

3 In the Textual site name display area (shown below), determine:

Whether to enable/disable site name display upon participant joining the conference.

Whether to enable/disable site name display upon participant leaving the conference.

The site name display Duration.


Pre-requisites● This feature is applicable only to AVC endpoints, and to CP Only and Mixed CP and SVC

conferences.





Feature check-box


Polycom, Inc. 129

ProceduresTo modify site name display duration, see the procedure for enabling/disabling this feature described above.

RELEASE NOTES Version 8.7.1 RealPresence Collaboration ...Version 8.7.1 - New Features List Polycom,...

Documents

Transcript of RELEASE NOTES Version 8.7.1 RealPresence Collaboration ...Version 8.7.1 - New Features List Polycom,...