Polycom RealPresence 1800, RealPresence 2000, RealPresence 4000 Administration Manual

Download

Page 1

ADMINISTRATION GUIDE

8.8 | December 2018 | 3725-74900-000B1

RealPresence® Collaboration Server

1800/2000/4000/Virtual Edition

Page 2

Copyright© 2018, 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 Drive San Jose, CA 95002 USA

Trademarks Polycom

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.

, the Polycom logo and the names and marks associated with Polycom products are

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.

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. To receive software information, as well as the open source software code used in this product, contact Polycom by email at

OpenSourceVideo@polycom.com.

Customer Feedback We are striving to improve our documentation quality and we appreciate your feedback. Email

your opinions and comments to DocumentationFeedback@polycom.com.

Polycom Support Visit the Polycom Support Center for End User License Agreements, software downloads,

product documents, product licenses, troubleshooting tips, service requests, and more.

Page 3

Contents

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Audience, Purpose, and Required Skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Privacy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Polycom and Partner Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

The Polycom Community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Product Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Supported Network Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

IP Conferencing Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

ISDN (Audio/Video) Conferencing Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Multipoint Conferencing Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Required Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

System User Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Administrator Read-only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chairperson . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Auditor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

User Interface Availability Based on User Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Navigating the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

The MCU Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

MCU Icons and States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Conferences List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Conferences List Toolbar Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

System Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

MCU State Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Port Usage Gauges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

List Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

RMX Management Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Frequently Used and Rarely Used Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Polycom, Inc. iii

Page 4

Contents

Conference Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Toolbar Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Install RMX Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Connect to the MCU with RMX Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Add an MCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Connect to an MCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Configure the Time Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Requesting and Adding Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Create a Certificate Signing Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Installing the Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Obtain the Display Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Integrate with the RealPresence Resource Manager System . . . . . . . . . . . . . . . . . . . . . . . . . 19

Overlay a Custom Logo on Conference Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Configure Required System Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Integrate with the RealPresence DMA System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Integrate with HARMAN Media Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Customizing the RMX Manager User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Switch the RMX Management Section View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Move Items in the RMX Management Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Restore Default RMX Manager User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Conference Profiles and Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Conference Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

View the List of Conference Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Add a New Conference Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Conference Profile Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Conference Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

View the List of Conference Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Add a New Conference Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Additional Conference Profile and Conference Template Tasks . . . . . . . . . . . . . . . . . . . . . . . 37

Edit a Conference Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Delete a Conference Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Export a Conference Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Import a Conference Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Edit a Conference Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Delete a Conference Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Export a Conference Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Import a Conference Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Polycom, Inc. iv

Page 5

Contents

Save an Ongoing Conference as a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Advanced Conferencing Profile Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Enable Recording in the Conference Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Change Position of the Conference Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Indicators for Microsoft Skype for Business Users . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Enable Multiple Content Resolutions (Transcoding) on TIP Endpoints . . . . . . . . . . . . . . . . . . 43

Binary Floor Control Protocol (BFCP) Support for TIP endpoints . . . . . . . . . . . . . . . . . . . . . . 44

Legacy Content for TIP Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

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

Conference Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Viewing Scheduled Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Scheduling a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Starting an Ad Hoc Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Other Ways to Start a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Working with Active Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

General Conference Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Viewing the List of Active Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Viewing the Properties of an Active Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Locking a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Unlocking a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Participant Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Viewing the List, State and Properties of Participants . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Adding Participants to an Active Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Moving Participants Between Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Sending a Message to Participants During a Conference . . . . . . . . . . . . . . . . . . . . . . . . 57

Restricting Content Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Designating a Participant the Lecturer in an Active Conference . . . . . . . . . . . . . . . . . . . . 58

Muting Participants Other Than Lecturer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Previewing a Participant’s Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Enabling Auto Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Enabling Customized Polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Canceling a Message Overlay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Adding a Participant in an Active Conference to the Address Book . . . . . . . . . . . . . . . . . 63

Viewing the List of Participants Awaiting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Content Sharing Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Giving Exclusive Content Sharing Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Canceling Exclusive Content Sharing Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Polycom, Inc. v

Page 6

Contents

Abort a Content Sharing Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Conference Recording Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Cascading Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Cascading Link Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Setting the Video Layout in Cascading conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Flags Controlling Cascade Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

DTMF Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Play Tone Upon Cascading Link Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Possible Cascading Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Basic Cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Basic Cascading Using IP Cascaded Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Dialing Directly to a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Dialing to an Entry Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Automatic Identification of the Cascading Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Basic Cascading Using ISDN-video Cascaded Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Network Topologies Enabling Content Sharing Over ISDN-video Cascaded Links . . 71

Guidelines for ISDN-video Cascaded Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Gateway to Gateway Calls via ISDN-video Cascading Link . . . . . . . . . . . . . . . . . . . . 72

Gateway to MCU Calls via ISDN-video Cascading Link . . . . . . . . . . . . . . . . . . . . . . . 73

MCU to MCU Calls via ISDN-video Cascading Link . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Collaboration Server Configuration Enabling ISDN-video Cascading Links . . . . . . . . 74

Conference Profile Definition 76

MCU Interoperability Table 77

Suppression of DTMF Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

System Flag Settings 79

Star Cascading Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Master-Slave Cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Cascade Enabled Participant Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Cascading via Entry Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Enabling Cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Creating the Dial-out Cascaded Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Monitoring Star Cascaded Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

H.239-enabled MIH Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

MIH Cascading Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Cascading Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

MIH Cascading Guidelines in CP Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Master - Slave Conferences 92

Video Session Mode, Line Rate and Video Settings 93

Polycom, Inc. vi

Page 7

Contents

MGC to Collaboration Server Cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Method I 95

Method II 96

User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

User Roles (Authorization Levels) and Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

View the List of Current Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Add a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Edit a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Delete a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Change a User’s Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Disable a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Enable a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Rename a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Add a Machine Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

View MCU Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Viewing the Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Adding a Group to the Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Adding a New Participant to the Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Participant Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Adding Participants from the Address Book to a Conference . . . . . . . . . . . . . . . . . . . . . . . . 108

Editing a Participant’s Address Book Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Deleting a Participant from the Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Copying or Moving a Participant in the Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Filtering the Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Exporting an Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Importing an Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Operator Conference and Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Operator Conference Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Defining Components Prerequisite for Operator Assistance . . . . . . . . . . . . . . . . . . . . . . . . . 113

Saving an Operator Conference to a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Starting an Operator Conference from a Template . . . . . . . . . . . . . . . . . . . . . . . . . 122

Monitoring Operator Conferences and Participants Awaiting Assistance . . . . . . . . . . . . . . . 123

Requesting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Participant Alerts List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Audible Alarm for Notifying on Required Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Polycom, Inc. vii

Page 8

Contents

Administration and Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

System and Participant Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Viewing System Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Viewing Participant Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Forcing Video Resource Allocation to CIF Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Viewing the Resource Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Resource Reports for Collaboration Servers 1800/2000/4000 . . . . . . . . . . . . . . . . . 130

Setting the Port Usage Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

View System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Enable SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Hot Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Enabling Hot Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Configuring the Hot Backup Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Modifying the Master MCU Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Audible Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Configuring Audible Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Replacing the Audible Alarm File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Customizing the Multilingual Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Banner Display and Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Software Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Backup Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Restore Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Download Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Ping the Collaboration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Configure Notification Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Retrieve Logger Diagnostic Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Information Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Standard Security Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Ultra Secure Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Network Intrusion Detection System (NIDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Using the Information Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Auditor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Auditor Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Retrieving Auditor Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Auditor File Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Audit Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Alerts and Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

ActiveX Bypass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

. . 151

Polycom, Inc. viii

Page 9

Contents

Installing ActiveX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Collaboration Server Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Reset the Collaboration Servers 2000/4000/1800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Collaboration Server Virtual Edition Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Entry Queues, Ad Hoc Conferences and SIP Factories . . . . . . . . . . . . . . . . . . 161

Entry Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Entry Queue List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Transit Entry Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

IVR Provider Entry Queue (Shared Number Dialing) . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Call Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Guidelines for Setting the Entry Queue as IVR Provider . . . . . . . . . . . . . . . . . . . . . 166

Using External IVR Services via the MCCF-IVR . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Call Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Call Flow for Standalone SIP Endpoints 167

Call Flow for Standalone TIP Endpoints 168

Call Flow for TIP Endpoints from a Polycom ITP System 168

Guidelines for Using External IVR Services via the MCCF-IVR Package . . . . . . . . 169

Configuring the MCU to Support External IVR Services via the MCCF-IVR . . . . . . 169

SIP Factories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

SIP Registration & Presence for Entry Queues and SIP Factories with SIP Servers . . . . . . 171

Guidelines for registering Entry Queues and SIP Factories with SIP Servers . . . . . 172

Monitoring Registration Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Ad Hoc Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Gateway to Polycom® RealPresence Distributed Media Application™ (DMA™) System . . . 173

System Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Managing System Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Add a System Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Edit a System Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Delete a System Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

System Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Call Detail Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Enabling a CDR Backup Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Enabling Multi-Part CDRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

View the MCU CDR List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Retrieve and Save a CDR for Viewing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Retrieve and Save CDRs for Billing and Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

CDR Fields in Unformatted Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Polycom, Inc. ix

Page 10

Contents

The Conference Summary Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Event Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Standard Event Record Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Event Specific Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Active Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Disconnection Causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

IP Disconnection Causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

ISDN Disconnection Causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Disconnection Cause Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Hardware Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Viewing the Status of the Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Identifying the Types of Video Cards in an MCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

Viewing the Properties of Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

Viewing an MCU or Video Card Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

Viewing Active Alarms for an MCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

Running Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

ISDN Diagnostic on RMX 1800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Restore RealPresence Collaboration Server Defaults . . . . . . . . . . . . . . . . . . . 315

Perform a Standard Restore from USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

Perform a Comprehensive Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

Perform a Restore While in Ultra Secure Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

Appendix - Polycom Lab Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

Lab Features Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

Activate Experimental Lab Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Current RealPresence Collaboration Server Lab Features . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Discussion Mode Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Description of Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Layout Usage Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

System Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

Guidelines to Related Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

Interaction with Other Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

Enable and Disable this Polycom Lab Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Exclude Inactive-Video Participants from Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Description of Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Interactions with Other Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

Polycom, Inc. x

Page 11

Contents

Enable and Disable this Polycom Lab Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

Popup Site Name on Participant Join/Leave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

Description of Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

Appearance Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

General Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Site Name Display Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

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

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Using Video Clips for IVR Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

Description of Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Video Slides Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

System Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

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

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

Appendix - Secure Communication Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Certificate Configuration and Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Certificate Template Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Certificate Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Configure Certificate Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Switching to Secure Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Purchasing and Installing a Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

System Flags Controlling Secure Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

Enabling Secure Communication Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

Alternate Management Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

Appendix - Ad Hoc Conferencing and External Database Authentication . . . 338

Ad Hoc Conferencing without Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

Ad Hoc Conferencing with Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

Entry Queue Level - Conference Initiation Validation with an External Database Application 341

Conference Access with External Database Authentication . . . . . . . . . . . . . . . . . . . . . . . . . 343

Conference Access Validation - All Participants (Always) . . . . . . . . . . . . . . . . . . . . . . . 343

Conference Access Validation - Chairperson Only (Upon Request) . . . . . . . . . . . . . . . . 345

System Settings for Ad Hoc Conferencing and External Database Authentication . . . . . . . . 346

Ad Hoc Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

Authentication Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

MCU Configuration to Communicate with an External Database Application . . . . . 347

Enabling External Database Validation for Starting New Ongoing Conferences . . . 349

Enabling External Database Validation for Conferences Access . . . . . . . . . . . . . . . 350

Polycom, Inc. xi

Page 12

Contents

Appendix - Media Traffic Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

Traffic Shaping Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

System Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

Capacity Reduction During Traffic Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

System Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

Appendix - Modular MCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

System Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

MCU Operation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

Modular MCU Implementation Aspects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

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

Soft Blade Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

Monitoring Modular MCU Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

Monitoring Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

MMCU Impact on Participant Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

Faults and Active Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

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

MMCU Components Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

IP Address Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

RDP Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

Polycom RealConnect Call Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

Direct Call Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

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

Enabling RDP Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

Polycom MCU Video Quality Dialog on DMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

IP Network Services - SIP Servers Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

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

for Business . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

Monitoring RDP Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

Modular MCU Resource Consumption and Management . . . . . . . . . . . . . . . . . . . . . . . 365

Resource Weight Factoring in Resource Management 365

Resource Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

Port Usage for Skype for Business . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Modular MCU Security Aspects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Modular MCU Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Logger Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Logs Format 368

Logging Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

Logs at the Soft Blades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Call Logs 369

Polycom, Inc. xii

Page 13

Contents

General Logs 369

Filtering Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

Modular MCU Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

Virtual Edition Modular MCU Upgrade Storage Requirements . . . . . . . . . . . . . . . . . 371

Monitor Soft Blades Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

Appendix - Polycom Open Collaboration Network (POCN) . . . . . . . . . . . . . . . 372

Collaboration With Cisco’s Telepresence Interoperability Protocol (TIP) . . . . . . . . . . . . . . . 372

Deployment Architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

Single Company Model - Polycom and Cisco Infrastructure . . . . . . . . . . . . . . . . . . . . . . 373

Call Flow - Multipoint Call with DMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

Call Flow - Multipoint Call without DMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

Company to Company Models Using a Service Provider . . . . . . . . . . . . . . . . . . . . . . . . 378

Model 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

Call Flows - Multipoint Call via Service Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380

Model 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380

Call Flow - Multipoint Call via Service Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381

Model 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381

Deployment Architecture Composition 382

Call Flow - Multipoint Call via Service Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

Model 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384

Gatekeepers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384

Standalone Polycom Resource Manager/DMA System as a Gatekeeper . . . . . . . . 384

Standalone Cisco IOS Gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

Neighbored Cisco IOS and Polycom Resource Manager/DMA Gatekeepers . . . . . 385

DMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

CUCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

Configuring the Cisco and Polycom Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

Cisco Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

CUCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386

IOS Gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386

IOS and DMA/Resource Manager Gatekeepers (Neighbored) . . . . . . . . . . . . . . . . 386

Polycom Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386

Configuring the Collaboration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387

Configuring DMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387

Configuring the Resource Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387

Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388

Entry Queue and Virtual Entry Queue Access 389

Polycom, Inc. xiii

Page 14

Contents

Configuring the Conference and Entry Queue IVR Services 389

Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389

Procedure 1: Set the MIN_TIP_COMPATIBILITY_LINE_RATE System Flag . . . . . 390

Procedure 2: Configure Collaboration Server to Statically Route Outbound SIP Calls to

DMA or CUCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

Procedure 3: Configure Collaboration Server H.323 Network Service to register with

DMA/Resource Manager gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391

Procedure 4: Configure a TIP Enabled Profile on the Collaboration Server . . . . . . . 392

Procedure 5: Configuring an Ad Hoc Entry Queue on the Collaboration Server if DMA is

not used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

Procedure 6: Configuring a Meeting Room on the Collaboration Server . . . . . . . . . 397

Procedure 7: Configuring Participant Properties for Dial Out Calls . . . . . . . . . . . . . 397

Collaboration with Microsoft and Cisco . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398

Deployment Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Call Flow - Multipoint Calls using DMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401

Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402

DMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402

Microsoft Lync Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

CUCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

Solution Interoperability Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

TIP Layout Support & Resource Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

Resource Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

Configuring Microsoft, Cisco and Polycom Components . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

Content Sharing Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410

Polycom Immersive Telepresence Systems (ITP) Version 3.0.3: 410

Polycom video conferencing endpoints (HDX) Version 3.0.3: 410

Cisco TelePresence® System (CTS) Versions 1.7 / 1.8: 410

Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

Resolution Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415

Operations During Ongoing Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416

Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416

CTS Participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416

Lync Participants (RTV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418

Known Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419

Appendix - Direct Connection to the RealPresence Collaboration Server . . . 421

Establish a Direct Connection to the RealPresence Collaboration Server . . . . . . . . . . . . . . 421

Configure the Connecting Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422

Cable the Workstation Connection to the RealPresence Collaboration Server . . . . . . . 422

Polycom, Inc. xiv

Page 15

Contents

Connect to the MCU with the RMX Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

Configure the Primary Management Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424

Connect the Alternate Management Network (2000/4000) . . . . . . . . . . . . . . . . . . . . . . . . . . 424

Connecting the Collaboration Server via Modem (2000/4000) . . . . . . . . . . . . . . . . . . . . . . . 425

Configure the Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

Create a Dial-up Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

Appendix - Homologation for Brazil . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

H.323 & SIP Protocol Flag Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

H.323 & SIP Flag Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

Flag name: SIP_TIMERS_SET_INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

Flag name: H323_TIMERS_SET_INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428

Flag name: DISABLE_DUMMY_REGISTRATION . . . . . . . . . . . . . . . . . . . . . . . . . . 428

Polycom, Inc. xv

Page 16

Before You Begin

The Polycom® RealPresence® Collaboration Server (RMX) Administrator Guide provides instructions to

configure and administer your RealPresence Collaboration Server (RMX) 1800, 2000, 4000, and Virtual Edition Multipoint Control Unit (MCU).

Audience, Purpose, and Required Skills

The primary audience for this guide is system administrators and network engineers who configure, maintain, and support the telecommunications infrastructure and video conferencing environment. Operators and participants assigned to the chairperson role also find task information in this guide useful.

To perform some of the implementation and maintenance tasks described in this guide, the administrator should have basic technical knowledge and skills in the following disciplines:

● Current telecommunications practices, protocols, and principles

● Telecommunication basics, video teleconferencing, and voice or data equipment

● Virtual machine environments

● Networking, security certificates, and software configuration

Privacy

Privacy-related options

Available

Option name in UI

Manage call detail records (CDR)

Manage user credentials

Manage address book Yes - multiple See the Address Book section in this guide.

Manage data backups Yes - multiple See the Address Book , Enabling a CDR Backup Alarm , and Cyclic File

Manage audit and log files

Polycom, Inc. xvi

settings

Yes - multiple See the Call Detail Records section in this guide.

Yes - multiple See the User Management and User Management Flags sections in this

Auto Audit and log files are automatically deleted by the system (oldest first)

Location in the system

guide.

System Flag sections in this guide.

when the system reaches the auditor event file limit of 1000. Also see the Cyclic File System Flag section in this guide.

Page 17

Before You Begin

How Data Subject Rights are supported

Data Subject Right Method of support

Right to be informed What customer personal data is collected?

See the Purposes for processing personal data table in this topic.

How is customer personal data is used?

See the Purposes for processing personal data table in this topic.

How long is customer personal data kept?

Any personal data made available when working with Polycom support is only retained until each specific issue is resolved and then it is purged.

Is customer personal data shared with any third parties and if so, who?

If personal data is made available when working with Polycom support, this data may be shared with contracted third-party engineering companies.

How can a data subject be notified of a data breach?

Data Subjects have a right to be notified when their data has been processed without authorization. The product administrator is able to monitor and identify when security anomalies have occurred. See the How admin can be informed of

any security anomalies (including data breach) table in this topic.

Right to access (view and/or obtain a copy of all personal data for a specific data subject)

Right to rectification (make corrections to inaccurate or incomplete personal data)

Right to erasure (remove all personal data)

Right to restrict processing (temporarily cease all processing of personal data)

Personal data about specific participants in conferences can be viewed or downloaded via the CDR. See the Retrieve and Save a CDR for Viewing section in this guide.

Personal data related to users who are Administrators, Operators and Auditors can be viewed using RMX Manager or RealPresence Resource Manager (if configured). See the User Management section in this guide.

Personal data about specific participants in conferences cannot be edited or updated because the information derives from the device of origin.

Personal data related to users who are Administrators, Operators and Auditors can be edited or updated using RMX Manager or RealPresence Resource Manager (if configured). See the User Management section in this guide.

Polycom does not manipulate data made available during the support process, so any rectification of inaccuracies of personal data must be performed by customer directly.

For details on how to erase customer personal data from the system, see the

How customer personal data is deleted table in this topic.

Any customer personal data made available when working with Polycom support will be erased by requesting erasure through your Polycom support representative.

Not applicable.

Polycom, Inc. xvii

Page 18

Before You Begin

Data Subject Right Method of support

Right to data portability (receive a copy of all personal data in a commonly used, machine-readable format)

Right to object to processing (permanently stop all processing of personal data)

Purposes for processing personal data

Personal Data Category

Call detail records (CDR)

Type of Personal Data Purpose of Processing Interface type

All of the following for both near and far endpoints:

• Name

• Status

• Role

• IP Address/Phone

• Alias Name/SIP Address

• Lync/Skype user name

CDRs can be downloaded in XML format to a USB device. See the Retrieve and

Save a CDR for Viewing section in this guide.

The Address Book can be exported in XML format. See the Exporting an

Address Book section in this guide.

Audit and log files can be downloaded in plain text format.See the Retrieve

Logger Diagnostic Files section of this guide.

Not applicable.

• Maintaining call history

• Troubleshooting call errors

or performance issues

• RMX Manager

• RealPresence Resource

Manager (if configured)

• Download to USB

• API

Use the TRANS_CDR_LIST and TRANS_CDR_FULL APIs to retrieve CDRs.

All RMX APIs are available at Polycom Support page. See the RMX API SDK for your version of the product.

User credentials

Polycom, Inc. xviii

All of the following:

• User name

• Password

• Authorization level

• RealPresence Resource

Manager (if configured)

Page 19

Before You Begin

Personal Data Category Type of Personal Data Purpose of Processing Interface type

Address book All of the following:

• Name

• Endpoint website

• IP Address (H.323 and

SIP)

• Alias Name/Type (H.323

Only)

• SIP Address

• Endpoint Website IP

Address (IP Only)

Audit and log files

• Admin and User

credentials (excluding passwords)

• All CDR details

• Admin and User actions

• Ease of use for dialing

participant

• Store frequently used

information

• Admin and user activity

logging

• Maintain history of

configuration changes

• Troubleshooting system

issues

• RMX Manager

• RealPresence Resource

Manager (if configured)

• RMX Manager

• RealPresence Resource

Manager (if configured)

• Download to USB

• API

APIs are used to retrieve audit and log files. Use TRANS_AUDIT_FILE_SU MMARY_LIST API for audit files and TRANS_LOG_FILE_LIST for log files.

All RMX APIs are available at Polycom Support page. See the RMX API SDK for your version of the product.S

How admin can be informed of any security anomalies (including data breach)

Security anomaly type

All active alarms

Where to check Recommended frequency to check

See the Active Alarms , Hardware

Monitoring and System Flags sections in

this guide.

The alarms are checked every 3 sec. If there is new alarm, the alarm list is updated with new list of alarms. Recommend log review once daily

Polycom, Inc. xix

Page 20

Before You Begin

How customer personal data is deleted

Data type Steps to delete Deletion method

Call detail record (CDR)

User credentials

Address book

Data backups

Audit and log files

By default, CDRs are overwritten by new CDRs periodically. If required, CDR can be deleted through the command line interface (ssh)

CDRs can also be deleted by performing a standard or comprehensive restore operation. See the Restore

RealPresence Collaboration Server Defaults section in

this guide.

See the Delete a User section in this guide. Simple delete

See the Deleting a Participant from the Address Book section in this guide.

The Address Book is also deleted by performing a standard or comprehensive restore operation. See the

Restore RealPresence Collaboration Server Defaults

section in this guide.

Backup are stored in Local system. Back up files can be deleted from local Windows / Linux

system. The local system is the machine where the backup file is stored using RMX Manager.

Audit and log files are automatically deleted by the system (oldest first) when the system reaches the auditor event file limit of 1000.

Audit and log files are also deleted by performing a standard or comprehensive restore operation. See the

Restore RealPresence Collaboration Server Defaults

section in this guide.

To do this:

1 Enable SSH 2 Go to > /opt/mcu/output/cdr 3 rm -f * cdr

Standard restore – simple delete Comprehensive restore – System

hard disk file partition is formatted

If using the RMX Manager – simple delete

Standard restore – simple delete Comprehensive restore – System

hard disk file partition is formatted

Delete the backup file from specific path on the local system.

To do this:

1 Enable SSH 2 Go to > opt/mcu/mcms/Logfiles 3 Select the module > cd Logger 4 rm -f * (or the file name )

Standard restore – simple delete Comprehensive restore – System

hard disk file partition is formatted

Getting Help

For more information about installing, configuring, and administering Polycom products, see the Polycom

Document Library.

Polycom and Partner Resources

See the following Polycom documentation for related information on this product:

● Polycom

Guide

● Polycom

Polycom, Inc. xx

RealPresence® Collaboration Server Release Notes

RealPresence® Collaboration Server 1800/2000/4000/Virtual Edition Getting Started

RealPresence® Collaboration Server Hardware Guide for the associated appliance edition

Page 21

Before You Begin

● Polycom® RealPresence® Collaboration Server 1800/2000/4000 Deployment Guide for Maximum Security Environments

See the Polycom Document Library to learn more about the following RealPresence Platform products:

● Polycom

RealPresence® DMA® 7000

RealPresence® Resource Manager

RealPresence® Web Suite

RealPresence® Media Suite

RealPresence® Access Director™

● Polycom® RealPresence® Group Series

The Polycom Community

The Polycom Community gives you access to the latest developer and support information. Participate in discussion forums to share ideas and solve problems with your colleagues. To register with the Polycom Community, simply create a Polycom online account. When logged in, you can access Polycom support personnel and participate in developer and support forums to find the latest information on hardware, software, and partner solutions topics.

Polycom, Inc. xxi

Page 22

Product Overview

The RealPresence Collaboration Server (RMX) 1800, 2000, 4000, and Virtual Edition Multipoint Control Units (MCUs) are high performance, scalable MCUs that provide a feature-rich, multipoint audio and video conferencing experience.

Product Features

The RealPresence Collaboration Server supports the following features audio and video conferencing features.

Supported Features for Conferencing

Feature Name Description

Polycom Open Collaboration Network

Presence in Microsoft Office Communications, Lync, or Skype for Business

Cascading Conferences The RealPresence Collaboration Server can merge multiple conferences into a

Content Sharing The RealPresence Collaboration Server supports sharing of documents,

Video Preview The RealPresence Collaboration Server enables you to preview video and the

The Polycom Open Collaboration Network (POCN) enables Polycom, Microsoft, and Cisco users, within their own environment, to participate in the same conference running on a RealPresence Collaboration Server.

The RealPresence Collaboration Server also natively interoperates with Cisco Telepresence Systems and Polycom Telepresence and video conferencing endpoints, ensuring optimum quality multiscreen, multipoint calls.

Registration and Presence enables Microsoft Lync or Skype for Business users to see user and meeting room status (Available, Busy, or Offline). Users can connect to these contacts and resources directly from the buddy list.

single conference. This enables RealPresence Collaboration Servers to split a larger number of participants and resources.

Microsoft Lync or Skype for Business users can also connect (via Polycom RealConnect) to a RealPresence Collaboration Server meeting room to a conference running on the Microsoft AVMCU.

presentations, videos, or other content with conference participants. HD H.264 Content and H.264 Content for Cascading links allow conference

participants to receive high-quality content in both standard conferences and cascaded conferences.

video quality sent and received by participants and the conference. This enables users to identify possible quality degradation. The RealPresence Collaboration Server supports H.264 High Profile with video preview.

Polycom, Inc. 1

Page 23

Product Overview

Supported Features for Conferencing (continued)

Feature Name Description

Indicators The RealPresence Collaboration Server offers different types indicators and

allows you to design the layout of those indicators on some participant’s screens:

• Network Quality — Indicates the quality of the video channels

• Recording — Indicates that the system is recording the conference

• Audio and Video Participants — Identifies the number of audio and video

participants in the conference (AVC only)

Auto Scan and Customized Polling in Video Layout

Packet Loss Compensation Polycom LPR and DBA

Lecture Mode Lecture Mode enables all participants to view the lecturer in full screen while

NoiseBlock™ The RealPresence Collaboration Server automatically detects and mutes AVC

The RealPresence Collaboration Server enables you to define a single cell in the conference layout to cycle the display of participants that aren’t in the conference layout.

Polycom Lost Packet Recovery (LPR) and Dynamic Bandwidth Allocation (DBA) help minimize media quality degradation that can result from packet loss in the network.

The Polycom LPR algorithm uses Forward Error Correction (FEC) to create additional packets that contain recovery information. DBA allocates the bandwidth needed to transmit the additional packets.

the conference lecturer sees all the other conference participants in the selected layout. When the number of sites or endpoints exceeds the number of video windows in the layout, the system switches among participants every 15 seconds.

endpoints that have a noisy audio channel.

Supported Network Configurations

The RealPresence Collaboration Server supports the following conferencing network configurations:

● IP conferencing network

● ISDN (Audio/Video) conferencing network

● Multipoint conferencing network

IP Conferencing Network

Typically, the RealPresence Collaboration Server 2000 and RealPresence Collaboration Server, Virtual Edition use a single LAN port for system management, signaling, and IP conferencing. You can separate the management and signaling networks when deploying RealPresence Collaboration Server 2000 into Maximum Security Environments.

The RealPresence Collaboration Server 1800 and RealPresence Collaboration Server 4000 use separate LAN ports for system management and IP conferencing.

Polycom, Inc. 2

Page 24

Product Overview

ISDN (Audio/Video) Conferencing Network

To enable ISDN-video and ISDN-voice participants to connect to the MCU, you must define an ISDN (audio/video) Network Service. You can define only two ISDN (audio/video) Network Services, of the same Span Type (E1 or T1). Each Network Service can attach spans from either or both cards.

Most of the parameters of the first ISDN (audio/video) Network Service are configured in the Fast Configuration Wizard, which runs automatically if an RTM ISDN card is detected in the RealPresence

Collaboration Server during first time setup. For more information, see the RealPresence Collaboration Server (RMX) 1800/2000/4000/Virtual Edition Getting Started Guide.

The RealPresence Collaboration Server 1800 with three DSP cards supports ISDN (Audio/Video) networks. The RealPresence Collaboration Server 2000 and 4000 also support ISDN (Audio/Video) networks. For more information on ISDN (Audio/Video) support, see Defining ISDN (audio/video) Network Services.

Multipoint Conferencing Network

Multipoint Video Conferencing using a RealPresence Collaboration Server

Required Software Components

The required software components for RealPresence Collaboration Server are as follows:

RealPresence Collaboration Server Ver sion

RealPresence Collaboration Server 1800/2000/4000

RealPresence Collaboration Server, Virtual Edition

Polycom, Inc. 3

Required Software Components

• .Net Framework 3.5 SP1 or higher is required and installed

automatically.

• Internet Explorer to allow the running of Signed ActiveX.

• .Net Framework 2.0 SP1 or higher is required and installed

automatically.

• Internet Explorer must be enabled to allow the running of Signed

ActiveX. If ActiveX installation is blocked, see ActiveX Bypass.

Page 25

Product Overview

System User Types

RealPresence Collaboration Server users are identified by their role and associated authorization level, which determines a user’s capabilities within the system. The RealPresence Collaboration Server supports the following user authorization levels:

● Administrator

● Operator

● Administrator Read-only

● Chairperson

● Auditor

Note that conference participants are not considered “users” of the RealPresence Collaboration Server as they never access the MCU user interface. However, conference participant information can be stored in the RealPresence Collaboration Server Address Book for scheduling and management purposes.

Machine Accounts

User names can be associated with servers (machines) to ensure that all users are subject to the same account and password policies, but these are not considered a user type. For more details, see Defining a Machine Account.

Administrator

A RealPresence Collaboration Server system administrator can define and delete other users and perform all system configuration and maintenance tasks.

The RealPresence Collaboration Server, by default, ships with a single pre-defined administrator account which provides initial system access. This administrator account is:

● User name: SA_PLCM_Integration

● Password: Polycom_CS

Upon initial login, the RealPresence Collaboration Server displays an active alarm indicating the existence of this SA_PLCM_Integration default user.

The RealPresence administrator account as well, thus allowing the RealPresence DMA system to log into the RealPresence Collaboration Server. However, for security reasons, Polycom strongly recommends immediately setting up a new administrator account on both the RealPresence Collaboration Server and the RealPresence DMA system and deleting the default administrator account.

Distributed Media Application™ (DMA®) is configured to recognize this default

Administrator Read-only

A user with Administrator Read-only permissions has the same viewing and monitoring permissions of an administrator. However, this user is limited to creating system backups and cannot perform any other configuration or conference related operation.

Polycom, Inc. 4

Page 26

Product Overview

Operator

An Operator can manage Meeting Rooms, Profiles, Entry Queues, and SIP Factories, and can also view the Collaboration Server configurations, but cannot change them.

Administrator and Operator users can verify which users are defined in the system. Neither of them can view the user passwords, but an Administrator can change a password.

Chairperson

A Chairperson can only manage ongoing conferences and participants, in both single and cascading RealPresence Collaboration Server scenarios. The Chairperson does not have access to the Collaboration Server configurations and utilities.

Auditor

An Auditor can only view Auditor Files and audit the system.

User Interface Availability Based on User Type

The following table identifies which user interface panes, features, and functions are available to which type of RMX system user.

Admin Chairperson Operator

Tab Na me

General      

Advanced     

Gathering Settings

Video Quality

Video Settings

Audio Settings

Customized Polling

Skins      

IVR      

CP SVC Mixed VSW CP SVC Mixed VSW CP SVC Mixed VSW

    

     

     

Information      

Recording      

Polycom, Inc. 5

Page 27

Product Overview

Admin Chairperson Operator

Tab Na me

Site Names      

Message Overlay

Network Services

CP SVC Mixed VSW CP SVC Mixed VSW CP SVC Mixed VSW

     

     

Navigating the System

The RealPresence Collaboration Server can be managed and monitored with either the RMX Manager application on a Windows-based system or the RMX Web Client using Internet Explorer. In general, the tasks documented in this guide apply to both RMX Manager and the RMX Web Client, but we document them from the RMX Manager interface.

The RMX Manager main screen is displayed when it is connected to at least one RealPresence Collaboration Server. The RMX Manager main screen and the RMX Web Client main screen are similar except RMX Manager includes an MCU pane, as it can manage multiple MCUs. RMX Manager displays the RealPresence Collaboration Server functions based on the authorization level of the logged in user.

The MCU pane is available to all users. Only one RealPresence Collaboration Server can be selected in the MCU pane. The menu items, RMX management, address book, conference templates, and all properties that are applicable to the selected MCU are available.

Polycom, Inc. 6

Page 28

Product Overview

The MCU Pane

The MCU pane includes the MCU list and an MCU toolbar.

For each listed RealPresence Collaboration Server, the system displays the following information:

MCU Menu Description

MCU Display Name

IP Address

Status

Product Type

The name of the RealPresence Collaboration Server and its icon according to its type and connection status.

The IP address of the RealPresence Collaboration Server.

The MCU status:

• Connected: The MCU is connected to RMX Manager and can be managed

by an RMX Manager user.

• Disconnected: The MCU is disconnected from RMX Manager.

•Major: The MCU has a major problem. The MCU behavior is affected and

proper attention is required.

The RealPresence Collaboration Server type: RMX 1800/2000/4000/800VE. Before connecting to the MCU for the first time, the RealPresence Collaboration Server type is unknown and so RMX is displayed as a general indication.

Monitored When selected, indicates that the conferences running on this MCU are

automatically added to the conferences list and monitored. To stop monitoring the conferences running on this MCU and the participants, clear the Monitored check box.

Video Resources

Audio Resources

The number of video resources available for conferencing.

The number of audio resources available for conferencing.

Polycom, Inc. 7

Page 29

Product Overview

MCU Icons and States

The MCU icons and states are as follows:

MCU Icon Description

RealPresence Collaboration Server (RMX) 2000, disconnected

RealPresence Collaboration Server (RMX) 2000, connected

RealPresence Collaboration Server (RMX) 4000, disconnected

RealPresence Collaboration Server (RMX) 4000, connected

RealPresence Collaboration Server 1800, disconnected

RealPresence Collaboration Server 1800, connected

RealPresence Collaboration Server, Virtual Edition, disconnected

RealPresence Collaboration Server, Virtual Edition, connected

Conferences List

The Conferences List includes all the conferences currently running on the MCU along with the Status, Conference ID, Start Time, and End Time data.

The number of ongoing conferences is displayed in the title of the pane.

Polycom, Inc. 8

Page 30

Product Overview

Conferences List Toolbar Options

If you are logged in as an operator or administrator, then the toolbar options are as follows:

Conferences List Toolbar Options

Toolbar Option Permission Role

New Conference • Operator

• Administrator

Delete Conference • Operator

• Administrator

Save Conference to Template • Operator

• Administrator

Start/Resume/Pause Recording • Operator

• Administrator

Stop Recording • Operator

• Administrator

Find Conference • Operator

• Administrator

Chairperson Password Chairperson only

Refresh Chairperson only

System Status Bar

The Status Bar is available to operators and administrators to display the system alerts, participant alerts, port usage gauges, and MCU state indicator. The information included in the status bar varies with the product model.

MCU State Indicator

The MCU State Indicator is available to chairpersons, operators, and administrators.

The MCU State indicator displays one of the following:

MCU State Indicator

Option Description

The MCU is starting up. The time remaining until the system start-up is complete. The Time remaining is displayed within parentheses. The blue progress indicator bar indicates the start-up progress.

Polycom, Inc. 9

Page 31

Product Overview

MCU State Indicator (continued)

Option Description

The MCU is functioning normally.

The MCU has a major problem. The MCU behavior could be affected and attention is required.

Port Usage Gauges

The Port Usage Gauges are displayed on the Status Bar at the bottom of the interface.

For RealPresence Collaboration Server 1800/2000/4000, the Port Usage Gauge displays:

● Total number of video or voice ports

The port information in the system according to the video or voice port configuration. The Audio gauge is disp layed only if audio ports are alloc ated by the a dministrator, otherwise only the vid eo por t gauge is displayed.

● Number of video and voice ports in use

● High port usage threshold

Polycom, Inc. 10

Page 32

Product Overview

For RealPresence Collaboration Server, Virtual Edition, the Port Usage Gauge displays:

● Total number of video ports in the system

● Number of video ports in use

● High port usage threshold

The basic unit used for reporting resource usage in the Port Gauges is HD720p30. Usage numbers are rounded to the nearest integer.

List Pane

The List Pane displays details of the item selected in the Conferences pane or RMX Management pane. The

title of the pane changes according to the selected item.

Example: When an ongoing conference is selected in the Conferences pane, the list and parameters of the connected participants is displayed.

Selecting an item in the RMX Management pane lists the items currently defined.

Example: If the Users item is selected, a list of system users defined for the MCU is displayed.

Address Book

The Address Book is available to chairpersons, operators, and administrators. The Address Book displays a list of participants and groups that are defined on the MCU. The information in the Address Book can be modified only by an administrator. All system users can view and use the Address Book to assign participants to conferences. The Quick Search field displays all the available options in the Address Book.

Polycom, Inc. 11

Page 33

Product Overview

The Address Book has two sections.

● The Hierarchy section displays a hierarchy of groups, which provides an easy way to manage a collection of participants and their associated endpoints. For example, if you frequently conduct conferences with the marketing department, create a group called “Marketing Team” that contains the endpoints of all members of the marketing team. Double-clicking a group on the navigation pane displays the group participants and sub-groups in the List pane.

● The All Participants section displays the single unique entity of all the participants in a single level. When adding a participant to a group, the system adds a link to the participant’s unique entity that is stored in the All Participants list. The same participant may be added to many groups at different levels, and all these participant links are associated with the same definition of the participant in the All Participants list. If the participant properties are changed in one group, they will be changed in all groups.

The Participants List in the Address Book displays the following information for each participant:

Field/Option Description

Type Indicates whether the participant is a video ( ) or voice ( ).

Name Displays the name of the participant.

IP Address/Phone Enter the IP address of the participant’s endpoint.

• For H.323 participant define either the endpoint IP address or alias.

• For SIP participant define either the endpoint IP address or the SIP address. Note: This field is removed from the dialog box when the ISDN (audio/video) protocol is

selected.

Network The network communication protocol used by the endpoint to connect to the conference:

• H.323

• SIP

• ISDN (audio/video)

Dialing Direction Dial-in – The participant dials in to the conference.

Dial-out – The Collaboration Server dials out to the participant.

Encryption Indicates whether the endpoint uses encryption for its media.

The default setting is Auto, indicating that the endpoint must connect according to the conference encryption setting.

On first access, the RMX Address Book appears on the main RMX Manager page. You can hide the Address Book pane by clicking the anchor pin.The Address Book pane closes and a tab appears at the right edge of the screen. If it is hidden, double-click the Address Book tab on the right to unhide it.

RMX Management Pane

The RMX Management pane is available to operators and administrators. The RMX Management pane lists the entities that are to be configured to enable the RealPresence Collaboration Server to run conferences. Only users with administrators permission can modify these parameters.

The RMX Management pane is divided into two sections:

● Frequently Used – Parameters often configured, monitored, or modified.

Polycom, Inc. 12

Page 34

Product Overview

● Rarely Used – Parameters configured during initial system setup and rarely modified afterward.

You can toggle between toolbar and list views in the RMX Management pane, and you can move items between these two sections to customize the management tasks per system user.

In list view, you can toggle items between the Frequently Used and Rarely Used sections depending on the operations you most commonly perform and the way you prefer to work with the RMX Web Client. This option does not work in toolbar view as all items are represented by icons.

Frequently Used and Rarely Used Sections

You can expand or collapse items between the frequently used and rarely used sections. You can also move the items within and between the frequently used and rarely used sections by dragging icons of the item to the appropriate position.

An indicator line ( ) appears indicating the new position of the icon.

Conference Templates

Administrators and operators can create, save, schedule, and activate identical conferences using conference templates.

A conference template does the following:

● Saves the conference profile

● Saves all participant parameters including the Personal Layout and Video Forcing settings

● Simplifies telepresence conference setup where precise participant layout and video forcing settings

are crucial

Polycom, Inc. 13

Page 35

Product Overview

The MCU initially displays the conference templates list as a closed tab in the RMX Manager main screen. The tab indicates the number of saved conference templates.

Toolbar Buttons

The Conference Template toolbar includes the following buttons:

Conference Templates – Toolbar Buttons

Button Description

New Conference Template Creates a new Conference Template.

Delete Conference Template Deletes the Conference Template(s) that are selected in the list.

Start Conference from Template Starts an ongoing conference from the Conference Template that has

an identical name, ID parameters and participants as the template.

Schedule Reservation from Template Creates a conference Reservation from the Conference Template

with the same name, ID, parameters and participants as the Te mp l at e .

Opens the Scheduler dialog box enabling you to modify the fields required to create a single or recurring Reservation based on the template. For more information see Scheduling Conferences Using

the Reservation Calendar.

The Conferences List toolbar includes the following button:

Conferences List – Toolbar Button

Button Description

Save Conference to Template Saves the selected ongoing conference as a Conference Template.

Polycom, Inc. 14

Page 36

Getting Started

This section describes the tasks that you may need to complete (based on your system design and installation) to configure the Polycom RealPresence Collaboration Server after first-time setup.

Install RMX Manager

The RealPresence Collaboration Server can be managed and monitored with either the RMX Manager application on a Windows-based system or the RMX Web Client application using Internet Explorer. For the most part, Polycom recommends using RMX Manager to configure and manage the RealPresence Collaboration Server. However, use the RMX Web Client when direct access to a single RealPresence Collaboration Server, Appliance Edition is required.

To install RMX Manager:

1 Access Polycom Support at support.polycom.com. Polycom recommends using Microsoft Internet

Explorer for the download.

You can also install RMX Manager from the RMX Web Client login page.

2 In the Documents and Downloads section, select UC Infrastructure as the Product Type, your

model of the RealPresence Collaboration Server as the Product, and click Go.

3 Select the appropriate version of the Local Web Client (RMX Manager).

4 When prompted, accept the End User License Agreement and the Export Restrictions

Agreement.

5 When prompted, click Open and navigate to the

RmxManagerInstallerMsi

6 Double-click

7 Follow the directions for the install wizard.

setup.exe

folder.

to install RMX Manager.

RMX_x-x-x-nnnn_LocalWebClient-RMXManager >

Connect to the MCU with RMX Manager

With RMX Manager, you can connect to one or more RealPresence Collaboration Server MCUs installed on the network.The connection process has two steps: you first add the MCU, then you connect to the MCU.

Note the following about connecting RMX Manager to an MCU:

● The first MCU connected to RMX Manager provides the authorization level of users that can connect to the other MCUs on the list.

● Each user can have a different login name and password for each of the listed MCUs.

● You must define all users in the user list of each of the listed MCUs.

Polycom, Inc. 15

Page 37

Getting Started

Add an MCU

To add a RealPresence Collaboration Server MCU to RMX Manager, you need the MCUs IP address and a user name and password for the server--either the admin account or your own credentials.

To add an MCU:

1 In RMX Manager, click Add MCU.

2 Enter a unique name for the MCU and enter the MCU IP.

3 Enter the required port to be used for the connection. Enter 443 to establish a secure connection.

4 Enter a valid User Name, and Password.

5 Click OK.

Connect to an MCU

Use the RMX Web Client when direct access to a single RealPresence Collaboration Server, Appliance Edition is required.

To connect to an MCU:

1 In RMX Manager, select the MCU from the MCUs list or enter its IP address in the Find: field and

click

2 Click Connect MCU .

3 If required, select a certificate for the MCU and click OK.

4 If you are prompted to re-enter credentials, enter the User Name, and Password again.

When the progress indicator shows Complete, the RealPresence Collaboration Server is ready.

Configure the Time Settings

You can configure the RealPresence Collaboration Server (RMX) time manually or set it up to synchronize with an external NTP server. While using NTP Server, ensure to use version 4 which is supported and used by the RealPresence Collaboration Server while using NTP Server. This will ensure continuity, accurate scheduling, and accurate reports for all systems. Following MCU reset, a delay might occur when synchronizing with the external NTP servers.

To set the time settings:

1 In RMX Manager, go to Setup > RMX Time.

2 Configure these settings, as necessary.

Field Description

GMT Date The UK, Greenwich date.

Local Time The MCU local time settings calculated from GMT Time and GMT Offset.

Polycom, Inc. 16

Page 38

Getting Started

Field Description

GMT Time Select the Up/Down arrows to set the GMT Time.

GMT Offset The time zone difference between Greenwich and the MCU physical location, in

hours and minutes.

Retrieve Client Time Automatically updates the GMT Date, GMT Time, and GMT Offset to match that of

the workstation.

Use NTP Server When selected, synchronizes the MCU time with up to three NTP server and

disables the manual GMT Date and GMT Time setting.

Adjust Reservations Time

3 Click OK.

This option adjusts the start time of all reservations.

Requesting and Adding Certificates

The RealPresence Collaboration Server can generate a Certificate Signing Request (CSR) to send to a certificate authority (CA), a trusted entity that validates and officially issues, or signs, PKI certificates. The RealPresence Collaboration Server uses those certificates for client and server authentication.

If your system is in an environment without a PKI, you do not need a CA-signed certificate; the system comes with a self-signed certificate for its TLS connections. When a PKI is deployed, however, self-signed certificates are not trusted and CA-signed certificates are needed.

Create a Certificate Signing Request

The following procedure creates a certificate signing request (CSR) that you can submit to your chosen certificate authority. This method uses the private key generated at software installation time.

To create a certificate signing request:

1 In RMX Manager, go to Setup > RMX Secured Communication > Certification Repository.

2 Go to Personal Certificates and click Add.

3 Select the Network Service for which to request a certificate (commonly Default IP or IP Network

Service) and the Certificate Method of CSR and click Create Certificate Request.

4 Complete the following fields

CSR Information Description

Country Name Two letter code for the country of

State or Province Specifies the state or province where your organization is located.

Locality Specifies the city where your organization is located.

Polycom, Inc. 17

Page 39

Getting Started

CSR Information Description

Organization Specifies your organization's name.

Organizational Unit Specifies the business group defined by your organization.

Note: The system supports only one OU field. If you want the CA-signed certificate to include more than one OU, download and manually edit the CSR.

Common Name (DNS) Specifies the system name. Polycom recommends the following guidelines for

this field:.

• For systems registered in DNS, use the system's fully qualified domain name

(FQDN).

• For systems not registered in DNS, use the system's IP address.

Subject Alternative Name (SAN)

Hash Method Specifies the hash algorithm for the CSR: SHA-256 (recommended) or SHA-1

The SAN field allows you to specify additional host names to be protected by a single SSL Certificate. It allows you to secure host names on different base domains in a single SSL certificate or allows you to virtual host multiple SSL sites on a single IP address.

This field may be required when using EAP-TLS in conjunction with a Network Policy Server (MS-NPS). When it is selected, you can modify the example values provided, to match local certificate requirements and delete those that are not applicable.

• Principle Name—Specifies the user and domain name for logging in to a

Windows domain (e.g., user@example.com). (This is the userPrincipalName attribute of the account object in Active Directory.)

It should be related to the 802.1X identity and password.

• DNS Name—If DNS/MCU Host name is configured, the configured name will

display, otherwise a default example will display:

DNS Name=myhost.example.com

Replace myhost.example.com with either FQDN of the RealPresence Collaboration Server Management Network Interface or the MCU Host name.

• IP addresses

 If RMX is configured with IPv4, then the IPv4 address will display.  If RMX is configured with IPv6, then the IPv6 address will display, besides

you can also enter additional IPv6 addresses.

 If RMX is configured with both IPv4 and IPv6, then both IP addresses will

display.

(not recommended).

5 Click Copy Request.

6 Go to the Certificate Authority (CA) website and request a certificate from them as required and

documented by them.

7 Paste the copied CSR content into the certificate request and complete the request process.

Polycom, Inc. 18

Page 40

Getting Started

Installing the Certificate

You can add, edit, and remove certificates from the system.

To add the certificate to the system:

1 In RMX Manager, go to Setup > RMX Secured Communication > Certification Repository.

2 Go to Personal Certificates, click Add. and then Send Certificate.

3 Copy the certificate text and click Paste Certificate and then Send Certificate.

4 Click Activate Certificate and then OK to disconnect, which is required to activate the certificate.

Obtain the Display Name

Administrators and operators can configure the MCU to display participants’ names (as found in the Addess Book) into an active conference rather than their endpoint system names as found in the endpoint (which is often the endpoint site name).

When enabled, the MCU retrieves the endpoint system data (name, alias, number or IP address) for each dial-in participant and compares it first with the conference dial-in participants list. If the endpoint is not found there, the MCU then compares the data to entries in the Address Book. If a match is found, the system displays the participant’s name as defined in the Address Book.

The system compares the following endpoint data with the Address Book entries:

● For H.323 participants, the system compares the IP address, Alias, or H.323 number.

● For SIP participants, the system compares the IP address or the SIP URI.

This feature is supported for IPv4 participants only.

To enable the Obtain Display Name from Address Book option:

1 In RMX Manager, go to Setup > Customize Display Settings > Ongoing Conferences.

2 Select Obtain display name from address book and click OK.

Integrate with the RealPresence Resource Manager System

If your organization has the Polycom® RealPresence® Clariti solution (that is, a RealPresence Resource Manager system and a RealPresence DMA system along with one or more RealPresence Collaboration Servers), integrate your RealPresence Collaboration Server with the Polycom Manager system and set it us as the device (endpoint and server) application manager. The Resource Manager system can also manage users and conference participants.

RealPresence® Resource

Polycom, Inc. 19

Page 41

Getting Started

To integrate the RealPresence Collaboration Server with the RealPresence Resource Manager system:

1 If not already done, add the MCU(s) to the RealPresence Resource Manager system. See the

RealPresence Resource Manager Operations Guide for more information.

2 If your organization uses the RealPresence Resource Manager system Global Address Book for

conference and endpoint management, add a user account on the RealPresence Resource Manager that the RealPresence Collaboration Server can use as its machine integration account.

See the RealPresence Resource Manager Operations Guide for more information.

3 Write down the user name and password for the machine integration account. You will need this

information for configuring the required system flags. See System Flags for more information.

Overlay a Custom Logo on Conference Displays

You can add a custom logo to the conferencing display for your organization’s video conferences. The custom logo must meet the following specifications:

● File type must be .jpg, .jpeg, or .bmp

● File size must be no more than 1 megabyte.

● Image resolution must be no more than 256 pixels x256 pixels

● Image area (width * height) must not be smaller than 64 pixels x 64 pixels

To add a custom logo as a conference overlay:

1 In RMX Manager, go to RMX Management > Rarely Used > Conference Profiles.

2 In the Conference Profiles pane, double click on the profile to edit

3 Select the Layout Indications tab.

4 Enable the Custom Logo checkbox.

5 Select the appropriate Logo Position. The options are identical to those supported for the Layout

Indication icons.

6 Click OK to save the profile.

7 In RMX Manager, go to Setup > Custom Logo

8 Browse to and select the logo image file to upload.

9 Click OK.

The RealPresence Collaboration Server validates the logo and prompts you to reboot. The server must be rebooted before it starts using the uploaded logo.

Configure Required System Flags

In general, you configure the RealPresence Collaboration Server using the user interface. However, you will likely need to configure the MCU for specific application and operational needs by adding predefined RealPresence Collaboration Server system flags and setting them to the required values.

Polycom, Inc. 20

Page 42

Getting Started

To configure the required system flags:

1 In RMX Manager, go to Setup > System Configuration > System Configuration.

2 In the MCMS_PARAMETERS_USER

3 To enable machine integration with the RealPresence Resource Manager system, add the

EXTERNAL_CONTENT_DIRECTORY, EXTERNAL_CONTENT_IP, EXTERNAL_CONTENT_PASSWORD EXTERNAL_CONTENT_USER

4 To allow endpoints included in a cascaded conference to display content (sometimes called content

snatching), add the

5 For environments that include NAT Firewall deployments, add the

NUM_OF_INITIATE_HELLO_MESSAGE_IN_CALL_ESTABLISHMENT

6 Click OK and when prompted, click Yes.

After the RealPresence Collaboration Server resets, RMX users can access this GAB to add participants to conferences. However, the RealPresence Collaboration Server uses the Global Address Book in read-only mode, which means you must add or modify Address Book entries on the RealPresence Resource Manager system.

system flags.

ENABLE_CONTENT_SNATCH_OVER_CASCADE

tab, click New Flag.

, and

system flag and set its value to YES.

system flag and set its value to 3.

Integrate with the RealPresence DMA System

If your organization has the Polycom® RealPresence® Clariti solution (that is, a RealPresence Resource Manager system and a RealPresence DMA system along with one or more RealPresence Collaboration Servers), integrate your RealPresence Collaboration Server with the Polycom system and set it us as the call control for the conferencing network. Configure the RealPresence DMA system as the H.323 gatekeeper and/or SIP server, endpoint registrar and virtual meeting room manager.

RealPresence® DMA

To integrate the RealPresence Collaboration Server with the RealPresence DMA system:

1 If not already done, add the RealPresence Collaboration Servers and the RealPresence DMA

system as device instances to the RealPresence Resource Manager system. See the RealPresence Resource Manager Operations Guide for more information.

2 In RMX Manager, go to RMX Management > Rarely Used > IP Network Services.

3 From IP Network Services, double-click Default IP Service and select the required IP Network

Type: H.323 or H.323 & SIP.

4 Go to Gatekeeper tab and from the Gatekeeper drop-down list, select Specify.

5 Enter either the RealPresence DMA system’s IP Address or Name (as registered in the DNS).

6 As required, enter the IP Address or Name for an alternate backup gatekeeper.

7 Enter the MCU Prefix in Gatekeeper number, which is the number this network service uses to

register with the RealPresence DMA system gatekeeper. This number is used by H.323 endpoints as the first part of their dial-in string when dialing the MCU.

8 Complete the other fields as required and then click OK.

Polycom, Inc. 21

Page 43

Getting Started

Integrate with HARMAN Media Suite

RealPresence Collaboration Server can dial out to a HARMAN Media Suite (previously Polycom RealPresence Media Suite) for conference recording if you first establish a dial-out Recording Link, which is a dial-out connection from the MCU to the HARMAN Media Suite.

To integrate the RealPresence Collaboration Server with the HARMAN Media Suite:

1 In RMX Manager, go to RMX Management > Rarely Used > Recording Links ().

2 In the Recording Links list, click New Recording Link ( ).

3 Define the following recording link parameters:

Recording Link Parameters

Parameter Description

Name A unique descriptive name to identify to the virtual recording room (VRR) on the

HARMAN Media Suite.

Type Select the network environment: H.323 or SIP

IP Address • If no H.323 gatekeeper is configured, enter the IP Address of the HARMAN Media

Suite.

• If an H.323 gatekeeper is configured, enter its IP address or alias.

• If a SIP server is configured, enter its IP address.

Polycom, Inc. 22

Page 44

Getting Started

Recording Link Parameters

Parameter Description

Alias Name If using the endpoint alias instead of the IP address, first select the alias type and then

enter the endpoint alias. The name should be the same as HARMAN Media Suite registration information.

If the recording link defines the VRR, enter the RealPresence Media Suite E.164 +VRR in the Alias Name.

If the recording link does not define the VRR, enter the HARMAN Media Suite E.164 that registers to RealPresence DMA system as the Alias Name. The default VRR is used for recording.

If you are associating this recording link to a VRR on the HARMAN Media Suite, define the alias as follows:

• If using the HARMAN Media Suite IP address, enter the VRR number as the Alias

Name. For example, if the VRR number is 5555, enter 5555.

• If the Alias Type is set to H.323 ID, enter the HARMAN Media Suite IP address and

the VRR number in the format:

For example: If the Media Suite IP is 173.26.120.2 and the VRR number is 5555, enter 173.26.120.2##5555

• If the Alias Type is set to E.164, enter the HARMAN Media Suite E.164 followed by

VRR number:<Media Suite E.164><VRR number> For example: If the HARMAN Media Suite E.164 is 123456 and the VRR number is

5555, enter 1234565555.

Alias Type Depending on the format used to enter the information in the IP address and Alias

fields, select H.323 ID or E.164 (for multiple Recording links).

E-mail ID and Participant Number are also available.

4 Click OK.

Customizing the RMX Manager User Interface

You can customize the RMX Manager user interface according to your preferences. Each user’s customizations are automatically saved for them.

Switch the RMX Management Section View

You can view the RMX Management section either as a list or as a toolbar.

To switch between RMX Management Toolbar and List Views:

» In RMX Manager, go to the RMX Management section and toggle the upward or downward arrow to

change from list view to toolbar view respectively.

Polycom, Inc. 23

Page 45

Getting Started

Move Items in the RMX Management Section

You can move items between the Frequently Used and Rarely Used sections, depending on the operations you most commonly perform and the way you prefer to work with RMX Manager.

To move items in the RMX Management list:

1 In RMX Manager, go to the RMX Management section.

2 Drag and drop the icon of the item you wish to move to the desired position.

An indicator line ( ) appears indicating the new position of the icon.

Restore Default RMX Manager User Interface

You can restore the RMX Manager user interface to its factory default configuration when needed.

To restore the RMX Manager user interface to its default configuration:

» In RMX Manager, go to View > Restore RMX Display Defaults.

Polycom, Inc. 24

Page 46

Conference Profiles and Templates

Use conference profiles and conference templates to enable a standalone RealPresence Collaboration

Server to implement standard and manageable conferencing experiences for your conferencing community.

IMPORTANT:

If you have a Polycom manage conferencing parameters on the RealPresence DMA system and not on the RealPresence Collaboration Server.

The RealPresence DMA system has more flexibility, as it can associate conferencing experiences with users, conference rooms, or enterprise groups. It also offers more features and functions.

Conference Profiles

In a standalone RealPresence Collaboration Server environment, you can enable the following conferencing capabilities and features using conference profiles:

● Conferencing mode--Continuous Presence (CP) and Advanced Video Coding (AVC), Video Switching, Scalable Video Codec (SVC), or mixed CP and SVC

● Video line rate

● Conference skin and screen layout

● Entry queue (EQ) and interactive voice response (IVR) experiences

● Content sharing features

● Recording features

● Endpoint protocol(s) supported

● Conference messaging

● Polycom Lost Packet Recovery (LPR) and Dynamic Bandwidth Allocation (DBA)

● Encryption

The following topics describe RealPresence Collaboration Server conference profiles.

RealPresence® DMA® system, create conference templates and

View the List of Conference Profiles

A RealPresence Collaboration Server has three default conference profiles based on conferencing mode. They are:

● Factory_Video_Profile

● Factory_SVC_Video_Profile

● Factory_Mix_Video_Profile

Polycom, Inc. 25

Page 47

Conference Profiles and Templates

To view the current list of conference profiles:

» In RMX Manager, go to RMX Management > Rarely Used > Conference Profiles.

Add a New Conference Profile

Conference profiles specify the parameters best suited for your conferencing software and hardware environments. Use the default profiles or add new profiles specific to your conferencing environment.

To add a new conference profile:

1 In RMX Manager, go to RMX Management > Rarely Used > Conference Profiles.

2 In the Conference Profiles pane, click New Profile ( ).

3 In the Display Name field, enter a unique and identifiable name for the profile and select the

required Conferencing Mode.

The New Profile tabs and options change based on the selected conferencing mode and the MCU model (appliance edition or virtual edition). Only supported options are available on each tab.

 When CP (Continuous Presence) is selected, all tabs are available.

 When SVC Only is selected, the General, Advanced, Video Quality, Video Settings, Audio

Settings, IVR, and Network Settings tabs are available.

 When CP and SVC is available, all tabs except the Gathering Settings tab, are available.

4 Select and edit the parameters you wish to define.

 General Parameters

 Advanced Parameters

 Gathering Settings - Not available when CP and SVC or SVC Only conferencing modes are

selected

 Video Quality Parameters

 Video Settings Parameters

 Audio Settings Parameters

 IVR Parameters

 Recording Parameters - Not available when SVC Only conferencing mode is selected

 Site Names Parameters - Not available when SVC Only conferencing mode is selected

 Message Overlay Parameters - Not available when SVC Only conferencing mode is selected



Network Services Parameters

 Layout Indications Parameters - Not available when SVC Only conferencing mode is selected

For detailed information about the conferencing parameters, see Conference Profile Parameters .

5 Click OK to save the new profile.

Polycom, Inc. 26

Page 48

Conference Profiles and Templates

Conference Profile Parameters

The following tables list the conference parameters that you can enable on the RealPresence Collaboration Server.

General Parameters

Field/Option Description

Display Name Provide a meaningful name for the profile.

Line Rate Specifies the maximum bit rate at which endpoints can connect to conferences. The line rate is

the combined video, audio and content rate. Note: Downspeeding is not supported. As a result, ISDN-video calls will consume bandwidth

resources according to the line rate specified in the conference profile. For example, if the conference line rate is 512kbps, ISDN-video calls connecting at lower line rates (256kbps) still consume the bandwidth resources of 512kbps calls. As a result, if bandwidth resources are fully consumed, ISDN-video calls may be rejected before media card resources are exhausted.

Conferencing Mode

Routing Name Assign a routing name or allow the system to assign one automatically.

Video Switching Available only for Appliance Editions.

Choose one of the following:

• Continuous Presence (CP) — (also known as AVC) This mode supports the H.264

Advanced Video Coding (AVC) compression standard. In CP mode, the MCU selects the best video protocol, resolution, and frame rate for each endpoint according to its capabilities.

• SVC Only — This mode supports an extension of the H.264 standard, known as H.264

Scalable Video Coding (SVC). The number of enhancement layer streams sent to a device can be tailored to fit the bandwidth available and device capabilities.

SVC conferencing is only possible with endpoints that support H.264 SVC. Enabling this setting disables many of the other template settings.

• CP and SVC — (also known as or mixed mode) This mode enables both AVC-only endpoints

and endpoints supporting SVC to join a conference.

• If all ASCII text is entered in the Display Name, it is used also as the Routing Name.

• If any combination of Unicode and ASCII text (or full Unicode text) is entered in the Display Name, the ID (such as Conference ID) is used as the Routing Name.

An alternative to Continuous Presence (CP) mode, this option provides HD video while using MCU resources more efficiently. All participants see the current speaker full screen while the current speaker sees the previous speaker.

When enabled:

• The minimum available line rate is 768 kbps

• All endpoints must connect at the same line rate. Those that don’t support the specified line

rate are connected in voice-only mode.

• You can also enable H.264 high profile, which allows the confer bandwidth-conserving H.264 High Profile codec.

ence to use Polycom’s

Operator Conference

Polycom, Inc. 27

Not available when Video Switching is enabled. Enable this option to define the profile of an operator conference.

Page 49

Conference Profiles and Templates

Advanced Parameters

Field/Option Description

Encryption Specifies the media encryption setting:

• No encryption — All endpoints join unencrypted

• Encrypt when possible — Endpoints supporting encryption join encrypted; others join

unencrypted.

• Encrypt all — Endpoints supporting encryption join encrypted; others cannot join.

Packet loss compensation

(LPR and DBA)

Auto Terminate Not available when Operator Conference is enabled. Not recommended for SVC Only

Auto Redialing Enables the MCU to automatically redial H.323 and SIP participants that have been

Exclusive Content Mode

Enable FECC When enabled, participants can control the zoom and PAN of other endpoints in the

FW NAT Keep Alive

Enables Lost Packet Recovery (LPR) and Dynamic Bandwidth Allocation (DBA).

• LPR creates additional packets containing recovery information that can be used to

reconstruct packets lost during transmission. In CP Conferences, LPR is enabled by default while in VSW Conferences, LPR is disabled

by default. LPR can be enabled for VSW conferences but H.320 and SIP participants will not be able to connect.

• DBA allocates the bandwidth needed to transmit the additional packets.

conferences. When enabled, the MCU automatically ends the conference when the specified termination

conditions are met. Terminate conditions include:

• Minutes Before First Joins

• Minutes At the End

 After last participant quits  When last participant remains

abnormally disconnected from a conference.

When enabled, if a participant is broadcasting content, other participants are prevented from interrupting with their own content while the current content stream is active.

conference via the FECC channel.

Specifies that when receiving calls through a firewall or session border controller (SBC), the MCU should send media stream keep-alive messages to the RTP, UDP and BFCP channels at the interval specified.

The acceptable interval is within the range of 1 - 86400 seconds.

Polycom, Inc. 28

Page 50

Conference Profiles and Templates

Advanced Parameters

Field/Option Description

TIP Compatibility Available only when CP (Continuous Presence) conferencing mode is selected.

Enables compatibility with Cisco Telepresence Systems (CTS) and Telepresence Interoperability Protocol (TIP), either for video only or for both video and content.

If Prefer TIP is enabled, TIP content is used for endpoints that support TIP, and non-TIP content is used with non-TIP endpoints.

Requires a minimum line rate of 1024 kbps and HD resolution (720 or better). Note: If an option other than None is enabled, the Gathering Settings options are disabled.

MS AV MCU Cascade Mode

Gathering Settings - Not available when CP and SVC or SVC Only conferencing modes are selected

Field Description

Enable Gathering Available only when CP (Continuous Presence) conferencing mode is selected.

Displayed Language

Dial-in Number 1 Applies to Appliance Editions only.

Dial-in Number 2

When integrated with a Microsoft Skype for Business environment, controls behavior of the cascade link with the Skype for Business AVMCU.

• Resource Optimized — The cascade link between the <Product Name>RealPresence

Collaboration Server system and the Skype for Business server’s AVMCU is limited to SD video resolutions to conserve MCU resources.

• Video Optimized — The cascade link between the <Product Name>RealPresence

Collaboration Server system and the Skype for Business server’s AVMCU is capable of HD video resolutions, increasing MCU resource usage.

When enabled, the MCU implements a Gathering Phase, which is the time period at the beginning of a conference when participants are connecting to the conference.

During the Gathering Phase, a mix of live video from connected endpoints is combined with both static and variable textual information (specified here) about the conference into a slide which is displayed on all connected endpoints.

Language in which the Gathering Phase page is displayed.

Optional access numbers to display on the gathering phase slide.

Info 1 Optional free-form text fields to display on the gathering phase slide.

Info 2

Info 3

Polycom, Inc. 29

On a 16:9 endpoint, a maximum of 96 characters can be displayed for each field, and fewer on a 4:3 endpoint.

Page 51

Conference Profiles and Templates

Video Quality Parameters

Field Description

People Video Definition

Video Quality Available only when CP (Continuous Presence) conferencing mode is selected.

Specifies two video optimizations:

•Motion — higher frame rate without increased resolution

• Sharpness — higher video resolution that requires more system resources Note: When Sharpness is selected, the MCU will send 4CIF (H.263) at 15fps instead of CIF

(H.264) at 30fps.

Maximum Resolution

Video Clarity™ Applies to Appliance Editions only. Available only when CP (Continuous Presence)

Auto Brightness

Content Video Definition

Content Settings

Available only when CP (Continuous Presence) conferencing mode is selected.. Overrides the Maximum Resolution setting of the Resolution Configuration dialog box. Select

one of the following options:

•Auto - The Maximum Resolution remains as selected in the Resolution Configuration

dialog box.

•CIF

•SD

• HD720

• HD1080

conferencing mode is selected. Not available when Video Switching is enabled. When enabled, a video enhancement algorithm is applied that sends clearer images with sharper

edges and higher contrast back to all endpoints at the highest possible resolution supported by each endpoint.

All layouts, including 1x1, are supported.

Applies to Appliance Editions only. When enabled, color changes may be observed in computer-based VGA content sent by HDX

endpoints through the People video channel.

Specifies the transmission mode for the content channel based on the type of content most often shared.

•Graphics — Basic mode, intended for normal graphics

• Hi-res Graphics — A higher bit rate intended for high resolution graphic display

•Live Video — Content channel displays live video

• Customized Content Rate - Manual definition of the Conference Content Rate, mainly for

cascading conferences. If you choose a custom content rate, specify the line rate reserved for the content.

AS SIP Content

Polycom, Inc. 30

Available only when CP (Continuous Presence) conferencing mode is selected. Enables content sharing using AS-SIP security and the Multiple Content Resolutions option,

which is not supported in any other content sharing mode.

Page 52

Conference Profiles and Templates

Video Quality Parameters

Field Description

Multiple Content Resolutions

Send Content to Legacy Endpoints

H.264 High Profile

Available only when CP (Continuous Presence) conferencing mode is selected. Enables content sharing in multiple streams, one for each video protocol: H.263 and H.264. This

allows endpoints with different protocols to connect and disconnect without having to restart content sharing.

When enabled, choose which content protocols and resolutions to use for each stream of content.

• Content Protocol

 Transcode to H.264 is always selected  Use H.263  Use H.264 if available, otherwise use H.263  Use H.264 cascade and SVC optimized  Use H.264 HD

• Content Resolution—Specify the fixed resolution and frame rate of the content channel for content sharing in cascaded conferences. Available only when Content Protocol is set to H.264 cascade and SVC optimized. The content resolutions available for selection depend on the content sharing mode (highest common or multiple content resolutions), line rate and content settings selected for the conference.

Available only when CP (Continuous Presence) conferencing mode is selected. When enabled, content can be sent over the video (people) channel to H.323/SIP/ISDN-video

endpoints that do not support H.239 content. Select this option when Avaya IP Softphone will be connecting to the conference.

Applies to Appliance Editions only. Displayed only when conferencing mode is VSW (Video Switching), or the selected Content Protocol is H.264 Cascade Optimized.

In scenarios where endpoints not supporting high profile (such as HDX) are connected to the conference, it is recommended to clear this check-box to enable them to share content.

Enable MS RDP Content

When enabled, the MCU starts conferences on Modular MCUs (MMCU) that have sufficient soft blade resources. MMCUs may be configured with an RDP translator that converts H.264 content shared from a standard endpoint to RDP content to deliver to a Skype ASMCU. Likewise, when a Skype client shares RDP content, the RDP translator delivers H.264 content to the MMCU.

Notes:

• For Polycom RealConnect calls to work, set ‘AllowMultiView’ to TRUE on the Skype for

Business Front End Server. This will enable the participants to

connect and receive multiple

video streams.

• This option can be used in place of a separate Polycom

ContentConnect™ gateway solution.

Polycom, Inc. 31

Page 53

Conference Profiles and Templates

Video Settings Parameters

Field/Option Description

Presentation Mode

Same Layout Available only when CP and SVC conferencing mode is selected. Not available if Presentation

Lecturer View Switching

Telepresence Mode

Telepresence Layout Mode

Available only when CP (Continuous Presence) conferencing mode is selected. When enabled, the conference changes to lecture mode when the current speaker speaks for 30

seconds. When another participant starts talking, it returns to the previous video layout.

Mode or Video Switching is selected, or if Telepresence Mode is Yes . Forces the selected layout to all participants. Personal selection of the video layout is disabled.

Available only when CP (Continuous Presence) conferencing mode is selected. Not available if Same layout is selected or Telepresence Mode is Yes.

When in lecture mode, enables the lecturer’s view to automatically switch among participants (if the number exceeds the number of windows in the layout) while the lecturer is talking.

Available only when CP (Continuous Presence) conferencing mode is selected. Supports telepresence conference rooms joining the conference:

•Auto – A conference is automatically put into telepresence mode when a telepresence

endpoint (RPX, TPX, ATX, or OTX) joins. Recommended setting.

•On – Telepresence mode is on, regardless of whether a telepresence endpoint is present.

•Off – Telepresence mode is off, regardless of whether a telepresence endpoint is present.

Available only when CP (Continuous Presence) conferencing mode is selected. Not available if Telepresence Mode is No.

Specifies the layout for telepresence conferences:

•Manual – Layout is controlled manually by a conference operator using the Multipoint Layout

Application (MLA) interface.

• Continuous Presence (MLA) – Tells the MLA to generate a multipoint view (standard or

custom).

•Room Switch – Tells the MLA to use Voice Activated Room Switching (VARS). The speaker’s

site is the only one seen by others.

• Speaker Priority – Ensures that the current speaker is always displayed in the video layout.

The previous speakers are also displayed if there is room in the layout. In this mode, each endpoint in the conference reserves screens for displaying the active speaker in the largest video layout cell available.

Auto Scan Interval(s)

Auto Layout Available only when CP (Continuous Presence) conferencing mode is selected.

Polycom, Inc. 32

Available only when CP (Continuous Presence) conferencing mode is selected. Specifies the time interval (between 5 - 300 seconds) that Auto Scan uses to cycle the display of

participants that are not in the conference layout in the selected cell. Auto Scan is often used in conjunction with Customized Polling which allows the cyclic display

to be set to a predefined order for a predefined time period.

When selected, the system automatically selects the conference layout based on the number of participants currently connected to the conference. When a new video participant connects or disconnects, the conference layout automatically changes to reflect the new number of video participants.

Page 54

Conference Profiles and Templates

Audio Settings Parameters

Field/Option Description

Audio Clarity Available only for Appliance Editions.

When enabled, improves the voice quality in conference of a PSTN endpoint.

Mute participant except lecturer

Speaker Change

When enabled, the MCU automatically mutes all participants except the lecturer upon connection to the conference.

Specifies the amount of time a participant must speak continuously before becoming the speaker.

Threshold

Auto mute noisy endpoints

Also known as NoiseBlock™. When enabled, the MCU automatically detects and mutes AVC endpoints that have a noisy audio channel.

IVR Parameters

Field/Option Description

Conference IVR Service

Conference Requires Chairperson

Lists the conference IVR services available on the MCU. The default Conference IVR Service is selected.

When enabled, conferences will not start until the chairperson joins. Callers who arrive early are placed on hold. If Terminate conference after chairperson leaves is also enabled, the conference will end when the last chairperson leaves.

This option is ignored if a participant doesn’t enter a chairperson passcode. For enterprise users, chairperson passcodes/passwords can come from the Active Directory, but

you can override the Active Directory value. For local users, you can add or change chairperson passcodes/passwords when you create or

edit the users. Note: When enabled for a Polycom RealConnect

presenter acts as the chairperson for the conference.

conference, the Skype for Business

Recording Parameters - Not available when SVC Only conferencing mode is selected

Parameter Description

Enable

Enables recording of conferences.

Recording

Dial Out Recording Link

Conference recording requires a recording system such as a Polycom RealPresence Media Suite or Polycom Capture Server. Select the recording link for the device to be used for conference recording.

Start Recording Select when to start the recording:

• Immediately – Conference recording is automatically started upon connection of the first

participant.

• Upon Request – The operator or chairperson must initiate the recording (manual).

Audio Only When enabled, limits recording to the audio channel of the conference.

Polycom, Inc. 33

Page 55

Conference Profiles and Templates

Recording Parameters - Not available when SVC Only conferencing mode is selected

Parameter Description

Display Recording Icon

Play recording message

Site Names Parameters - Not available when SVC Only conferencing mode is selected

Field Description

Display Mode Specifies if, when, and how the endpoint display name is shown on each video participant’s

Message Overlay Parameters - Not available when SVC Only conferencing mode is selected

When enabled, the MCU displays a recording indicator (a red dot) to all participants to inform them that the conference is being recorded.

Skype for Business users connected to the conference via Polycom RealConnect technology get notified when a Skype for Business user starts recording the meeting by displaying a recording icon within the video layout.

When enabled, the MCU plays a recording message into the conference when recording starts and ends.

display.

•Auto - Whenever the video layout changes, display the name for 10 seconds in the font size,

background color, and screen position specified.

•On - For the duration of the conference, display the name in the font size, background color,

and screen position specified.

•Off - Do not display the site names and all other fields in this tab are grayed and disabled

Field Description

Enable When enabled, specifies a message to display on selected conference participant’s video

display.

Content Enter the message text (up to 50 characters) to display and specify the font size, color, position,

and transparency for the text display. You can also specify the speed at which the text should move (static, slow, or fast) and how often it should repeat.

Network Services Parameters

Parameter Description

SIP Registration

Accept Calls When enabled, allows dial in participants to connect to a conference via a network service.

Polycom, Inc. 34

When enabled, registers the conference with the SIP server of the selected network service.

Page 56

Conference Profiles and Templates

Layout Indications Parameters - Not available when SVC Only conferencing mode is selected

Field Description

Position Use the drop-down menu to set the display position of the indication icons group.

Recording Available when Enable Recording is enabled on the Recording tab.

When enabled, the MCU displays a recording indicator (a red dot) to all participants to inform them that the conference is being recorded.

Audio Participants

Video Participants

Network Quality

Custom Logo When enabled and a

When enabled, displays the count of audio participants on each video participant’s display. The count can be displayed on the constantly or when participants join and leave the conference.

When enabled, displays the count of video participants on each video participant’s display.

When enabled, the network quality reading is displayed on each video participant’s display.

Conference Templates

Administrators and operators can create, save, schedule, and activate identical conferences using conference templates.

A conference template does the following:

● Saves the conference profile

● Saves all participant parameters including the Personal Layout and Video Forcing settings

● Simplifies telepresence conference setup where precise participant layout and video forcing settings

are crucial

The MCU initially displays the conference templates list as a closed tab in the RMX Manager main screen. The tab indicates the number of saved conference templates.

View the List of Conference T emplates

A RealPresence Collaboration Server does not have default conference templates because they require information that is not standard.

On first access, the list of conference templates appears in the main RMX Manager pane. If the list is hidden, double-click the Conference Template tab on the right.

Polycom, Inc. 35

Page 57

Conference Profiles and Templates

Add a New Conference Template

Create conference templates to start and replicate successful conferences. Conference templates:

● Identify the desired conference profile (and thus, parameters) for a conference

● Identify that participants and participant parameters (including their personal layout and video forcing

settings) for a conference

● Simplify the setup of telepresence conferences, where precise participant layout and video forcing

settings are crucial.

To add a new conference template:

1 In RMX Manager, click Conference Templates.

2 Click New Conference Template ( ).

3 In the General tab:

a In the Display Name field, enter the new template name.

b Specify the duration of the conference in hours and minutes and enable Permanent Conference

to create a standard recurring conference.

c Assign a Routing Name and ID or allow the system to assign them automatically.

d Select the required Profile.

e As required, assign a Conference Password that users must enter to join the conference or a

Chairperson Password that the chairperson must enter to take on the chairperson

responsibilities.

4 Go to the Participants section and:

a Click Add from Address Book, select the required groups and participants, and click Add

b Click New and enter the required information for the new participant, and click Add.

5 To assign a lecturer for Lecture Mode conferences, select a Lecturer from the participant’s list, and

if required enable Dial Out Manually so the MCU can initiate the dial out.

Dial-out and dial-in participants are two separate participants even if they have the same IP address/number; therefore, if a dial-out participant is added to the conference, but that participant dials in before the MCU dials out to him, the MCU creates a second participant in the Participants list and still attempts to dial out to the participant. If the dial-out participant was designated as the conference lecturer, the MCU cannot replace that participant with the dial-in participant that is connected to the conference.

Polycom, Inc. 36

Page 58

Conference Profiles and Templates

6 To override the layout identified in the selected conference profile, click Media Sources and enable

Override layout from profile.

For information on how to change the conference layout, see <reference here>.

7 To add optional conference information, click Information and enter the required text into the Info1,

Info2, Info3, or Billing Info text boxes.

8 Click OK to create the new conference template.

Additional Conference Profile and Conference Template Tasks

You can edit, delete, export, and import conference profiles and conference templates as described in the following sections.

Edit a Conference Profile

You can edit an existing conference profile but you cannot rename it.

To edit a conference profile:

1 In RMX Manager, go to RMX Management > Rarely Used > Conference Profiles.

2 In the Conference Profiles list, double-click the profile to edit.

3 Edit the required profile parameter(s) and click OK.

For detailed information about the conferencing parameters, see Conference Profile Parameters .

Delete a Conference Profile

You can delete profiles from the MCU; however, a conference profile cannot be deleted if it is currently used by meeting rooms, reservations, entry queues, or SIP factories. A profile that is assigned to only one ongoing conference and no other conferencing entity can be deleted.

To delete a conference profile:

1 In RMX Manager, go to RMX Management > Rarely Used > Conference Profiles.

2 In the Conference Profiles list, select the conference profile to delete.

3 Click Delete Profile

( ) and click OK.

Export a Conference Profile

If your environment includes multiple MCUs, you will likely want all of the same conference profiles available on all MCUs, so conferences can successfully cascade over multiple MCUs. The RealPresence Collaboration Server allows you to export conference profiles from one MCU as a single XML file and import them to other MCUs.

Polycom, Inc. 37

Page 59

Conference Profiles and Templates

Only RealPresence Collaboration Server administrators can export and import conference profiles. Operators can only export conference profiles.

To export a conference profile:

1 In RMX Manager, go to RMX Management > Rarely Used > Conference Profiles.

2 In the Conference Profiles section:

 To export all conference profiles, click Export Conference Profiles .

 To export just selected conference profiles:

i In the Conference Profiles list, select the required conference profiles.

ii Right-click and select Export Selected Conference Profiles.

3Browse to the location to which to save the exported file.

4 In the Profiles file name field, enter the file name prefix and click OK.

The file is saved to the location specified with the name specified. The file will have the _confProfiles.xml suffix predefined and required by the MCU.

Import a Conference Profile

If your environment includes two or more MCUs, you will likely want all of the same profiles available on all MCUs, so conferences can successfully cascade over multiple MCUs.

To import a conference profile:

1 In RMX Manager, go to RMX Management > Rarely Used > Conference Profiles.

2 In the Conference Profiles section, click Import Conference Profiles .

3Browse to the location of previously exported _confProfiles.xml file.

4 Select the file, and click OK.

Note that a conference profile will not be imported when:

 A conference profile with that name already exists

 The conference profile requires an IVR service that is not present on the MCU .

Edit a Conference Template

You cannot edit a conference template.

Delete a Conference T emplate

You can delete one or several conference templates at a time.

Polycom, Inc. 38

Page 60

Conference Profiles and Templates

To delete a conference template:

1 In RMX Manager, click Conference Templates.

2 In the Conference Templates list, select the template(s) to delete.

3 Right-click and select Delete Conference Template.

4 Click OK.

Export a Conference Template

You can export conference templates from one MCU as a single XML file and import them to other MCUs in your environment. When you export conference templates, you should also export the profiles associated with the templates to ensure that identical settings are used for conferences running on different MCUs. This is especially important in environments using cascading conferences that are running on different MCUs.

Only RealPresence Collaboration Server administrators can export and import conference templates. Operators are only allowed to export conference profiles.

To export a conference template:

1 In RMX Manager, click Conference Templates.

2 In the Conference Templates pane:

 To export all conference profiles, click Export Conference Templates .

 To export just selected conference templates,

i In the Conference Templates list, select the required conference template(s).

ii Right-click and select Export Selected Conference Templates.

3Browse to the location to which to save the exported file(s).

4 In the Templates file name field, enter the file name prefix for the exported templates.

5 To export the conference profile as part of this export, enable Export includes Conference Profiles

and in the Profiles file name field, type the file name prefix for the exported profiles.

6 Click OK.

The conference templates are saved to the specified location with the specified name and a _confTemplates.xml suffix predefined as required by the MCU.

The conference profiles are saved to the specified location with the specified name and a _confProfiles.xml suffix predefined as required by the MCU.

Import a Conference T emplate

You can import conference templates (and associated conference profiles) from one to multiple MCUs in your environment.

To import a conference template:

1 In RMX Manager, click Conference Templates.

Polycom, Inc. 39

Page 61

Conference Profiles and Templates

2 In the Conference Templates pane, select Import Conference Templates.

3 If required, enable Import includes conference profiles to include the conference profile as part of

the import.

4Browse to the location of the previously exported

file(s)

5 Select the file(s) to import and click OK.

The imported conference template(s) and profile are added to their respective lists.

_confTemplate.xml

and

_confProfiles.xml

Save an Ongoing Conference as a Template

You can save any ongoing conference as a template; however, consider these notes:

● If the profile assigned to a conference is deleted while the conference is ongoing the conference

cannot be saved as a template.

● Only defined participants can be saved to the conference template. Before saving a conference to a

template ensure that all undefined participants have disconnected.Undefined participants are not saved in conference templates.

● Conference templates saved from an ongoing conference do not include Message Overlay text

messages.

To save an ongoing conference as a template:

1 In the RMX Manager Conferences List, select the conference to be saved as a template.

2 Right-click and select Save Conference to Template.

The MCU saves the template with a name derived from the ongoing conference display name. Operator conference templates are displayed with the operator conference icon.

Polycom, Inc. 40

Page 62

Advanced Conferencing Profile Features

This section describes specific conferencing features you may wish to enable or disable. You usually enable or disable features via the conferencing profile. Occasionally, you may need to enable or disable features using system flags.

IMPORTANT:

If you have a Polycom manage conferencing parameters on the RealPresence DMA system and not on the MCU.

The RealPresence DMA system has more flexibility, as it can associate conferencing experiences with users, conference rooms, or enterprise groups. It also offers more features and functions including MCU cascading and integration with Polycom RealConnect.

Enable Recording in the Conference Profile

Enable conference recording on the RealPresence Collaboration Server as part of the conference profile by first configuring the dial-out recording link. The recording link defines the connection between the MCU and the recording system. Then you must modify the configuration profile recording settings

The default Conference IVR Service associated with the RealPresence Collaboration Server includes the recording-related voice messages and default DTMF codes that allow the conference chairperson to control the recording process from the endpoint. However, you can associate change these default settings if desired.

RealPresence® DMA® system, create conference templates and

To enable recording via the Conference Profile:

1 In RMX Manager, go to RMX Management > Recording Links ().

2 In the Recording Links list, click New Recording Link ( ).

3 Enter a unique and recognizable Name for the recording system and link and select the network

environment: H.323 or SIP.

4 Enter the IP Address and/or the Alias Name of the recording system.

 If no gatekeeper is configured, you must enter the recording system’s IP Address. If you are using

the HARMAN Media Suite, enter its IP address and then enter the virtual recording room (VRR) number in the Alias Name field.

 If a gatekeeper is configured, you can enter the recording system’s IP Address or its alias.

 If a SIP server is configured, enter its IP address instead of the IP address of recording system.

5 If using Alias Name, select the Alias Type for the recording system.

Polycom, Inc. 41

Page 63

Advanced Conferencing Profile Features

 If you are associating this recording link to a VRR on the HARMAN Media Suite, if the Alias Type

is set to H.323 ID, enter the Media Suite IP address and the VRR number in the format:

For example: If the Media Suite IP is 173.26.120.2 and the VRR number is 5555, enter

173.26.120.2##5555Define the following recording link parameters on the default IP network service to enable recording.

 Depending on the format used to enter the information in the IP address and Alias fields, select

H.323 ID or E.164 (for multiple Recording links). E-mail ID and Participant Number are also available.

6 Click OK.

The recording link is added to the RealPresence Collaboration Server unit.

7 In RMX Manager, go to RMX Management > Conference Profiles ( ).

8 From the Conference Profile list, select the profile to enable for recording.

9 Right click and select Profile Properties

10 In the New Profile Properties section, go to Recording and click Enable Recording.

11 Enter the required recording parameters. For more information about these parameters, see

Recording Parameters - Not available when SVC Only conferencing mode is selected .

12 Click OK.

Change Position of the Conference Indicators

During a conference, when enabled, participants see a variety of indicators that provide information about the conference. If required, you can change the position of these indicators in the conference layout.

Conference indicators include:

● Audio and video participant indicators

During an ongoing conference, participants see the number of audio-only and video participants who are connected to the conference. The system displays a maximum of 99 participants of each type. The icon group is displayed for AVC endpoints only.

● Recording indicator

When Display Recording Icon is selected in either the Recording or Layout Indications tab of the Conference Properties dialog, the recording status is indicated by the standard recording icon.

● Network quality indicator

Network quality is determined by the percentage of packet loss according to the following default threshold values:

 Packet loss less than 1% is considered Normal

 Packet loss in the range of 1% - 5% is considered Major

 Packet loss above 5% is considered Critical.

Conference indicators, shown below, are displayed on AVC endpoints only for CP or mixed conferences.

Polycom, Inc. 42

Page 64

Advanced Conferencing Profile Features

To change the position of the conference indicators:

1 In RMX Manager, go to RMX Management > Rarely Used > Conference Profiles.

2 In the Conference Profiles pane, double click on the profile to edit

3 Select the Layout Indications tab.

4 From the Position drop-down menu, select a new position for the indicators. Options are Left Top,

Top, Right Top, Left Bottom, Bottom, or Right Bottom.

5 Click OK.

Indicators for Microsoft Skype for Business Users

Microsoft Skype for Business and Lync users see the same conference indicators other Polycom RealConnect conference participants do provided the video stream sent to the their endpoint is compatible. However, the indications are not embedded in the video sent to the link, so as to preserve the Skype for Business or Lync user experience.

Enable Multiple Content Resolutions (Transcoding) on TIP Endpoints

The RealPresence Collaboration Server supports content transcoding for TIP endpoints in Prefer TIP virtual meeting room (VMR) conferences.

TIP endpoints in Prefer TIP VMR conferences support the following content resolutions and frame rates:

● XGA 5fps @512K (default)

● 720p5 @768K

● 1080p5 @1Mbps

● 720p30 @2.25Mbps

● 1080p30@4Mbps (Not supported on RealPresence Collaboration Server, Virtual Edition)

Polycom, Inc. 43

Page 65

Advanced Conferencing Profile Features

TIP endpoints work at one of the above resolutions only. Any TIP endpoint not supporting the selected rate and resolution is unable to receive the content. TIP endpoints supporting Version 7 don’t receive any content in content transcoding mode if the selected resolution is other than XGA 5fps @512K.

To set the multiple content resolution for TIP endpoints, you must set the TIP Compatibility option to Prefer

TIP in the Conference Profile under Profile Properties > Advanced tab.

To enable multiple resolutions (set content transcoding) on Cisco TIP endpoints:

1 In RMX Manager, go to RMX Management > Rarely Used > Conference Profiles.

2 In the Conference Profiles pane, double click on the profile to edit

3 Go to Video Quality and in the Content Video Definition section

4 Now enable Multiple Content Resolutions.

5 Select the appropriate content resolution and frame rate from the drop-down menu for the TIP

Encoder.

6 Click OK.

Binary Floor Control Protocol (BFCP) Support for TIP endpoints

Support for Cisco Telepresence Interoperability Protocol (TIP) version 8, now allows TIP endpoints to receive high-resolution content using Binary Floor Control Protocol (BFCP).

BFCP provides better coordinated access to conferencing resources.

For more information, see Content Sharing Using BFCP Protocol for TIP Participants in RealPresence® Collaboration Server Technical Reference Guide.

Legacy Content for TIP Endpoints

In a TIP Compatibility > Prefer TIP conference, if a TIP endpoint doesn't have the required capabilities to meet the content threshold based on the conference line rate, the RealPresence Collaboration Server considers that TIP endpoint as legacy and sends content to it over the video channel.

Enable NoiseBlock™

The RealPresence Collaboration Server uses NoiseBlock,™ a heuristic algorithm, to monitor and lessen the audio of AVC endpoints with high levels of non-speech background noise. This helps prevent those endpoints from mistakenly become the active speaker, which could detract from the overall video conferencing experience.

The NoiseBlock feature is supported for AVC endpoints only in Continuous Presence (CP) and in Mixed CP and SVC conferences. In mixed CP and SVC conferences, the RealPresence Collaboration Server blocks audio towards AVC-based endpoints only.

Polycom, Inc. 44

Page 66

Advanced Conferencing Profile Features

It affects only AVC-based and audio only endpoints (non-SAC endpoints). It does not affect SVC-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.

Typically, the NoiseBlock feature is enabled by default based on the interaction of two configuration elements:

● The ENABLE_SELECTIVE_MIXING flag value (enabled by default) and

● The Auto mute noisy endpoints setting (enabled by default)

Note that NoiseBlock does not guarantee exact identification of non-speech originated sounds and when the endpoints are automatically muted by the MCU, no indication is displayed in RMX Manager or at the endpoint.

● 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.

● 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.

Polycom, Inc. 45

Page 67

Conference Management

If your environment has a standalone RealPresence Collaboration Server, you can use it to schedule and start conferences.

IMPORTANT:

If your environment includes a Polycom Scheduler feature, or another scheduling application such as Microsoft Outlook or the Polycom Conferencing Add-in for Microsoft Outlook, Polycom recommends that you create and schedule conferences using one of these standard scheduling applications and not the MCU.

This section on conference management discusses how to schedule and start conferences and what operations are available to perform on active conferences.

Viewing Scheduled Conferences

Each RealPresence Collaboration Server maintains its own calendar of scheduled conferences in the Reservation Calendar.

RealPresence® Resource Manager, which has a Web

To view scheduled conferences in the Reservation Calendar:

» In RMX Manager, go to RMX Management > Rarely Used > Reservations.

Scheduling a Conference

On the RealPresence Collaboration Server, you schedule a conference by making a reservation. The reservation reserves the required resources for the number of participants at the time and duration you specify. Resources are reserved for participants at the highest video resolution supported by the line rate specified in the conference profile associated with the reservation and up to the maximum system video resolution specified for the system.

To schedule a conference:

1 In RMX Manager, go to RMX Management > Rarely Used > Reservations.

2 In the Reservation Calendar, select the date and time for the future conference. Drag the cursor

across the calendar to extend the duration of the conference.

3 Right-click and select New Reservation.

4 Select and edit the conference parameters you wish to define.

Polycom, Inc. 46

Page 68

Conference Management

General Conference Parameters

Field Description

Display Name Unique name that identifies the conference within RMX Manager.

If left blank, the MCU automatically generates a Display Name for the conference, which can then be modified.

The maximum field length for the Display Name is approximately:

• 80 ASCII characters

• 40 European or Latin text characters

• 25 Asian text characters

Do not use comma or semi-colon characters in this field.

Duration Identifies the duration of the conference in HH:MM format.

Permanent Conference Displayed in the New Conference dialog only. Enable this option to create this

conference as a standard recurring conference.

Routing Name Unique name with which the MCU registers the conference with network devices such

as gatekeepers and SIP servers. If left blank, the MCU automatically generates a Routing Name. Because this name

must be ASCII characters, the MCU defines the name as follows:

• If ASCII characters are entered as the Display Name, it is used also as the Routing

Name

• If a combination of Unicode and ASCII characters (or full Unicode text) is entered as

the Display Name, the ID (such as Conference ID) is used as the Routing Name.

Polycom recommends you allow the MCU to assign the Routing Name automatically

Profile Choose the pre-defined conference profile that best identifies the conferencing mode,

line rate, media settings and general settings suitable for your conferencing environment. For a detailed description of Conference Profiles, see Conference

Profiles and Templates .

ID Unique ID number for the conference on the MCU. If left blank, the MCU automatically

assigns an ID number once the conference starts. Polycom recommends you allow the MCU to assign the Routing Name automatically.

Communicate this conference ID to dial-in participants to enable them to dial in to the conference.

Note: If setting the Conference ID to the digits that are used for MCU prefix in Gatekeeper (for example gatekeeper prefix is set to 10 and the conference ID is 1001), the system will not be able to dial to the destination conference as the prefix digits are truncated from the conference ID, preventing the system from locating it.

Conference Password Password that participants must enter to join the conference. If left blank, participants

are not required to enter a password to join the conference. This password is valid only in conferences that are configured to prompt for a

conference password. By default, this password is 4 numeric characters. The administrator can modify

requirements for this field. For more information, see System Flags . The MCU can be configured to automatically generate this password when this field is

left blank. For more information, see System Flags .

Polycom, Inc. 47

Page 69

Conference Management

General Conference Parameters

Field Description

Chairperson Password Password that the chairperson must enter to join the conference with chairperson

responsibilities. If left blank, chairperson functionality is not enabled for the conference. This password is valid only in conferences that are configured to prompt for a

chairperson password. By default, this password is 4 numeric characters. The administrator can modify

requirements for this field. For more information, see System Flags . The MCU can be configured to automatically generate this password when this field is

left blank. For more information, see System Flags .

Reserve Resources for Video Participants

(Appliance Edition only)

Reserve Resources for Audio Participants

(Appliance Edition only)

Maximum Number of Participants

Enable ISDN (audio/video) Dial-in

ISDN (audio/video) Network Service

Dial-in Number (1) Unique dial-in number for the conference. Choose this number from the dial-in number

Number of video participants for which the system must reserve resources. Default: 0 participants. Maximum participants:

• MPMRx-D / RMX1800: 100

• MPMRx-S: 30

Number of audio participants for which the system must reserve resources. Default: 0 participants. Maximum participants:

• MPMRx-D / RMX1800: 300

• MPMRx-S: 90

Total number of participants that can join to the conference. Choose Automatic to allow resource availability to determine the maximum number of participants that can join the conference.

Note: If a number is specified, it should be large enough to accommodate the participants specified in the Reserve Resources for Video/Voice Participants fields.

Allows ISDN-video and ISDN-voice participants to join directly to the conference.

Choose the pre-defined network service that best suites your conferencing environment. Identifies the pre-defined Network Service.

range defined for the selected Network Service. If left blank, the MCU automatically assigns a number from the dial-in range defined for

the selected ISDN (audio/video) Network Service.

Dial-in Number (2) Second unique dial-in number for the conference. Again, choose this number from the

dial-in number range defined for the selected Network Service. By default, the second dial-in number is not defined.

5 To make the conference recurring, click Schedule and enter the required scheduling and recurrence

information.

6 Click Participants and add participants from the Address Book or click New and enter the required

information for new participants.

7 If required, chose a participant as a lecturer and as needed enable Dial Out Manually, so the MCU

can dial out to the lecturer.

Polycom, Inc. 48

Page 70

Conference Management

8 To override the layout identified in the selected conference profile, click Media Sources and enable

Override layout from profile.

9 To add optional conference information, click Information and enter the required text into the Info1,

Info2, Info3, or Billing Info text boxes.

10 Click OK to schedule the conference.

Unless otherwise specified, the system automatically assigns the conference an ID when the conference starts.

11 Communicate the conference ID to conference dial-in participants.

Starting an Ad Hoc Conference

Ad hoc conferences are those created and started immediately.

To create and start an ad hoc conference:

1 In the Conferences section of RMX Manager, click New Conference ().

2 Select and edit the conference parameters you wish to define. For more information about the

conferencing parameters, see General Conference Parameters .

3 Click Participants and add participants from the Address Book or click New and enter the required

information for new participants.

4 If required, chose a participant as a lecturer and as needed enable Dial Out Manually, so the MCU

can dial out to the lecturer.

5 To override the layout identified in the selected conference profile, click Media Sources and enable

Override layout from profile.

6 To add optional conference information, click Information and enter the required text into the Info1,

Info2, Info3, or Billing Info text boxes.

7 Click OK to start the conference.

Unless otherwise specified, the system automatically assigns the conference an ID when the conference starts.

8 Communicate the conference ID to conference dial-in participants.

Polycom, Inc. 49

Page 71

Conference Management

Other Ways to Start a Conference

The RealPresence Collaboration Server provides many ways to start a conference. The most common method is documented previously. The other ways include:

● By dialing into a meeting room

● By dialing into an ad hoc entry queue

● By clicking on a reservation in the calendar

 If the reservation start time is past due, the conference starts immediately.

 If the reservation start time is in the future, the conference starts at the specified date and time.

● By clicking on a conference template and selecting Start Conference from Template

● By copying and pasting a conference in the Conferences list.

● From Microsoft Outlook using the Polycom Conferencing Add-in for Microsoft Outlook.

Polycom Conferencing for Microsoft Outlook is an add-in that enables users to easily organize and invite attendees to video-enabled meetings via Microsoft Outlook®.

This feature is applicable to Continuous Presence (CP) conferences only.

Polycom, Inc. 50

Page 72

Working with Active Conferences

If your environment has a standalone RealPresence Collaboration Server, you can use it to manage active conferences.

IMPORTANT:

If your organization uses another conference management application such as the Polycom RealPresence® Resource Manager, Polycom recommends that you create and schedule conferences using that applications and not the MCU.

This section discusses what actions are available to administrators, operators and chairpersons as they interact with active conferences.

General Conference Management Tasks

An RMX administrator or operator may be required to perform these general conference management tasks on an active conference.

Viewing the List of Active Conferences

You can view the list of active conferences in the main Conferences List section of RMX Manager.

Viewing the Properties of an Active Conference

In general, a conference’s properties are derived from the conference profile and conference template used to define the conference.

To view the properties of an active conference:

1 In the RMX Manager Conferences List, select the active conference of interest.

2 Right-click and select Conference Properties.

For information about the conference parameters identified, see General Conference Parameters .

Locking a Conference

You must be logged in as a chairperson, operator, or administrator to lock an active conference.

Polycom, Inc. 51

Page 73

Working with Active Conferences

To lock a conference:

1 In the RMX Manager Conferences List, select the active conference to lock

2 Right-click and select Lock Conference.

Locking the conference hides the list of conference participants in the Participants pane. If the conference is locked, a voice prompt informs users that the conference is secured and they cannot join.

Unlocking a Conference

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

To unlock a locked conference:

1 In the RMX Manager Conferences List, select the active conference to unlock.

2 Right-click and select Unlock Conference.

When the conference is unlocked, a voice prompt informs users that they can join the conference and all participants taking part in the conference are displayed.

Participant Management Tasks

An RMX administrator or operator may be required to perform participant management tasks for participants who are in an active conference.

Viewing the List, State and Properties of Participants

You can view the list of participants in an active conference including other information about the conference participant’s state and other participant properties.

To view the list and state of active conference participants:

1 In the RMX Manager Conferences List, select the active conference of interest.

RMX Manager displays the Participants List and the status of each participant including:

Column Icon/Description

Name Displays the name and type (icon) of the participant:

Audio Participant – Connected via IP phone or ISDN (audio/video).

Video Participant – Connected with audio and video channels.

Polycom, Inc. 52

Page 74

Working with Active Conferences

Column Icon/Description

Status Displays the connection status (text and icon) of the participant. If there is no problem with

the participant’s connection no indication is displayed.

Connected – The participant is successfully connected to the conference.

Disconnected – The participant is disconnected from the conference. This

status applies only to defined participants.

Waiting for Dial-in – The system is waiting for the defined participant to dial into the conference.

Partially Connected – The connection process is not yet complete; the video channel has not been connected.

Faulty Connection – The participant is connected, but problems occurred in the connection, such as synchronization loss.

Secondary Connection – The endpoint’s video channel cannot be connected to the conference and the participant is connected only via audio.

Awaiting Individual Assistance (AVC-based connection) – The participant has requested the user’s (operator’s) assistance.

Awaiting Conference Assistance (AVC-based connection) – The participant has requested the operator’s assistance for the conference. This usually means that the user (operator) has been requested to join the conference.

Connected, Noisy – Participant’s endpoint is requesting too many intras, resulting in the MCU ceasing to send intras to the endpoint to preserve conference quality for all other participants.

Polycom, Inc. 53

Page 75

Working with Active Conferences

Column Icon/Description

Role Displays the participant’s role or function in the conference:

Chairperson – The participant is defined as the conference chairperson. The chairperson can manage the conference using touch-tone signals (DTMF codes).

Lecturer (AVC-based connection) – The participant is defined as the conference Lecturer.

Lecturer and Chairperson – The participant is defined as both the conference Lecturer and Chairperson.

Cascade-enabled Dial-out Participant (AVC-based connection) – A special participant functioning as a link in a cascaded conference.

Recording (AVC-based connection) – A special participant functioning as a Recording Link.

Note: The Recording participant does not support H.264 High Profile. If recording a conference set to H.264 High Profile, the Recording participant connects as Audio Only and records the conference Audio while displaying the recording icon for the conference.

Request to speak (AVC-based connection) - Participants that were muted by the conference organizer/system operator can indicate that they want to be unmuted by entering the appropriate DTMF code (default 99).

The icon is displayed for 30 seconds.

IP Address/Phone The IP participant’s IP address or the ISDN (audio/video) participant’s phone number.

Alias Name/ SIP Address

The participant’s Alias Name or SIP URI.

The alias of a Polycom

RealPresence® Media Suite if the participant is functioning as a

recording link.

Network The participant’s network connection type – H.323, or SIP or ISDN (audio/video).

Dialing Direction Dial-in – The participant dialed the conference.

Dial-out – The MCU dialed the participant.

Audio Displays the status of the participant’s audio channel.

If the participant’s audio is connected and the channel is neither muted nor blocked, no indication is displayed.

Disconnected – Participant’s audio channel is disconnected. This is a defined participant who is waiting to be connected to the conference.

Muted – Participant’s audio channel is muted. Indicates who initiated the Mute: participant, RealPresence Collaboration Server User or MCU. The participant can still hear the conference.

Blocked – Transmission of audio from the conference to the participant is blocked.

Muted and Blocked - Audio channel is muted and blocked.

Polycom, Inc. 54

Page 76

Working with Active Conferences

Column Icon/Description

Video Displays the status of the participant’s video channel.

If there is no problem with the participant’s video connection and the channel is neither suspended nor secondary, no indication is displayed.

Disconnected – Participant’s video channel is disconnected. This is a defined participant who is waiting to be connected to the conference.

Suspended – Video transmission from the endpoint to the conference is suspended.

Secondary – Participant is connected only through the audio channel due to problems with the video channel.

Encryption (AVC-based connection) Indicates that the endpoint is connected to the

conference using encryption.

Service Name Displays the IP Network Service used to connect this participant to the conference.

FECC Token Participant is the holder of the Far End Camera Control (FECC) token and has

FECC capabilities. The FECC token can be allocated to only one participant at a time and remains

unallocated if no participant requests it. Note: FECC is not supported with ISDN-video.

Content Token Participant is the holder of the Content token and has content sharing

permission. The Content token can be allocated to only one participant at a time and remains

unallocated if no participant requests it.

2 For more information about a participant, select the participant of interest.

3 Right-click and select Participant Properties.

Adding Participants to an Active Conference

Operators and administrators can add participants to active conference.

If no participants were defined for the conference or as long as no participants are connected, the indication Empty and a warning icon ( ) appear in the Status column in the Conferences pane.

The conference status changes when participants connect to the conference.

To add a participant or group to an active conference:

1 In the RMX Manager Conferences List, select the active conference of interest.

2 Click Participants and then:

a Click Add from Address Book, select the required groups and participants, and click Add

Polycom, Inc. 55

Page 77

Working with Active Conferences

b Click New and enter the required information for the new participant, and click Add.

If any of the participants added to the conference are dial-out participants, the MCU initiates a call to the participant.

Moving Participants Between Conferences

An RMX administrator or operator can move participants between active Continuous Presence (CP) Only conferences or between an Entry Queue and active CP conference (if the participant failed to enter the correct conference ID or conference password).

An RMX administrator or operator cannot move participants from Lost Packet Recovery (LPR)-enabled, Video Switching, or Telepresence conferences. Moving participants between encrypted and non-encrypted conferences depends on the ALLOW_NON_ENCRYPT_PARTY_IN_ENCRYPT_CONF flag setting, as described in the following table:

Participant Move Capabilities vs. ALLOW_NON_ENCRYPT_PARTY_IN_ENCRYPT_CONF flag setting

Source Conference / Entry Queue

Flag Setting

NO Yes Yes Yes

Encrypted

Destination Conference Encrypted Move Enabled?

NO Yes No Yes

NO No Yes No

NO No No Yes

YES Yes Yes Yes

YES Yes No Yes

YES No Yes Yes

YES No No Yes

Note the following:

● When moving participants, IVR messages and slide display (if enabled for the conference) are

skipped.

● When moving dial-out participants, they will be disconnected from the original conference, and then

the MCU automatically dials out to connect them to the destination conference.

● Participants in cascaded conferences links cannot be moved between conferences.

● Participants cannot be moved to a conference if the move will cause the number of participants to

exceed the maximum number of participants allowed for the destination conference.

To move a participant from one conference to another:

1 In the RMX Manager Conferences List, select the active conference of interest.

2 In the Participant list, select the participant to move.

3 Right-click and select one of the following options:

 Move to Operator Conference - To move the participant(s) to an Operator conference.

Polycom, Inc. 56

Page 78

Working with Active Conferences

 Move to Conference - To move the participant to another ongoing CP conference.

 Back to Home Conference - If the participant was moved to another conference or to an

Operator conference, this options returns the participant back the original conference.

This option is not available if the participant was moved from an Entry Queue to an active conference.

4 In the Move to Conference, select the destination conference and click OK.

Sending a Message to Participants During a Conference

Using the Message Overlay feature, an RMX administrator or operator can send messages to a single conference participant, a number of selected participants, or all conference participants. The RMX user can enable or modify the Message Overlay feature for active conferences or for future conferences as part of the conference profile.

The Message Overlay feature is not available:

● In Video Switching (VSW) conferences.

● In Lecture Mode

● When the PCM menu is active

● On endpoints that have their video suspended

Note: The content streams sent by the RealPresence Collaboration Server towards SVC endpoints

are AVC (H.264 encoded) streams. Enabling content transcoding in a Mixed mode conference causes the RealPresence Collaboration Server to use a single content encoder for sending content to H.264 AVC and SVC endpoints. Similar to the AVC endpoints, all SVC endpoints joining a conference with message overlay on content stream enabled, receive the configured message overlay on their content streams in content transcoding mode. But SVC endpoints don’t receive the same message overlay on their people video, as by design RealPresence Collaboration Server doesn’t support message overlay on SVC video streams.

To send messages to conference participants:

1 In the RMX Manager Conferences List, select the active conference of interest.

2 In the Participant list, select the participants to receive the message.

3 Right-click and select Send Text Message to Participant.

4 In the Conferences list, again select the conference of interest.

5 Right click and select Conference Properties.

6 Go to Message Overlay and check the Enable option.

7 In the Content field, enter the message text (up to 50 characters) to be displayed to selected

conference participants.

Note that the number of characters that can be included in a message varies according to the language and the type and size of font used.

8 Specify the font size, color, position, and transparency.

9 Specify the speed at which the text should move (static, slow, or fast) and how often it should repeat.

Polycom, Inc. 57

Page 79

Working with Active Conferences

10 Click OK.

Changes to the Message Overlay content or display characteristics (position, size, color and speed) are immediately visible to all participants.

Restricting Content Sharing

You can restrict content sharing/broadcasting to the conference lecturer. Restricting content sharing/broadcasting prevents the accidental interruption or termination of H.239 Content while it is shared in a conference.

Enable this restriction by setting the RESTRICT_CONTENT_BROADCAST_TO_LECTURER system flag to ON. For more information about setting this system flag, see System Flags .

Designating a Participant the Lecturer in an Active Conference

During an ongoing conference, you can change the conference to Lecture Mode by designating a participant the lecturer.

In Lecture Mode, all participants see the lecturer in full screen, while the conference lecturer sees all the other conference participants in the selected layout. When the number of participants in a conference is greater than the number of cells in the conference layout, switching between participants occurs every 15 seconds. Automatic switching is suspended when one of the participants begins talking, and it is resumed automatically when the lecturer resumes talking.

To designate a participant the lecturer during the ongoing conference:

1 In the RMX Manager Conferences List, select the active conference of interest.

2 Right click and select Conference Properties.

3 Go to Video Settings, and in the Lecturer field, select the lecturer from the list of the connected

participants.

4 To enable automatic switching between participants viewed on the lecturer’s screen, enable Lecturer

View Switching.

5 To change the video layout for the lecturer, select another video layout option.

6 Click OK.

Muting Participants Other Than Lecturer

During an ongoing conference (including a cascaded conference) that is set to Lec ture M ode, y ou can mute all participants other than the lecturer. This prevents conference participants from interrupting the lecture.

You can enable or disable the Mute Participants Except Lecturer option at any time after the start of the conference. When enabled, conference participants are not muted until the lecturer joins the conference.

Muted participants can only be unmuted by:

● A RealPresence Collaboration Server administrator or operator or

Polycom, Inc. 58

Page 80

Working with Active Conferences

● The participant entering the DTMF code to activate the Mute All Except Me option. To do this, the

participant must be authorized to do so in the IVR Services properties). In this case, the lecturer’s audio is muted and the authorized participant’s audio is unmuted until you reactive the Mute Participants Except Lecturer option again.

When the Mute Participants Except Lecturer option is enabled, the mute indicator on the participant video endpoint display are not visible because the mute participants was initiated by the MCU. You may wish to inform participants that their audio is muted by using the Message Overlay functions. For more information on this function, see Sending a Message to Participants During a Conference .

To mute all participants other than the lecturer during the ongoing conference:

1 In the RMX Manager Conferences List, select the active conference of interest.

2 Right-click and select Profile Properties.

3 Go to Audio Settings and enable the Mute Participants Except Lecturer option.

4 If a lecturer is not identified in the Lecturer field, select the lecturer from the list of the connected

participants.

5 Click OK.

When the Mute Participants Except Lecturer option is enabled and a conference has started, the Mute by MCU icon is displayed in the Participants pane.

Previewing a Participant’s Video

You can preview the video sent from a participant to the conference (MCU) and the video sent from the conference to a participant by selecting the appropriate option from the Participant pop-up menu. This allows you to monitor the quality of the video sent and received by participant’s in conference and identify possible quality degradation. The video preview is displayed in a separate independent window with no disruption to the conference and the video preview window size and resolution are adjusted to the resolution of the PC on which it is displayed.

Polycom, Inc. 59

Page 81

Working with Active Conferences

To display the video preview window, the display system must meet the following minimum system requirements:

● DirectX is installed

● DirectDraw Acceleration is enabled and no other application is using the video resource

● Hardware acceleration is enabled

Refer to the system documentation for information about how to enable these options. If the video card installed in the PC does not support DirectDraw Acceleration, a black window may be viewed.

Note the following:

● RealPresence Collaboration Server supports Video Preview in AVC CP conferences only

● Live video shown in the preview window does not include shared content being sent by the participant

● Video preview is supported in cascaded conferences

● Video preview is disabled in encrypted conferences

● Video preview is not displayed when the participant’s video is suspended

To preview the participant video:

1 In the RMX Manager Conferences List, select the active conference of interest.

2 From the conference Participants pane, select the participant whose video you want to preview.

3 Right-click and select one of the following options:

 View Participant Sent Video - To display the video sent from the participant to the conference.

 View Participant Received Video - To display the video sent from the conference to the

participant.

The Video Preview window opens.

Enabling Auto Scan

When the number of participants in a conference is greater than the number of cells in the conference layout, you can display those extra participants within a single designated cell in the conference layout. Auto Scan only takes effect when the number of participants is larger than the number of cells in the conference layout. RealPresence Collaboration Server supports Auto Scan in AVC CP conferences only

Polycom, Inc. 60

Page 82

Working with Active Conferences

To enable Auto Scan:

1 In the RMX Manager Conferences List, select the active conference of interest. and click

Conference Properties.

2 Right-click and in the Conference Properties - General dialog, click Video Settings.

The Video Settings dialog is displayed.

Reference Number Description

1 Auto Scan interval

2 Auto Scan option

3 Selected video layout

4 Selected video layout cell

3 If Auto Layout is enabled, clear it.

4 In the video layout cell to be designated for Auto Scan, select Auto Scan from the drop-down menu.

5 Select the scanning interval from the Auto Scan Interval(s) list .

6 Click Apply or OK.

Polycom, Inc. 61

Page 83

Working with Active Conferences

Enabling Customized Polling

Customized Polling allows you to define an Auto Scan order and an Auto Scan time interval. Customized Polling only takes effect when the number of participants is larger than the number of cells in the layout.

Note the following:

● RealPresence Collaboration Server supports Auto Scan and Customized Polling in AVC CP

conferences only

● If Customized Polling is not defined, the RealPresence Collaboration Server will Auto Scan based on

the order in which participants connected to the conference.

To define the scanning order in the Customized Polling tab:

1 In the RMX Manager Conferences List, select the active conference of interest. and click

Conference Properties.

2 Right-click and in the Conference Properties - General dialog, click Customized Polling.

Polycom, Inc. 62

Page 84

Working with Active Conferences

Reference Number Description

1 All conference participants

2 Add/Delete

3 Move participant up or down in scanning order

4 Add All/Delete All

5 Scanning order

All conference participants are listed in the left pane (All Participants) whereas the participants to be displayed in the Auto Scan enabled cell are listed in the right pane (Scanning Order).

3 Use the buttons in the dialog to select the participants and determine their scanning order.

4 Click Apply or OK.

Canceling a Message Overlay

You can cancel the messages being sent to conference participants whether the message is part of the conference profile or not.

To cancel the Message Overlay:

1 In the Conferences list of RMX Manager, select the active conference of interest.

2 Right click and select Conference Properties.

3 Go to Message Overlay and clear the Enable checkbox.

Adding a Participant in an Active Conference to the Address Book

You can add a participant of an active conference to the Address Book, thus saving their information for future conferences. In this case, the participant is always added to the Main group in the Address Book.

To add a participant in an active conference to the Address Book:

1 In the Conferences list of RMX Manager, select the active conference of interest.

2 In the Participant list, select the participants to add.

3 Right-click and select Add Participant to Address Book.

Viewing the List of Participants Awaiting Help

The Participant Alerts section at the bottom of RMX Manager flashes when participants are awaiting help. Double-click on the Participant Alert title to view the list of participants awaiting help.

Polycom, Inc. 63

Page 85

Working with Active Conferences

Content Sharing Management Tasks

An RMX administrator or operator may be required to perform these tasks to manage content sharing into an active conference.

Giving Exclusive Content Sharing Ownership

When not in Exclusive Content Mode, all conference participants with capable devices can share content with the conference. As an RMX administrator or operator, you can give a participant the exclusive right to share content.

To give token ownership:

1 In the Participants list, select the participant to define as the exclusive content token owner.

2 Right-click and select Change To Content Token Owner.

If another participant is currently sharing content, he is requested to release the token, and the participant selected as the token owner is marked as exclusive. RMX Manager displays a content indicator icon in the Role column of the participant’s entry in the Participants list.

Canceling Exclusive Content Sharing Ownership

An RMX administrator or operator can cancel a participant’s right to exclusive content sharing. Doing this returns the conference to its original conference sharing state.

To cancel token ownership:

1 In the Participants list, select the participant currently defined as the exclusive content token owner

2 Right-click and select Cancel Content Token Owner.

Abort a Content Sharing Session

An RMX administrator or operator can immediately abort a content sharing session.

To abort a content session:

1 In the Conferences list of RMX Manager, select the active conference of interest.

2 Right-click and select Abort H.239 Session.

Conference Recording Management Tasks

You can only start and stop recording for an active conference when the conference profile assigned to the conference has recording enabled and has a recording link set up. For more information on enabling recording via the conference profile see .

Polycom, Inc. 64

Page 86

Working with Active Conferences

If you edit the conference profile that is being used for active conferences to enable recording, that change will apply to the active conference, but it will also apply to all other active conferences and future conferences using that profile, which may not be desirable.

If an active conference is using the

Polycom, Inc. 65

Page 87

Cascading Conferences

Note: Content Applicability

• Cascading information applies to AVC-enabled Conferencing (CP, VSW, and mixed CP and SVC).

• Cascading Conferences are not supported by Collaboration Server (RMX) 1800 with no DSP cards,

and Collaboration Server 1800, Entry Level.

Cascading allows administrators to connect one conference directly to one or several conferences, depending on the topology, creating one large conference. The conferences can run on the same MCU or different MCUs.

There are many reasons for cascading conferences, the most common are:

● Connecting two conferences on different MCUs at different sites.

● Utilizing the connection abilities of different MCUs, like different communication protocols, such as,

serial connections, ISDN-video, etc.

Conferences are cascaded when a link is created between two conferences, running on two different MCUs.

Cascading Link Properties

Cascade links are treated as endpoints in CP conferences. They are allocated resources as any other endpoint according to Default Minimum Threshold Line Rates per Resolution and Resolution Configuration

for CP Conferences

They transmit audio, video and content between conferences as well as DTMF codes input from other endpoints in the conference.

Setting the Video Layout in Cascading conferences

When cascading two conferences, the video layout displayed in the cascaded conference is determined by the selected layout in each of the two conferences. Each of the two conferences will inherit the video layout of the other conference in one of their windows.

In order to avoid cluttering in the cascaded window, it is advised to select appropriate video layouts in each conference before cascading them.

Polycom, Inc. 66

Page 88

Cascading Conferences

Video layout of conference B within window of conference A

Video layout of conference A within window of conference B

Video Layouts in Cascaded Conferences

Conference A Conference B

Without cascading

During cascading

Guidelines

To ensure that conferences can be cascaded and video can be viewed in all conferences the following guidelines are recommended:

● The same version installed on all MCUs participating the cascading topology.

● The same license installed on all MCUs participating the cascading topology.

● Identical Conference Parameters defined in the Profile of the conferences participating in the

cascading topology:

 Conference line rates

 Content rate

 Encryption settings

● DTMF codes defined using identical numeric codes in the IVR services assigned to the cascading

conferences

● DTMF forwarding suppressed

● Video layout of the link is set to 1x1 by the appropriate system flag.

Cascaded links in 1x1 video layout use SD resolution.

● When the Mute Participants Except Lecturer option is enabled in the Conference Profile, all

participants (including the link participants) except the lecturer are muted.

● Gathering phase is not supported in Cascading Conferences.

Polycom, Inc. 67

Page 89

Cascading Conferences

Flags Controlling Cascade Layouts

● Setting the FORCE_1X1_LAYOUT_ON_CASCADED_LINK_CONNECTION System Flag to YES

(default) automatically forces the cascading link to Full Screen (1x1) in CP conferences, hence displaying the speaker of one conference to a full window in the video layout of the other conference.

Set this flag to NO when cascading between an Collaboration Server and an MCU/MGC functioning as a Gateway, if the participant layouts on the MCU/MGC are not to be forced to 1X1.

● Setting the AVOID_VIDEO_LOOP_BACK_IN_CASCADE System Flag to YES (default) prevents

the speaker’s image from being sent back through the participant link from the cascaded conference. This can occur in cascaded conferences with conference layouts other than 1x1. It results in the speaker’s own video image being displayed in the speaker’s video layout.

This option is supported with:

 In IP (H.323, SIP) and ISDN-video environments.

This option is supported with Basic Cascading of Continuous Presence and Video Switched conferences. If a Master MCU has two slave MCUs, participants connected to the slave MCUs will not receive video from each other.

 Video resolution will be according to the Resolution Configuration, or VSW profile.

For more details on defining system flags, see Modifying System Flags.

DTMF Forwarding

When two conferences are connected over an IP link, DTMF codes from one conference are not forwarded to the second conference. The following operations with the exception, and are available throughout the conference, with their DTMF codes forwarded (i.e. they will apply to both conferences):

● Terminate conference.

● Mute all but me.

● Unmute all but me.

● Secure conference.

● Unsecure conference.

Note: DTMF Codes Forwarding

During cascading between a gateway and a conference all DTMF codes are forwarded from the gateway to the conference and vice versa.

Play Tone Upon Cascading Link Connection

The Collaboration Server can be configured to play a tone when a cascading link between conferences is established. The tone is played in both conferences.

This tone is not played when the cascading link disconnects from the conferences.

The tone used to notify that the cascading link connection has been established cannot be customized.

The option to play a tone when the cascading link is established is enabled by setting the System Flag CASCADE_LINK_PLAY_TONE_ON_CONNECTION to YES.

Default value: NO.

Polycom, Inc. 68

Page 90

Cascading Conferences

The tone volume is controlled by the same flag as the IVR messages and tones: IVR_MESSAGE_VOLUME.

Possible Cascading Topologies

The following cascading topologies are available for setting cascading conferences:

● Basic Cascading - only two conferences are connected (usually running on two different

Collaboration Servers). The cascaded MCUs reside on the same network.

● Star Cascading - one or several conferences are connected to one master conference. Conferences

are usually running on separate MCUs. The cascaded MCUs reside on the same network.

● MIH (Multi-Hierarchy) Cascading (in non-virtual MCUs) - several conferences are connected to each

other in Master-Slave relationship. The cascaded MCUs can reside on different networks.

System configuration and feature availability change according to the selected cascading topology.

Note: Sharing Content in Cascaded Conferences

For properly sharing content in cascaded conferences, predefined dial in and out link participants must be defined with Master/Slave settings in the conferences.

When Cascading between the Collaboration Server and third party MCUs, the participant defined in the Collaboration Server conference must be defined as Master.

When cascading between the Collaboration Server and a Codian MCU, set the system flag ENABLE_CODIAN_CASCADE to YES to ensure that the Collaboration Server is defined as a Master in cascading conferences at all times.

Basic Cascading

In this topology, a link is created between two conferences, usually running on two different MCUs. The MCUs are usually installed at different locations (states/countries) to save long distance charges by connecting each participant to their local MCU, while only the link between the two conferences is billed as long distance call.

● This is the only topology that enables both IP and ISDN-video cascading links.

● Cascading between Collaboration Server Virtual Edition and Collaboration Servers (RMX)

2000/1800/4000 is supported.

● When linking two conferences using an IP cascading link:

 The destination MCU can be indicated by:

 IP address

 H.323 Alias

 If IP cascading link is used to connect the two conferences, both MCUs must be located in the

same network.

● One MCU can be used as a gateway.

● The configuration can include two Collaboration Servers or one Collaboration Server and one MGC.

● Multiple Cascade Links enabling Cascading between MCUs hosting conferences that include

Immersive Telepresence Rooms (ITP), such as Polycom’s OTX and RPX Room Systems, can be defined. For more information see Creating Multiple Cascade Links Between Telepresence

Conferences.

Polycom, Inc. 69

Page 91

Cascading Conferences

Basic Cascading Using IP Cascaded Link

In this topology, both MCUs can be registered with the same gatekeeper or the IP addresses of both MCUs can be used for the cascading link. Content can be sent across the Cascading Link.

Basic Cascading Topology - IP Cascading Link

For example, MCU B is registered with the gatekeeper using 76 as the MCU prefix.

The connection between the two conferences is created when a dial out IP participant is defined (added) to conference A whose dial out number is the dial-in number of the conference or Entry Queue running on MCU B.

Dialing Directly to a Conference

Dial out IP participant in conference A dials out to the conference running on MCU B entering the number in the format:

[MCU B Prefix/IP address][conference B ID].

For example, if MCU B prefix is 76 and the conference ID is 12345, the dial number is 7612345.

Dialing to an Entry Queue

When dialing to an Entry Queue, the dial out participant dials the MCU B prefix or IP address of MCU B and the Entry Queue ID in the format:

[MCU B Prefix/IP address][EQ B ID].

For example, if MCU B prefix is 76 and the Entry Queue ID is 22558, the dial number is 7622558.

When the participant from conference A connects to the Entry Queue, the system plays to all the participants in Conference A the IVR message requesting the participant to enter the destination conference ID.

At this point, the Conference A organizer or any other participant in the conference can enter the required information for the IVR session using DTMF codes. For example, the meeting organizer enters the destination conference ID - 12345.

Any DTMF input from conference A is forwarded to the Entry Queue on MCU B to complete the IVR session and enable the move of the participant to the destination conference B.

Polycom, Inc. 70

Page 92

Cascading Conferences

Once the DTMF codes are entered and forwarded to the Entry Queue on MCU B, the IVR session is completed, the participant moved to the destination conference and the connection between the two conferences is established.

Automatic Identification of the Cascading Link

In both dialing methods, the system automatically identifies that the dial in participant is an MCU, creates a Cascading Link, and displays the link icon for the participant ( ). The master-slave relationship is randomly defined by the MCUs during the negotiation process of the connection phase.

Basic Cascading Using ISDN-video Cascaded Link

ISDN-video connection can be used to link between two MCUs or MCU and gateway and create a cascading conference. Content can be sent across the ISDN-video Cascading Link.

Network Topologies Enabling Content Sharing Over ISDN-video Cascaded Links

ISDN-video Cascaded links that support content sharing can be created between two gateways, gateway-to-MCU or between two MCUs in the following network topologies:

● Gateway to Gateway

Gateway to Gateway Topology

In this topology, an IP participant calls another IP participant over an ISDN-video link between two gateways.

● Gateway to MCU

Gateway to MCU/ MCU to Gateway Topology

In this topology, an IP participant calls a conference running on an MCU via a gateway and over an ISDN-video link.

Polycom, Inc. 71

Page 93

Cascading Conferences

● MCU to MCU

Cascading Between Two MCUs Using an ISDN-video Link

In this topology, an ISDN-video participant from conference running on MCU A calls a conference running on MCU B over an ISDN-video link.

Guidelines for ISDN-video Cascaded Links

● Content is restricted, in the sense that when another endpoint wants to send content, the first

endpoint must stop sending content before the second endpoint can initiate or send content.

● Endpoints that do not support H.239 can receive the Content using the Send Content to Legacy

Endpoints option.

● A participant joining a conference with active Content, cannot view it. Content sharing should be

restarted.

● Cascaded MCUs/Gateways must be registered with the same Gatekeeper or neighboring

Gatekeepers. MCUs and endpoints must also be registered with Gatekeepers.

● Gateway/MCU calls require definition of IVR Services. For more information see System

Configuration.

Note: Content Protocol over ISDN-video Cascaded link

The content sharing protocol is H.263 when sent over ISDN-video Cascading link.

Gateway to Gateway Calls via ISDN-video Cascading Link

When H.323 participants connects to another IP participants via a Gateway to Gateway call over an

ISDN-video link, the dialing string includes the following components: [GW A prefix in GK] - The prefix with which the Collaboration Server (gateway) is registered to the

gatekeeper. [GW Profile ID] - The ID of the Gateway Profile defined on Gateway A to be used for routing the call to

the Gateway B. [GW Profile ISDN (audio/video) number] - The dial-in number assigned to the Gateway Profile

defined on Gateway B, including the required country and area codes.

Information required that is not part of the dialing string:

Polycom, Inc. 72

Page 94

Cascading Conferences

[Destination number] - The destination number as alias, IPv4 address or ISDN (audio/video) number of participant B.

The dialing string format:

H.323 Participants connecting to another IP participant via a Gateway to Gateway call over an ISDN-video

link enter a dial string using the format:

For example:

GW A prefix in Gatekeeper - (not used with SIP) 22

Gateway Profile ID in GW A 9999

ISDN-video Dial-in Number assigned to the Gateway Session Profile GW B

IP Participant Alias 3456

4444103

H.323 participant dials: 229999*4444103, and when prompted for the Destination number enters 3456 followed by the pound key (#) using DTMF codes

SIP Participants connecting to another IP participant via a Gateway to Gateway call over an ISDN-video link enter a dial string using the format:

For example:

If Central Signaling IP address of Gateway A is 172.22.177.89, SIP participant dials: 9999@

172.22.177.89* 4444103 and when prompted for the Destination number enters 3456 followed by the pound key (#) using DTMF codes.

Gateway to MCU Calls via ISDN-video Cascading Link

When H.323 participants connects to a conference/Meeting Room via a Gateway to MCU call over an ISDN-video link, the dialing string includes the following components:

[GW A prefix in GK] - The prefix with which Gateway A is registered to the gatekeeper.

[GW Profile ID on GW A] - The ID of the Gateway Profile on GW A to be used for routing the call to

the Meeting Room/conference running on MCU B.

[Conference/Meeting Room/Entry Queue ISDN (audio/video) number] - The dial-in number

assigned to the Entry Queue/Meeting Room/Conference defined on MCU B, including the required country and area codes.

Information required that is not part of the dialing string:

[Destination Conference ID] - Only if using the Entry Queue on MCU B for routing calls or creating

new ad hoc conferences. The ID of the destination conference on MCU B.

The dialing string format:

Polycom, Inc. 73

Page 95

Cascading Conferences

For Example:

GW A prefix in Gatekeeper - (not used with SIP) 22

Gateway Profile ID in GW A 9999

ISDN-video Dial-in Number assigned to the Entry Queue/MR/conference

H.323 participant dials 229999*4444100

SIP participant dials (if Central Signaling IP address of Gateway A is 172.22.177.89) 9999@

172.22.177.89 IP* 4444100

If dialing an Entry Queue, when prompted for the Destination number enters 3456 followed by the pound key (#) using DTMF codes to create a new conference or join an ongoing conference with that ID.

4444100

MCU to MCU Calls via ISDN-video Cascading Link

A dial out ISDN-video participant is defined (added) to conference A running on MCU A. The participant’s dial out number is the dial-in number of the Entry Queue or conference running on MCU B (for example

54145106).

MCU A dials out to an Entry Queue or conference B running on MCU B using the Entry Queue number (for example 54145106) or the conference number.

When the participant, who is a dial-in participant in conference B, connects to the Entry Queue, the system plays to all the participants in Conference A the IVR message requesting the participant to enter the destination conference ID (or if connecting to a conference directly, the participant is requested to enter the conference password).

At this point the Conference A organizer or any other participant in the conference can enter the required information for the IVR session using DTMF codes. For example, the meeting organizer enters the destination conference ID - 12345.

Any DTMF input from conference A is forwarded to the Entry Queue on MCU B to complete the IVR session and enable the move of the participant to the destination conference B.

Once the DTMF codes are entered and the IVR session is completed, the participant is connected to the conference and the connection between the conferences is established. The system automatically identifies the calling participant as an MCU and the connection is identified as a cascading link and the cascading link icon is displayed for the participant ( ).

Collaboration Server Configuration Enabling ISDN-video Cascading Links

To enable Gateway-to-Gateway, Gateway-to-MCU and MCU-to-MCU calls over ISDN-video Cascading links, the following configurations are required:

● Modifying the IP Network Service to include the MCU Prefix in the Gatekeeper (in the Gatekeepers

dialog box). For more details, see Modifying the Default IP Network Service.

Polycom, Inc. 74

Page 96

Cascading Conferences

● ISDN-video Network Service is configured in both MCUs. For more details, Modifying an ISDN

(audio/video) Network Service.

● Configuring a Gateway Profile and assigning dial-in ISDN (audio/video) numbers. For details, see

Defining the Gateway Profile.

● Configure the Entry Queue or conference (for direct dial-in) as enabled for ISDN-video connection and a dial-in number is assigned (for example 54145106).

● Defining the dial-in ISDN-video participant in MCU B and Dial-out ISDN-video participant in MCU A (for MCU-to-MCU cascading conferences).

A dial out ISDN-video participant is defined (added) to conference A. The participant’s dial out number is the dial-in number of the Entry Queue or conference running on MCU B (for example 54145106).

Polycom, Inc. 75

Page 97

Cascading Conferences

MCU A dials out to an Entry Queue or conference B running on MCU B using the Entry Queue number (for example 54145106) or the conference number.

Conference Profile Definition

The following table lists the recommended Meeting Room/Conference Profile parameters setting when routing ISDN-video cascaded calls.

Recommended Conference Profile Options Setting

Line Rate Motion Sharpness Encryption LPR

128 ?

128 ? ?

128 ? ? ?

256 ?

256 ? ?

256 ? ? ?

384 ?

384 ? ?

Polycom, Inc. 76

Page 98

Cascading Conferences

Recommended Conference Profile Options Setting

Line Rate Motion Sharpness Encryption LPR

384 ? ? ?

512 ?

512 ? ?

512 ? ? ?

768 ?

768 ? ?

768 ? ? ?

Note: Line Rate Recommendation

Since the remote participant settings are unknown, it is recommended that the gateway or endpoint be configured to support a higher line rate (for example, 768 Kbps) to allow flexibility during endpoint capability negotiations.

MCU Interoperability Table

The following table lists the different MCU and Gateway configurations that are supported or implemented when routing Cascaded ISDN-video calls.

MCU Interoperability Table

Source Destination Scenario Version(s)

Collaboration Server Gateway

Collaboration Server MCU

Endpoint Collaboration

Collaboration Server MCU

Collaboration Server Gateway

Collaboration Server MCU

Collaboration Server Gateway

Server Gateway

Codian Gateway

User calls via a Gateway to a Remote Conference (user to conference)

User calls via a Gateway to a Remote User behind Gateway (user to user)

A dial out participants calls to a remote conference (conference to conference)

A dial out participants calls to a remote User behind a Gateway (Conference to User)

User calls directly to a remote user behind a Gateway (User to User)

Dial out participants use a fixed rule behind the Codian Gateway.

Collaboration Server v. 7.1 or later

Collaboration Server v. 7.1

Collaboration Server v. 7.1 Latest Codian version

Polycom, Inc. 77

Page 99

Cascading Conferences

MCU Interoperability Table

Source Destination Scenario Version(s)

Collaboration Server Gateway

Codian Gateway Collaboration

Collaboration Server MCU

Collaboration Server Gateway

Radvision Gateway

Endpoint Collaboration

Codian Gateway

Server MCU

Server Gateway

Radvision Gateway

Collaboration Server MCU

Collaboration Server Gateway

Server Gateway

Dial out participants use a fixed rule behind the Codian Gateway.

User calls via a Codian Gateway to a Remote Conference (user to conference)

User calls via a Codian Gateway to a Remote User behind Collaboration Server Gateway (user to user)

User calls via a Radvision Gateway to a Remote User behind Collaboration Server Gateway (user to user)

User calls via a Radvision Gateway to a Remote Conference (user to conference)

User calls via a Radvision Gateway to a Remote User behind Collaboration Server Gateway (user to user)

User calls directly to a DMA controlled environment

Collaboration Server v. 7.1 Latest Codian version

Collaboration Server v. 7.1 Latest Radvision version

Collaboration Server v. 7.1

Collaboration Server MCU

Collaboration Server Gateway

A dial out participants calls to a remote conference on a DMA controlled environment

Collaboration Server v. 7.1

Polycom, Inc. 78

Page 100

Cascading Conferences

Notes:

• On the Codian gateway Content is not supported with line rates of 128Kbps and below.

• To send Content from a participant over Radvision Gateway to a conference/participant, the

GWP20 patch must be installed in the RadVision gateway: On the Radvision gateway, open the GWP20 User Interface.

Select Settings > Advanced Commands.

In the Command box, enter H239OlcPatch. In the Parameters box, enter Enable and click Send.

Suppression of DTMF Forwarding

Forwarding of the DTMF codes from one conference to another over an ISDN-video cascading link is not automatically suppressed as with IP cascading link, and it can be limited to basic operations while suppressing all other operations by the system flag DTMF_FORWARD_ANY_DIGIT_TIMER_SECONDS.

System Flag Settings

The DTMF_FORWARD_ANY_DIGIT_TIMER_SECONDS flag determines the time period (in seconds) in which MCU A forwards DTMF inputs from conference A participants to MCU B. During that time, the forwarding MCU does not apply the DTMF command to itself.

Once the timer expires, most of the DTMF codes (excluding five operations as for IP links) entered in conference A are not be forwarded to conference B, and are applied within the MCU receiving the DTMF code. This is done to prevent an operation requested by a participant individually (for example, mute my line) to be applied to all the participants in conference B.

Flag range (in seconds): 0 - 360000

This flag is defined on MCU A (the calling MCU).

If a flag is not listed in the System Flags list it must be added to the system.cfg file before it can be modified.

For more details on defining system flags, see Modifying System Flags.

Polycom, Inc. 79

Polycom RealPresence 1800, RealPresence 2000, RealPresence 4000 Administration Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Before You Begin

Audience, Purpose, and Required Skills

Privacy

Getting Help

Polycom and Partner Resources

The Polycom Community

Product Overview

Product Features

Supported Network Configurations

IP Conferencing Network

ISDN (Audio/Video) Conferencing Network

Multipoint Conferencing Network

Required Software Components

System User Types

Administrator

Administrator Read-only

Operator

Chairperson

Auditor

User Interface Availability Based on User Type

Navigating the System

The MCU Pane

Conferences List

System Status Bar

List Pane

Address Book

RMX Management Pane

Conference Templates

Getting Started

Install RMX Manager

Connect to the MCU with RMX Manager

Add an MCU

Connect to an MCU

Configure the Time Settings

Requesting and Adding Certificates

Create a Certificate Signing Request

Installing the Certificate

Obtain the Display Name

Integrate with the RealPresence Resource Manager System

Overlay a Custom Logo on Conference Displays

Configure Required System Flags

Integrate with the RealPresence DMA System

Integrate with HARMAN Media Suite

Customizing the RMX Manager User Interface

Switch the RMX Management Section View

Move Items in the RMX Management Section

Restore Default RMX Manager User Interface

Conference Profiles and Templates

Conference Profiles

View the List of Conference Profiles

Add a New Conference Profile

Conference Profile Parameters

Conference Templates

View the List of Conference T emplates

Add a New Conference Template

Additional Conference Profile and Conference Template Tasks

Edit a Conference Profile

Delete a Conference Profile

Export a Conference Profile

Import a Conference Profile

Edit a Conference Template

Delete a Conference T emplate

Export a Conference Template

Import a Conference T emplate

Save an Ongoing Conference as a Template

Advanced Conferencing Profile Features

Enable Recording in the Conference Profile

Change Position of the Conference Indicators

Enable Multiple Content Resolutions (Transcoding) on TIP Endpoints

Binary Floor Control Protocol (BFCP) Support for TIP endpoints

Legacy Content for TIP Endpoints

Enable NoiseBlock™

Conference Management

Viewing Scheduled Conferences

Scheduling a Conference

Starting an Ad Hoc Conference