Polycom 2000, 4000 User Manual

Polycom RMX™ 2000/4000

Administrator’s Guide

Version

5.0.1

| January 2010 | DOC2518C

Trademark Information

Polycom®, the Polycom “Triangles” logo, and the names and marks associated with Polycom’s
products are trademarks and/or service marks of Polycom, Inc., and are registered and/or
common-law marks in the United States and various other countries.

All other trademarks are the property of their respective owners.

Patent Information

The accompanying product is protected by one or more U.S. and foreign patents and/or pending
patent applications held by Polycom, Inc.
Portions, aspects and/or features of this product are protected under United States Patent Law in
accordance with the claims of United States Patent No: US 6,300,973; US 6,492,216; US
6,496,216; US 6,757,005; US 6,760,750; US 7,054,620; US 7,085,243; US 7,113,200; US
7,269,252; US 7,310,320.

PATENT PENDING

© 2010 Polycom, Inc. All rights reserved.

Polycom, Inc.
4750 Willow Road
Pleasanton, CA 94588-2708
USA

No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc.
Under the law, reproducing includes translating into another language or format.
As between the parties, Polycom, Inc., retains title to and ownership of all proprietary rights with
respect to the software contained within its products. The software is protected by United States
copyright laws and international treaty provision. Therefore, you must treat the software like any
other copyrighted material (e.g., a book or sound recording).

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

Regulatory Notices

United States Federal Communication

Commission (FCC)

Part 15: Class A Statement. This equipment has

been tested and found to comply with the limits for a
Class A digital device, pursuant to Part 15 of the FCC
Rules. Test limits are designed to provide reasonable
protection against harmful interference when the
equipment is operated in a commercial environment.
This equipment generates, uses and can radiate
radio-frequency energy and, if not installed and used
in accordance with the instruction manuals, may
cause harmful interference to radio communications.
Operation of this equipment in a residential area is
likely to cause harmful interference, in which case the
user will be required to correct the interference at his
or her own expense.

Part 68: Network Registration Number. This
equipment is registered with the FCC in accordance
with Part 68 of the FCC Rules. This equipment is
identified by the FCC registration number.

If requested, the FCC registration Number and REN
must be provided to the telephone company.

Any repairs to this equipment must be carried out by
Polycom Inc. or our designated agent. This
stipulation is required by the FCC and applies during
and after the warranty period.

United States Safety Construction Details:

• All connections are indoor only.

• Unit is intended for RESTRICTED ACCESS

LOCATION.

• Unit is to be installed in accordance with the

National Electrical Code.

• The branch circuit overcurrent protection shall

be rated 20 A for the AC system.

• This equipment has a maximum operating

ambient of 40°C, the ambient temperature in
the rack shall not exceed this temperature.

To eliminate the risk of battery explosion, the battery
should not be replaced by an incorrect type.
Dispose of used batteries according to their
instructions.

CE Mark R&TTE Directive

Polycom Inc., declares that the Polycom RMX™
2000 is in conformity with the following relevant
harmonized standards:

EN 60950-1:2001
EN 55022: 1998+A1:2000+A2:2003 class A
EN 300 386 V1.3.3: 2005
Following the provisions of the Council Directive

1999/CE on radio and telecommunication terminal
equipment and the recognition of its conformity.

Canadian Department of Communications

This Class [A] digital apparatus complies with
Canadian ICES-003.

Notice: The Industry Canada label identifies certified
equipment. This certification means that the
equipment meets telecommunication network
protective, operational and safety requirements as
prescribed in the appropriate Terminal Equipment
Technical Requirements document(s). The
Department does not guarantee the equipment will
operate to the user's satisfaction.

Before installing this equipment, users should ensure
that it is permissible to be connected to the facilities
of the local telecommunications company. The
equipment must also be installed using an acceptable
method of connection. The customer should be
aware that compliance with the above conditions may
not prevent degradation of service in some situations.
Repairs to certified equipment malfunctions, may give
the telecommunications company causes to request
the user to disconnect the equipment.

Users should ensure for their own protection that the
electrical ground connections of the power utility,
telephone lines and internal metallic water pipe
system, if present, are connected together. This
precaution may be particularly important in rural
areas.

Caution: Users should not attempt to make such
connections themselves, but should contact the
appropriate electric inspection authority, or
electrician, as appropriate.

Regulatory Notices

RMX 2000: Chinese Communication Certificate

RMX 2000 complies with IDA standards G0916-07

Singapore Certificate

Table of Contents

Conference Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Conferencing Modes .............................................................................. 1-3

Standard Conferencing .................................................................. 1-3

Supplemental Conferencing Features ......................................... 1-5

Viewing Profiles ..................................................................................... 1-6

Profile Toolbar ................................................................................ 1-7

Defining Profiles ..................................................................................... 1-8

Modifying an Existing Profile ..................................................... 1-23

Deleting a Conference Profile ..................................................... 1-24

Additional Conferencing Information . . . . . . . . . . . . . . 2-1

Video Session Modes ............................................................................. 2-1

Dynamic Continuous Presence (CP) Mode ................................ 2-1

High Definition Video Switching Mode ..................................... 2-2

Continuous Presence (CP) Conferencing ............................................ 2-2

Video Resolutions in CP ................................................................ 2-3

Additional Video Resolutions in MPM+ Mode ......................... 2-4

Additional Intermediate Video Resolutions ............................... 2-4

Video Display with CIF, SD and HD Video Connections ....... 2-5

Setting the Maximum CP Resolution for Conferencing ... 2-5

CP Conferencing with H.263 4CIF ............................................... 2-6

H.263 4CIF Guidelines ........................................................... 2-7

High Definition Video Switching ......................................................... 2-8

Guidelines ........................................................................................ 2-8

Enabling HD Video Switching ..................................................... 2-9

Modifying the HD Video Switching Threshold Bit Rate .. 2-9

Creating a High Definition Video Switching Profile ......... 2-9

Monitoring High Definition Video Switching Conferences ... 2-11

H.239 ....................................................................................................... 2-12

Content Transmission Modes ..................................................... 2-12

Content Protocol ........................................................................... 2-13

Defining Content Sharing Parameters for a Conference ........ 2-14

Sending Content to Legacy Endpoints ...................................... 2-16

Polycom RMX 2000/4000 Administrator’s Guide

i

Table of Contents

Guidelines for Sending Content to Legacy Endpoints .... 2-16

Interoperability with Polycom CMA and DMA .............. 2-17

Content Display on Legacy Endpoints .............................. 2-18

Enabling the Send Content to Legacy Endpoints Option ....... 2-19

Changing the Default Layout for Displaying Content

on Legacy Endpoints ............................................................ 2-20

Stopping a Content Session ........................................................ 2-22

Lecture Mode ........................................................................................ 2-23

Enabling Lecture Mode ............................................................... 2-23

Enabling the Automatic Switching .................................... 2-23

Selecting the Conference Lecturer ..................................... 2-24

Restricting Content Broadcast to Lecturer ........................ 2-24

Lecture Mode Monitoring ........................................................... 2-25

Closed Captions .................................................................................... 2-28

Enabling Closed Captions ........................................................... 2-29

Media Encryption ................................................................................. 2-30

Media Encryption Guidelines ..................................................... 2-30

Conference Access ................................................................ 2-31

Entry Queue Access ............................................................. 2-32

Move Guidelines ................................................................... 2-34

Encryption Flag Settings .............................................................. 2-34

Enabling Encryption in the Profile ............................................ 2-35

Enabling Encryption at the Participant Level .......................... 2-35

Monitoring the Encryption Status .............................................. 2-37

LPR – Lost Packet Recovery ................................................................ 2-38

Packet Loss .................................................................................... 2-38

Causes of Packet Loss .......................................................... 2-38

Effects of Packet Loss on Conferences ............................... 2-38

Lost Packet Recovery ................................................................... 2-38

Lost Packet Recovery Guidelines ....................................... 2-39

Enabling Lost Packet Recovery .......................................... 2-39

Monitoring Lost Packet Recovery .............................................. 2-40

Telepresence Mode ............................................................................... 2-42

RMX Telepresence Mode Guidelines ........................................ 2-42

System Level ......................................................................... 2-42

Conference Level .................................................................. 2-43

Room (Participant/Endpoint) Level .................................. 2-43

ii

Polycom RMX 2000/4000 Administrator’s Guide

RPX and TPX Video Layouts ...................................................... 2-44

Enabling Telepresence ................................................................. 2-47

Conference Level .................................................................. 2-47

Room (Participant/Endpoint) Level .................................. 2-48

Saving an Ongoing Conference as a Template ................. 2-49

Starting an Ongoing Conference From a Template ......... 2-50

Cascading Conferences - Star Topology ........................................... 2-51

Enabling Cascading ...................................................................... 2-53

Creating the Cascade-enabled Entry Queue .................... 2-53

Creating the Dial-out Cascaded Link ................................ 2-55

Enabling Cascaded Conferences without Password ....... 2-58

Monitoring Cascaded Conferences ............................................ 2-59

Creating the Dial-out Link from a Conference Running on

the MGC to the Conference Running on the RMX .................. 2-60

Cascading Conferences - H.239-enabled MIH Topology ............... 2-61

MIH Cascading Levels ................................................................. 2-61

MIH Cascading Guidelines ......................................................... 2-62

Master and Slave Conferences ............................................ 2-62

Video Session Mode, Line Rate and Video Settings ........ 2-63

H.239 Content Sharing ......................................................... 2-64

Setting up MIH Cascading Conferences ................................... 2-65

RMX to RMX Cascading ...................................................... 2-65

MGC to RMX 2000 Cascading ............................................ 2-73

Starting and Monitoring MIH Cascading Conferences .......... 2-83

Monitoring Participants in an MIH Cascaded

Conference ............................................................................. 2-83

Viewing Participant Properties .......................................... 2-85

Meeting Rooms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Meeting Rooms List ............................................................................... 3-3

Meeting Room Toolbar & Right-click Menu .............................. 3-5

Creating a New Meeting Room ............................................................ 3-6

Entry Queues, Ad Hoc Conferences and SIP Factories . 4-1

Entry Queues ........................................................................................... 4-1

Defining a New Entry Queue ....................................................... 4-4

Listing Entry Queues ..................................................................... 4-8

Modifying the EQ Properties ........................................................ 4-9

Transit Entry Queue ....................................................................... 4-9

iii

Table of Contents

Setting a Transit Entry Queue .............................................. 4-9

Ad Hoc Conferencing .......................................................................... 4-11

Gateway to Polycom® Distributed Media Application™

(DMA™) 7000 ....................................................................................... 4-12

SIP Factories .......................................................................................... 4-13

Creating SIP Factories .................................................................. 4-13

Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Viewing the Address Book ................................................................... 5-2

Displaying and Hiding the Address Book .......................... 5-2

Adding a Participant to the Address Book ......................................... 5-4

Adding a new participant to the Address Book Directly ......... 5-4

Adding a Participant from an Ongoing Conference to the

Address Book ................................................................................ 5-13

Modifying Participants in the Address Book ........................... 5-14

Deleting Participants from the Address Book .......................... 5-15

Searching the Address Book ....................................................... 5-15

Filtering the Address Book ......................................................... 5-16

Participant Groups ............................................................................... 5-18

Adding a New Group to the Address Book ............................. 5-18

Deleting a Group from the Address Book ................................ 5-19

Modifying a Group in the Address Book ................................. 5-20

Importing and Exporting Address Books ......................................... 5-21

Exporting an Address Book ........................................................ 5-21

Importing an Address Book ........................................................ 5-22

Integrating the Polycom CMA™ Address Book with the RMX .... 5-23

Reservations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Guidelines ................................................................................................ 6-1

System ...................................................................................... 6-1

Resources ................................................................................. 6-1

Reservations ............................................................................ 6-3

Using the Reservation Calendar .......................................................... 6-4

Toolbar Buttons ....................................................................... 6-5

Reservations Views ........................................................................ 6-5

Week View ............................................................................... 6-6

Day View ................................................................................. 6-6

Today View ............................................................................. 6-6

List View .................................................................................. 6-7

iv

Polycom RMX 2000/4000 Administrator’s Guide

Changing the Calendar View ....................................................... 6-8

Scheduling Conferences Using the Reservation Calendar ............. 6-10

Creating a New Reservation ....................................................... 6-10

Managing Reservations ....................................................................... 6-18

Guidelines ...................................................................................... 6-18

Viewing and Modifying Reservations ....................................... 6-18

Using the Week and Day views of the Reservations

Calendar ................................................................................. 6-18

Deleting Reservations .................................................................. 6-20

Searching for Reservations using Quick Search ...................... 6-21

Operator Assistance & Participant Move . . . . . . . . . . . 7-1

Operator Conferences ............................................................ 7-1

Defining the Components Enabling Operator Assistance ....... 7-3

Defining a Conference IVR Service with Operator

Assistance Options ................................................................. 7-4

Defining an Entry Queue IVR Service with Operator

Assistance Options ................................................................. 7-7

Defining a Conference Profile for an Operator

Conference ............................................................................... 7-9

Defining an Ongoing Operator Conference ..................... 7-16

Saving an Operator Conference to a Template ................ 7-21

Starting an Operator Conference from a Template ......... 7-22

Monitoring Operator Conferences and Participants

Requiring Assistance .................................................................... 7-23

Requesting Help ................................................................... 7-23

Participant Alerts List .......................................................... 7-25

Audible Alarms ............................................................................ 7-25

Using Audible Alarms ......................................................... 7-25

Moving Participants Between Conferences .............................. 7-26

Moving Participants ............................................................. 7-27

Conference Templates . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Guidelines ................................................................................ 8-1

Using Conference Templates ................................................................ 8-3

Toolbar Buttons ....................................................................... 8-4

Creating a New Conference Template ................................................ 8-5

Creating a new Conference Template from Scratch .................. 8-5

Saving an Ongoing Conference as a Template ........................ 8-12

v

Table of Contents

Saving an Operator Conference to a Template ................ 8-12

Starting an Ongoing Conference From a Template ......................... 8-14

Starting an Operator Conference from a Template ......... 8-15

Scheduling a Reservation From a Conference Template ................ 8-16

Deleting a Conference Template ........................................................ 8-18

Conference and Participant Monitoring . . . . . . . . . . . . 9-1

General Monitoring ................................................................................ 9-2

Conference Level Monitoring ............................................................... 9-3

Monitoring Operator Conferences and Participants

Requiring Assistance .................................................................... 9-11

Requesting Help ................................................................... 9-11

Participant Alerts List .......................................................... 9-13

Participant Level Monitoring ............................................................. 9-14

IP Participant Properties ..................................................... 9-15

Monitoring ISDN/PSTN Participants ............................... 9-25

Recording Conferences . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Configuring the RMX to enable Recording .............................. 10-1

Defining the Recording Link .............................................. 10-1

Enabling the Recording Features in a Conference IVR

Service .................................................................................... 10-3

Enabling the Recording in the Conference Profile .......... 10-4

Recording Link Encryption ................................................. 10-5

Managing the Recording Process ............................................... 10-8

Using the RMX Web Client to Manage the Recording

Process .................................................................................... 10-8

Using DTMF Codes to Manage the Recording Process 10-10

Conference Recording with Codian IP VCR .................................. 10-11

Users, Connections and Notes . . . . . . . . . . . . . . . . . . 11-1

Listing Users .................................................................................. 11-2

Adding a New User ..................................................................... 11-3

Deleting a User ............................................................................. 11-4

Changing a User’s Password ...................................................... 11-5

Disabling a User ............................................................................ 11-6

Enabling a User ............................................................................. 11-7

Renaming a User .......................................................................... 11-7

Connections ........................................................................................... 11-9

Viewing the Connections List ..................................................... 11-9

vi

Polycom RMX 2000/4000 Administrator’s Guide

User and Connection Management in Enhanced Security Mode 11-10

Managing the RMX Users ......................................................... 11-11

User Types ........................................................................... 11-11

Disabling/Enabling Users ................................................. 11-11

Renaming Users .................................................................. 11-11

Disabling Inactive Users .................................................... 11-11

Managing the User Login Process ........................................... 11-12

Implementing Strong Passwords ..................................... 11-12

Implementing Password Re-Use / History Rules ......... 11-13

Defining Password Aging ................................................. 11-14

Defining Password Change Frequency ........................... 11-14

Forcing Password Change ................................................. 11-15

Temporary User Lockout .................................................. 11-15

User Lockout ....................................................................... 11-15

User Login Record .............................................................. 11-16

Controlling RMX User Sessions ............................................... 11-17

Management Sessions per System ................................... 11-17

Sessions per User ................................................................ 11-17

Connection Timeout ........................................................... 11-17

Session Timeout .................................................................. 11-18

Erase Session History After Logout ................................. 11-18

Notes .................................................................................................... 11-19

Using Notes ................................................................................. 11-19

Network Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

IP Network Services ............................................................................. 12-2

Management Network (Primary) ............................................... 12-2

Default IP Service (Conferencing Service) ................................ 12-3

Modifying the Management Network ...................................... 12-3

Modifying the Default IP Network Service ............................ 12-13

Ethernet Settings (RMX 4000 Only) ......................................... 12-29

IP Network Monitoring ............................................................. 12-31

Using IPv6 Networking Addresses for RMX Internal and

External Entities .......................................................................... 12-36

RMX Internal Addresses ................................................... 12-36

External Entities .................................................................. 12-36

IPv6 Guidelines ........................................................................... 12-36

Network Security ................................................................................ 12-38

vii

Table of Contents

Network Separation ................................................................... 12-38

RMX 4000 ............................................................................. 12-38

RMX 2000 ............................................................................. 12-39

Enabling Network Separation .......................................... 12-39

ISDN/PSTN Network Services ........................................................ 12-43

Adding/Modifying ISDN/PSTN Network Services ............ 12-44

Obtaining ISDN/PSTN required information ............... 12-44

Modifying an ISDN/PSTN Network Service ......................... 12-53

IVR Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

IVR Services List ................................................................................... 13-2

IVR Services Toolbar .................................................................... 13-3

Adding Languages ............................................................................... 13-4

Defining a New Conference IVR Service .......................................... 13-9

Defining a New Conference IVR Service .................................. 13-9

Entry Queues IVR Service ................................................................. 13-27

Defining a New Entry Queue IVR Service ............................. 13-27

Setting a Conference IVR Service or Entry Queue IVR

Service as the Default Service ................................................... 13-32

Modifying the Conference or Entry Queue IVR Service

Properties ..................................................................................... 13-33

Replacing the Music File ................................................................... 13-34

Adding a Music File ........................................................... 13-34

Creating Audio Prompts and Video Slides .................................... 13-36

Recording an Audio Message ................................................... 13-36

Creating a Welcome Video Slide .............................................. 13-40

Default IVR Prompts and Messages ................................................ 13-41

Volume Control of IVR Messages, Music and Roll Call ............... 13-45

The Call Detail Record (CDR) Utility . . . . . . . . . . . . . . 14-1

The CDR File ......................................................................................... 14-2

CDR File Formats ......................................................................... 14-2

CDR File Contents ........................................................................ 14-3

Viewing, Retrieving and Archiving Conference Information ....... 14-5

Viewing the Conference Records ............................................... 14-5

Refreshing the CDR List .............................................................. 14-6

Retrieving and Archiving Conference CDR Records .............. 14-7

Gateway Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Call Flows ...................................................................................... 15-1

viii

Polycom RMX 2000/4000 Administrator’s Guide

Direct Dialing ........................................................................ 15-1

Gateway IVR ......................................................................... 15-5

Interoperability with CMA ................................................. 15-8

Connection Indications ................................................................ 15-9

Gateway Functionality ............................................................... 15-10

Configuring the Gateway Components on the RMX ............ 15-12

Defining the IVR Service for Gateway Calls ................... 15-12

Defining the Conference Profile for Gateway Calls ...... 15-16

Defining the Gateway Profile ........................................... 15-17

Displaying the Connection Information - System

Configuration ...................................................................... 15-21

Monitoring Ongoing Gateway Sessions ................................. 15-22

Gateway Session Parameters ............................................ 15-22

Connected Participant Parameters ................................... 15-23

Dialing to Polycom® DMA™ 7000 .................................................. 15-24

Direct Dialing from ISDN/PSTN Endpoint to IP Endpoint via a

Meeting Room ..................................................................................... 15-25

RMX Manager Application . . . . . . . . . . . . . . . . . . . . . 16-1

Installing the RMX Manager ....................................................... 16-1

Starting the RMX Manager Application ................................... 16-5

Connecting to the MCU ............................................................... 16-6

RMX Manager Main Screen ........................................................ 16-9

MCUs Pane .......................................................................... 16-10

Conferences Pane ................................................................ 16-11

RMX Management .............................................................. 16-12

List Pane ............................................................................... 16-13

Status Bar ............................................................................. 16-13

Address Book ...................................................................... 16-14

Conference Templates ........................................................ 16-15

Adding MCUs to the MCUs List .............................................. 16-15

Starting a Conference ................................................................. 16-18

Starting a Conference from the Conferences Pane ........ 16-18

Starting a Reservation ........................................................ 16-20

Starting an Ongoing Conference or Reservation From

a Template ........................................................................... 16-21

Monitoring Conferences ............................................................ 16-22

Grouping the Participants by MCU ................................. 16-23

ix

Table of Contents

Start Monitoring/Stop Monitoring .................................. 16-24

Modifying the MCU Properties ................................................ 16-25

Disconnecting an MCU .............................................................. 16-26

Removing an MCU from the MCUs Pane .............................. 16-26

Changing the RMX Manager Language ................................. 16-27

Installing RMX Manager for Secure Communication Mode 16-28

Using an Internal Certificate Authority .......................... 16-33

RMX Administration and Utilities . . . . . . . . . . . . . . . . 17-1

System and Participant Alerts ............................................................ 17-1

System Alerts ................................................................................ 17-2

Participant Alerts .......................................................................... 17-4

System Configuration .......................................................................... 17-5

Modifying System Flags .............................................................. 17-5

Manually Adding and Deleting System Flags ....................... 17-17

LEGACY_EP_CONTENT_DEFAULT_LAYOUT Flag

Values ........................................................................................... 17-28

JITC_MODE System Flag .......................................................... 17-30

Auto Layout Configuration ...................................................... 17-33

Customizing the Default Auto Layout ............................ 17-33

RMX Time ............................................................................................ 17-37

Altering the clock ....................................................................... 17-37

Resource Management ...................................................................... 17-39

Resource Capacity ...................................................................... 17-39

Resource Capacity Modes ................................................. 17-40

Resource Usage ................................................................... 17-41

Video/Voice Port Configuration ............................................. 17-44

Flexible Resource Capacity Mode .................................... 17-44

Fixed Resource Capacity ................................................... 17-44

Configuring the Video/Voice Resources in MPM

Mode ..................................................................................... 17-45

Configuring the Video/Voice Resources in MPM+

Mode ..................................................................................... 17-46

Flexible Resource Capacity ............................................... 17-46

Forcing Video Resource Allocation to CIF Resolution . 17-50

Resource Report .......................................................................... 17-52

Displaying the Resource Report ....................................... 17-52

x

Polycom RMX 2000/4000 Administrator’s Guide

Resource Report Display in Flexible Resource

Capacity Mode™ ................................................................ 17-53

Resource Report in Fixed Resource Capacity Mode™ . 17-55

ISDN/PSTN ........................................................................ 17-56

Port Usage .................................................................................... 17-57

Setting the Port Usage Threshold ..................................... 17-57

Port Usage Gauges ............................................................. 17-59

Port Gauges in Flexible/Fixed Capacity Modes ............ 17-60

System Information ............................................................................ 17-61

SNMP (Simple Network Management Protocol) .......................... 17-64

Detailed Description .................................................................. 17-64

MIB (Management Information Base) Files ............................ 17-64

Private MIBS ........................................................................ 17-64

Support for MIB-II Sections .............................................. 17-65

The Alarm-MIB ................................................................... 17-65

H.341-MIB (H.341 – H.323) ............................................... 17-65

Standard MIBs ..................................................................... 17-65

Traps ............................................................................................. 17-67

Status Trap Content ............................................................ 17-68

Defining the SNMP Parameters in the RMX .......................... 17-69

Audible Alarms .................................................................................. 17-75

Using Audible Alarms ............................................................... 17-75

Audible Alarm Permissions .............................................. 17-75

Stop Repeating Message .................................................... 17-76

Configuring the Audible Alarms ............................................. 17-76

User Customization ............................................................ 17-76

Replacing the Audible Alarm File .................................... 17-78

Multilingual Setting ........................................................................... 17-80

Customizing the Multilingual Setting ..................................... 17-80

Banner Display and Customization ................................................. 17-81

Customizing Banners ................................................................. 17-81

Banner Display ............................................................................ 17-82

Login Screen Banner .......................................................... 17-82

Main Screen Banner ............................................................ 17-84

Software Management ....................................................................... 17-85

Backup and Restore Guidelines ............................................... 17-85

Using Software Management ........................................... 17-86

xi

Table of Contents

Ping RMX ............................................................................................. 17-88

Guidelines .................................................................................... 17-88

Using Ping ................................................................................... 17-88

Notification Settings ........................................................................... 17-90

Logger Diagnostic Files ..................................................................... 17-92

Auditor ................................................................................................. 17-95

Auditor Files ................................................................................ 17-95

Auditor Event History File Storage ................................. 17-95

Retrieving Auditor Files .................................................... 17-96

Auditor File Viewer ................................................................... 17-98

Audit Events .............................................................................. 17-101

Alerts and Faults ............................................................... 17-101

Transactions ...................................................................... 17-103

ActiveX Bypass ................................................................................. 17-105

Installing ActiveX ..................................................................... 17-105

Resetting the RMX ............................................................................ 17-107

RMX Hardware Monitoring . . . . . . . . . . . . . . . . . . . . . 18-1

Viewing the Status of the Hardware Components ......................... 18-1

HW Monitor Pane Toolbar .................................................. 18-3

Viewing Hardware RMX 2000 Component’s Properties ................ 18-4

Viewing Hardware RMX 4000 Component’s Properties .............. 18-13

Diagnostic Mode ................................................................................. 18-22

Performing Diagnostics ............................................................. 18-23

Diagnostics Monitoring ............................................................. 18-26

MCU Monitor ...................................................................... 18-26

Cards Monitor ..................................................................... 18-27

Error Buffer .......................................................................... 18-28

Disconnection Causes . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

IP Disconnection Causes. .....................................................................A-1

ISDN Disconnection Causes .............................................................. A-10

Alarms and Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Alarms ..............................................................................................B-1

CDR Fields - Unformatted File . . . . . . . . . . . . . . . . . . . . C-1

The Conference Summary Record .......................................................C-3

Event Records .........................................................................................C-5

Standard Event Record Fields ......................................................C-5

Event Types .....................................................................................C-6

xii

Polycom RMX 2000/4000 Administrator’s Guide

Event Specific Fields ................................................................... C-16

Disconnection Cause Values .............................................................. C-55

MGC Manager Events that are not Supported by the RMX 2000 C-59

Ad Hoc Conferencing and External Database

Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Ad Hoc Conferencing without Authentication ................................ D-2

Ad Hoc Conferencing with Authentication ......................................D-3

Entry Queue Level - Conference Initiation Validation with

an External Database Application ............................................... D-4

Conference Access with External Database Authentication ........... D-6

Conference Access Validation - All Participants (Always) .....D-7

Conference Access Validation - Chairperson Only (Upon

Request) ..........................................................................................D-9

System Settings for Ad Hoc Conferencing and External Database

Authentication ..................................................................................... D-11

Ad Hoc Settings ...........................................................................D-11

Authentication Settings ..............................................................D-11

MCU Configuration to Communicate with an External

Database Application .......................................................... D-13

Enabling External Database Validation for Starting New

Ongoing Conferences .......................................................... D-15

Enabling External Database Validation for Conferences

Access ....................................................................................D-16

Participant Properties Advanced Channel Information E-1

Secure Communication Mode . . . . . . . . . . . . . . . . . . . . F-1

Switching to Secure Mode ............................................................. F-1

Purchasing a Certificate .........................................................F-1

Installing the Certificate ........................................................ F-3

Creating/Modifying System Flags ......................................F-5

Enabling Secure Communication Mode ..................................... F-5

Alternate Management Network .........................................F-6

Securing an External Database ..................................................... F-7

Configuring Direct Connections to RMX . . . . . . . . . . . . G-1

Management Network (Primary) ........................................................ G-1

Alternate Management Network ........................................................ G-1

Configuring the Workstation ....................................................... G-2

Connecting to the Management Network ................................. G-7

xiii

Table of Contents

Connecting to the Alternate Management Network ................ G-9

Connecting to the RMX via Modem ......................................... G-10

Procedure 1: Install the RMX Manager ............................ G-10

Procedure 2: Configure the Modem ................................. G-10

Procedure 3: Create a Dial-up Connection ...................... G-11

Procedure 4: Connect to the RMX ..................................... G-16

Setting the RMX for Integration Into Microsoft OCS

Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H-1

Configuring the OCS for RMX 2000/4000 ......................................... H-2

Setting the Trusted Host and Static Route for RMX in the

OCS .................................................................................................. H-2

Creating the Security (TLS) Certificate in the OCS and

Exporting the Certificate to the RMX Workstation ................. H-7

Retrieving the Certificate from the OCS to the RMX

Workstation ..........................................................................H-13

Optional. Creating the Certificate Password File

(certPassword.txt) ................................................................H-16

Optional. Setting the Static Route & Trusted Host for RMX in the

Load Balancer Server ..........................................................................H-17

Configuring the RMX 2000/4000 for Microsoft OCS 2007

Integration ............................................................................................H-19

Modify the RMX Management Network Service to Include

the DNS Server ............................................................................H-19

Defining a SIP Network Service in the RMX ...........................H-21

Polycom RMX System Flag Configuration ..............................H-25

Dialing to an Entry Queue, Meeting Room or Conference ...H-28

Active Alarms and Troubleshooting ................................................H-29

Active Alarms ..............................................................................H-29

Troubleshooting ...........................................................................H-31

Known Issues ...............................................................................H-31

xiv

Conference Profiles

Profiles stored on the MCU enable you to define all types of conferences.
Profiles include conference parameters such as Bit Rate, Video Layout,
Encryption, etc.

A maximum of 40 (RMX 2000) or 80 (RMX 4000) Conference Profiles can be
defined.

Conference Profiles are saved to Conference Templates along with all
participant parameters, including their Personal Layout and Video Forcing
settings, enabling administrators and operators to create, save, schedule
and activate identical conferences. For more information see Chapter 8,
“Conference Templates” .

The RMX is shipped with a default Conference Profile which allows users to
immediately start standard ongoing conferences. Its settings are as
follows:

Table 1-1 Default Conference Profile Settings

1

Setting Value

Profile Name Factory Video Profile
Bit Rate 384Kbps
H.239 Settings Graphics
High Definition Video

Switching
Operator Conference Disabled
Encryption Disabled
LPR Enabled for CP Conferences

Disabled

1-1

Chapter 1-Conference Profiles

Table 1-1 Defau lt Conference Profile Settings (Continued)

Setting Value

Auto Terminate

• After la st participant quits - Enabled

• When last participant remains - Disabled

Echo Suppression Enabled
Keyboard Noise Suppression Disabled
Video Quality Sharpness
Video Clarity™ Enabled
Content Video Definition

• Content Settings: Graphics

• Content Protocol: Up to H.264

Send Content to Legacy
Endpoints

Layout Auto Layout - Enabled

Skin Polycom
IVR Name Conference IVR Service

Enabled

Same Layout - Disabled

This Profile is automatically assigned to the following conferencing
entities:

1-2

Name ID

Meeting Rooms

Maple_Room 1001
Oak_Room 1002
Juniper_Room 1003
Fig_Room 1004

Entry Queue

Default EQ 1000

Conferencing Modes

Standard Conferencing

When defining a new video Profile, you select the parameters that
determine the video display on the participant’s endpoint and the quality
of the video. When defining a new conference Profile, the system uses
default values for standard conferencing. Standard conferencing enable
several participants to be viewed simultaneously and each connected
endpoint uses its highest video, audio and data capabilities up to the
maximum bit rate set for the conference.

The main parameters that define the quality of a video conference are:

• Bit Rate - The transfer rate of video and audio streams. The higher

the bit rate, the better the video quality.

• Audio Algorithm - The audio compression algorithm determines the

quality of the conference audio.

• Video protocol, video format, frame rate, annexes, and interlaced

video mode - These parameters define the quality of the video
images. The RMX will send video at the best possible resolution
supported by endpoints regardless of the resolution received from
the endpoints.

— When Sharpness is selected as the Video Quality setting in the

conference Profile, the RMX will send 4CIF (H.263) at 15fps

instead of CIF (H.264) at 30fps.

— H.264 protocol provides better compression of video images in

bit rates lower than 384 Kbps and it will be automatically

selected for the endpoint if it supports H.264.

— When working with RMXs at low bit rates (128, 256, or 384Kbps),

HDX endpoints will transmit SD15 resolution instead of 2CIF

resolution.

When using 1x1 conference layout, the RMX transmits the same
resolution it receives from the endpoint.

• Lost Packet Recovery (LPR) - LPR creates additional packets that

contain recovery information used to reconstruct packets that are lost
during transmission.

Polycom RMX 2000/4000 Administrator’s Guide

1-3

Chapter 1-Conference Profiles

• Video Clarity - Video Clarity feature applies video enhancing

• Supported resolutions:

algorithms to incoming video streams of resolutions up to and
including SD.

— H.261 CIF/QCIF – Is supported in Continuous Presence (CP)

conferences at resolutions of 288 x 352 pixels (CIF) and
144 x 176 pixels (QCIF). Both resolutions are supported at frame
rates of up to 30 frames per second.

— H.263 4CIF - A high video resolution available to H.263

endpoints that are not H.264 enabled. It is only supported for
conferences in which the video quality is set to sharpness and for
lines rates of 384kbps to 1920kbps.

— Standard Definition (SD) - A high quality video protocol which

uses the H.264 video algorithm. It enables HD compliant
endpoints to connect to Continuous Presence conferences at
resolutions of 720X576 pixels for PAL systems and 720X480
pixels for NTSC systems. Bit rates for SD range from 256Kbps to
2Mbps. For more information, see "Video Resolutions in CP” on
page 2-3.

— High Definition (HD) – HD is an ultra-high quality video

resolution. Depending on the RMX’s Card Configuration mode,
compliant endpoints are able to connect to conferences at
resolutions ranging from 720p (1280 x 720 pixels) to 1080p (1920
x 1080 pixels) (in MPM+ Mode) at bit rates ranging from 1024
Kbps to 4 Mbps (6 Mbps with HD VSW). For more information,
see "Video Resolutions in CP” on page 2-3.

— Operator Conferences - Offers additional conference

management capabilities to the RMX users, enabling them to
attend to participants with special requirements and acquire
participant details for billing and statistics. This service is
designed usually for large conferences that require the personal
touch. Operator assistance is available in both MPM and MPM+
Card Configuration Modes. For more information, see Chapter 7,
“Operator Assistance & Participant Move” on page 7-1.

1-4

Supplemental Conferencing Features

In addition to Standard Conferencing the following features can be enabled:

• H.239 – Allows compliant endpoints to transmit and receive two

simultaneous streams of conference data to enable Content sharing.
H.239 is also supported in cascading conferences. Both H.263 and
H.264 Content sharing protocols are supported. If all endpoints
connected to the conference have H.264 capability, Content is shared
using H.264, otherwise Content is shared using H.263.

For more information, see "H.239” on page 2-12.

• Lecture Mode – The lecturer is seen by all participants in full screen

while the lecturer views all conference participants in the selected
video layout.

For more information, see "Lecture Mode” on page 2-23.

• Presentation Mode – When the current speaker’s speech exceeds a

predefined time (30 seconds), the conference layout automatically
changes to full screen, displaying the current speaker as the
conference lecturer on all the participants’ endpoints. During this
time the speaker’s endpoint displays the previous conference layout.
When another participant starts talking, the Presentation Mode is
cancelled and the conference returns to its predefined video layout.
Presentation mode is available with Auto Layout and Same Layout.

— If the speaker in a video conference is an Audio Only participant,

the Presentation Mode is disabled for that participant.

— Video forcing works in the same way as in Lecture Mode when

Presentation Mode is activated, that is, forcing is only enabled at

the conference level, and it only applies to the video layout

viewed by the lecturer.

• Telepresence Mode - enables the connection of numerous high

definition telepresence rooms and of different models (such as TPX
and RPX) into one conference maintaining the telepresence
experience. This mode is enabled by a special license.

• Encryption – Used to enhance media security at conference and

participant levels. For more information, see "Media Encryption” on
page 2-30.

• Conference Recording - The RMX enables audio and video recording

of conferences using Polycom RSS 2000 recording system.

Polycom RMX 2000/4000 Administrator’s Guide

1-5

Chapter 1-Conference Profiles

Profile Toolbar

Profile List

Viewing Profiles

Conference Profiles are listed in the Conference Profiles list pane.

To list Conference Profiles:

1 In the RMX Management pane, expand the Rarely Used list.

2 Click the Conference Profiles button.

The Conference Profiles are displayed in the List pane.

1-6

The following Conference Profile properties are displayed in the List
pane:

Table 1-2 Conference Profiles Pane Columns

Field Description

Name The name of the Conference Profile.
Layout Displays either “Auto Layout” or an icon of the

layout selected for the profile.
For information about video layouts, see Ta ble 1-9

"Video Layout Options” on page 1-19.

Profile Toolbar

The Profile toolbar provides quick access to the Profile functions:

Table 1-3 Profile Toolbar buttons

Polycom RMX 2000/4000 Administrator’s Guide

Table 1-2 Conference Profiles Pane Columns (Continued)

Field Description

Line Rate The maximum bit rate at which endpoints can

connect to the conference.

Routing Name Displays the Routing Name defined by the user or

automatically generated by the system.

Encryption Displays if media encryption is enabled for the

Profile (Yes). For more information about
encryption, see "Media Encryption” on page 2-30.

Button

Button
Name

New Profile To create a new Profile.

Delete Profile To delete a profile, click the Profile name and

Descriptions

then click this button.

1-7

Chapter 1-Conference Profiles

Defining Profiles

Profiles are the basis for the definition of all ongoing conferences,
Reservations, Meeting Rooms, Entry Queues, and Conference Templates
and they contain only conference properties.

To define a new Profile:

1 In the RMX Management pane, click Conference Profiles.

2 In the Conference Profiles pane, click the New Profile button.

The New Profile – General dialog box opens.

1-8

The RMX displays the default settings, so you need only define the
Profile name.

Polycom RMX 2000/4000 Administrator’s Guide

3 Define the Profile name and, if required, the Profile general

parameters:

Table 1-4 New Profile - General Parameters

Field/Option Description

Display Name Enter a unique Profile name, as follows:

•

English text uses ASCII encoding and can contain
the most characters (length varies according to the
field).

• European and Latin text length is approximately

half the length of the maximum.

• Asian text length is approximately one third of the

length of the maximum.

It is recommended to use a name that indicates the
Profile type, such as Operator conference or Video
Switching conference.

Note: This is the only parameter that must be defined
when creating a new profile.

Routing Name Enter the Profile name using ASCII characters set.

The Routing Name can be defined by the user or
automatically generated by the system if no Routing
Name is entered as follows:

• If an all ASCII text is entered in 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 Display Name, the
ID (such as Conference ID) is used as the Routing
Name.

Line Rate Select the conference bit rate. The line rate

the combined video, audio and Content rate
The default setting is 384 Kbps.

represents
.

1-9

Chapter 1-Conference Profiles

Table 1-4 New Profile - General Parameters (Continued)

Field/Option Description

High Definition
Video Switching

Operator
Conference

If the Operator Conference option is selected, this
option is disabled, and the selection is cleared.
When selected, the conference is ultra-high quality
video resolution, in a special conferencing mode which
implies that all participants must connect at the same
line rate and use HD video and all participants with
endpoints not supporting HD will connect as
secondary (audio only).
For more information, see "High Definition Video
Switching” on page 2-8.
Select the High Definition resolution; select either
HD 720p or HD 1080p (in MPM+ mode only).
If HD 1080p is selected, endpoints that do not support
HD 1080p resolution are connected as Secondary
(Audio Only) participants.
Notes:

• High Definition Video Switching conferencing mode

is unavailable to ISDN participants.

Select this option to define the profile of an Operator
conference.

An Operator conference can only be a Continuous
Presence conference, therefore when selected, the
High Definition Video Switching option is disabled and
cleared.

When defining an Operator Conference, the Send

Content to Legacy Endpoints option in the Video
Settings tab is cleared and disabled.
For more information, see Chapter 7, “Operator
Assistance & Participant Move” on page 7-1.

1-10

4 Click the Advanced tab.

Polycom RMX 2000/4000 Administrator’s Guide

The New Profile – Advanced dialog box opens.

5 Define the following parameters:

Table 1-5 New Profile - Advanced Parameters

Field/Option Description

Encryption Select this check box to activate encryption for the

conference. For more information, see RMX 2000
Administrator’s Guide, "Media Encryption” on
page 2-30.

LPR When selected (default for CP conferences), Lost

Packet Recovery creates additional packets that

contain recovery information used to reconstruct
packets that are lost during transmission.

LPR check box is automatically cleared if High
Definition Video Switching is selected, but can be
selected if required. For more information, see RMX

2000 Administrator’s Guide, "LPR – Lost Packet
Recovery” on page 2-38.

1-11

Chapter 1-Conference Profiles

Table 1-5 New Profile - Advanced Parameters (Continued)

Field/Option Description

Auto Terminate When selected (default), the conference automatically

ends when the termination conditions are met:
Before First Joins — No participant has connected to

a conference during the n minutes after it started.
Default idle time is 10 minutes.

At the End - After Last Quits — All the participants
have disconnected from the conference and the
conference is idle (empty) for the predefined time
period. Default idle time is 1 minute.
At the End - When Last Participant Remains —
Only one participant is still connected to the
conference for the predefined time period (excluding
the recording link which is not considered a participant
when this option is selected). This option should be
selected when defining a Profile that will be used for
Gateway Calls and you want to ensure that the call is
automatically terminated when only one participant is
connected. Default idle time is 1 minute.
Note: The selection of this option is automatically
cleared and disabled when the Operator Conference
option is selected. The Operator conference cannot
automatically end unless it is terminated by the RMX
User.

1-12

Echo
Suppression

When enabled (default), an algorithm is used to search
for and detect echo outside the normal range of human
speech (such as echo) and automatically mute them
when detected.
Clear this option to disable the Echo Suppression
algorithm.

Notes:

• This option is activated only in MPM+ Card

Configuration Mode.

• The CMA uses the Profiles that are stored in the

RMX. When the Echo Suppression is enabled, it
will be enabled in the conference that is started
from the CMA with that Profile. However, the CMA
does not display an indication that this option is
enabled for the conference.

Polycom RMX 2000/4000 Administrator’s Guide

Table 1-5 New Profile - Advanced Parameters (Continued)

Field/Option Description

Keyboard Noise
Suppression

Select this option to let the system use an algorithm to
search for and detect keyboard noises and
automatically mute them when detected.

Notes:

• This option is activated only in MPM+ Card

Configuration Mode.

• The CMA uses the Profiles that are stored in the

RMX. When the Keyboard Noise Suppression is
enabled, it will be enabled in the conference that is
started from the CMA with that Profile. However,
the CMA does not display an indication that this
option is enabled for the conference.

6 Click the Video Quality tab.

The New Profile – Video Quality dialog box opens.

1-13

Chapter 1-Conference Profiles

7 Define the following parameters:

Table 1-6 New Profile - Video Quality Parameters

Field/Option Description

People Video Definition

Video Quality Depending on the amount of movement contained in

the conference video, select either:

• Motion – for a higher frame rate without increased

resolution. When selected, Video Clarity is
disabled.

• Sharpness – for higher video resolution and

requires more system resources.

Note: When Sharpness is selected as the Video
Quality setting in the conference Profile, the RMX will

send 4CIF (H.263) at 15fps instead of CIF (H.264) at
30fps. For more information, see RMX 2000
Administrator’s Guide, "Video Resolutions in CP” on
page 2-3.

Video Clarity™ When enabled (default), Video Clarity applies video

enhancing algorithms to incoming video streams of
resolutions up to and including SD. Clearer images
with sharper edges and higher contrast are sent back
to all endpoints at the highest possible resolution
supported by each endpoint.

All layouts, including 1x1, are supported.
Note: Video Clarity is enabled only when Video Quality

is set to Sharpness (default setting) and is disabled
when Video Quality is set to Motion.

Video Clarity can only be enabled for Continuous
Presence conferences in MPM+ Card Configuration
Mode.

1-14

Polycom RMX 2000/4000 Administrator’s Guide

Table 1-6 New Profile - Video Quality Parameters (Continued)

Field/Option Description

Content Video Definition

Content Settings Select the transmission mode for the Content channel:

• 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

Selection of a higher bit rate for the Content results in
a lower bit rate for the people channel.

For more information, see RMX 2000 Administrator’s

Guide, "H.239” on page 2-12.

Content Protocol H.263 – Content is shared using H.263 even if some

endpoints have H.264 capability.

Up to H.264 – H.264 is the default Content sharing
algorithm.

When selected:

• Content is shared using H.264 if all endpoints have

H.264 capability.

• Content is shared using H.263 if all endpoints do

not have H.264 capability.

• Endpoints that do not have at least H.263 capability

can connect to the conference but cannot share
Content.

1-15

Chapter 1-Conference Profiles

8 Click the Video Settings tab.

The New Profile - Video Settings dialog box opens.

1-16

9 Define the video display mode and layout using the following

parameters:

Table 1-7 Profile Properties - Video Settings

Field/Option Description

Presentation
Mode

Select this option to activate the Presentation Mode.
In this mode, when the current speaker speaks for a
predefined time (30 seconds), the conference changes
to Lecture Mode. When another participant starts
talking, the Presentation Mode is cancelled and the
conference returns to the previous video layout.

Polycom RMX 2000/4000 Administrator’s Guide

Table 1-7 Profile Properties - Video Settings (Continued)

Field/Option Description

Lecture View
Switching

Send Content to
Legacy
Endpoints

Select this option to enable automatic switching of
participants on the Lecturer’s screen when Lecture
Mode is enabled for the conference.
The automatic switching is enabled when the number
of participants exceeds the number of video windows
displayed on the Lecturer’s screen.

Note: Lecture Mode is enabled in the Conference
Properties – Participants tab. For more information,

see "Lecture Mode” on page 2-23.
When enabled (default), Content can be sent to H.323/

SIP/ISDN endpoints that do not support H.239 Content
(legacy endpoints) over the video (people) channel.
For more details, see Chapter 2, “Sending Content to

Legacy Endpoints” on page 2-16.

Notes:

• This option is enabled only in MPM+ Card

Configuration Mode and Resource Allocation Mode
is set to Flexible Mode.

• This option is valid when sending Content as a

separate stream is enabled in the System
Configuration and the flag: ENABLE_H239 is set to

YES.

• If High Definition Video Switching option is selected

in the Conference Profile - General tab, the Send
Content to Legacy Endpoints selection is cleared

and the option is disabled.

• If the Same Layout option is selected, the Send

Content to Legacy Endpoints selection is cleared

and is disabled.

Same Layout Select this option to force the selected layout on all

participants in a conference. Displays the same video
stream to all participants and personal selection of the
video layout is disabled. In addition, if participants are
forced to a video layout window, they can see
themselves.

1-17

Chapter 1-Conference Profiles

Table 1-7 Profile Properties - Video Settings (Continued)

Field/Option Description

Auto Layout When selected (default), 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.

For more information, see Table 1-8 "Auto Layout –
Default Layouts” on page 1-18.

Clear this selection to manually select a layout for the
conference.

The default Auto Layout settings can be customized by
modifying default Auto Layout system flags in the
System Configuration file. For more information see,
"Auto Layout Configuration” on page 16-33.

Telepresence
Mode

Select this option to enable the Telepresence Mode in
the Conference.

Notes:

• This field is enabled only if the RMX system is

licensed for Telepresence Mode.

• If the Auto Layout option is selected, the

Telepresence Mode option is disabled.

Table 1-8 Auto Layout – Default Layouts

Number of Video Participants Auto Layout Default Settings

0–2

3

4–5

6–7

1-18

Polycom RMX 2000/4000 Administrator’s Guide

Table 1-8 Auto Layout – Default Layouts (Continued)

Number of Video Participants Auto Layout Default Settings

8+

The RMX supports the VUI addition to the H.264 protocol for endpoints that
transmit wide video (16:9) in standard 4SIF resolution.

10 To select the Video Layout for the conference, click the required

number of windows from the layouts bar and then select the
windows array.

The selected layout appears in the Video Layout pane.

Table 1-9 Video Layout Options

Number of
Video Windows

1

2

3

4

5+

9

10+

Available Video Layout s

1-19

Chapter 1-Conference Profiles

In Classic View (for the first two skin
options) the frames fill the screen with
their borders touching

When there is a change of speaker in a Continuous Presence conference, the
transition is set by default to fade in the current speaker while fading out the
previous speaker.

To make this transition visually pleasant, fading in the current speaker while
fading out the previous speaker is done over a period of 500 milliseconds.

The Fade In / Fade Out feature can be disabled by adding a new flag to the
System Configuration. The Value of the new flag must be:
FADE_IN_FADE_OUT=NO.

For more information about System Flags, see the RMX 2000 Administrator’s
Guide, Chapter 16, “System Configuration” on page 16-5.

11 Click the Skins tab to modify the background and frames.

The New Profile - Skins dialog box opens.

1-20

Polycom RMX 2000/4000 Administrator’s Guide

12 Select one of the Skin options.

When T e lepresence Mode is enabled, the Skin options are disabled as the
system uses a black background and the frames and speaker indication are
disabled.

13 Click IVR tab.

The New Profile - IVR dialog box opens.

14 If required, set the following parameters:

Table 1-10 Profile Properties - IVR

Field/Option Description

Conference IVR
Service

The default conference IVR Service is selected. You
can select another conference IVR Service if required.

1-21

Chapter 1-Conference Profiles

Table 1-10 Profile Properties - IVR (Continued)

Field/Option Description

Conference
Requires
Chairperson

Select this option to allow the conference to start only
when the chairperson connects to the conference and
to automatically terminate the conference when the
chairperson exits. Participants who connect to the
conference before the chairperson are placed on Hold
and hear background music (and see the Welcome
video slide). Once the conference is activated, the
participants are automatically connected to the
conference.
When the check box is cleared, the conference starts
when the first participant connects to it and ends at the
predefined time or according to the Auto Terminate
rules when enabled.

15 Optional. Click the Recording tab to enable conference recording

with Polycom RSS 2000.

16 Select the Enable Recording check box.

1-22

17 Define the following parameters:

Table 1-11 Profile Properties - Recording Parameters

Parameter Description

Start Recording Select one of the following:

Audio Only Select this option to record only the audio channel of

18 Click OK to complete the Profile definition.

A new Profile is created and added to the Conference Profiles list.

Modifying an Existing Profile

Polycom RMX 2000/4000 Administrator’s Guide

• Immediately – conference recording is

automatically started upon connection of the first
participant.

• Upon Request – the operator or chairperson

must initiate the recording (manual).

the conference.

You can modify any of the Profile’s parameters but you cannot rename
the Profile.

To modify the Profile Properties:

1 In the Conference Profiles list, double -click the Profile icon or right-

click the Profile icon, and then click Profile Properties.

The Profile Properties - General dialog box opens.

1-23

Chapter 1-Conference Profiles

Deleting a Conference Profile

To delete a Conference Profile:

1 In the Conference Profiles list, select the Conference Profile you want to

delete.

2 Click the Delete Profile

() button.

or
Right-click the Conference Profile to be deleted and select
Delete Profile from the drop-down menu.

A confirmation dialog box is displayed.

3 Click OK in the confirmation dialog box.

4 The Conference Profile is deleted.

A Conference Profile cannot be deleted if it is being used by any conferencing
entities such as Ongoing conferences, Meeting Rooms, Entry Queues, SIP
Factories and Reservations.

1-24

Additional Conferencing Information

Various conferencing modes and video features require additional
settings, such as system flag settings, conference parameters and other
settings. In depth explanations of these additional settings are described
in the following sections.

The RMX 2000 can function with two types of video Media Processing
Modules (MPM): MPM and MPM+. These cards differ in their port
capacity and their support of video resolutions. In addition to all video
modes and features supported by MPM cards, MPM+ cards support
additional video resolutions and video quality enhancement such as
Video Clarity™ .

The RMX 4000 contains only MPM+ cards.

2

Video Session Modes

The RMX offers two video session modes: Continuous Presence and High
Definition Video Switching. The video session type determines the video
display options (full screen or split screen with all participants viewed
simultaneously) and the method in which the video is processed by the
MCU (with or without using the MCU’s video resources).

Dynamic Continuous Presence (CP) Mode

The Continuous Presence mode offers 24 layouts to accommodate
different numbers of participants and conference settings including
support of the VUI annex to the H.264 protocol for endpoints that
transmit wide video instead of 4CIF resolution.

2-1

Chapter 2-Additional Conferencing Information

For conferences with more participants than display squares, the RMX
dynamic video mix capability allows the viewed sites to be modified
throughout the conference. The displayed layout can be changed during
an ongoing conference, allowing a participant to view different screen
layouts of the other conference participants. These layout options allow
conferences to have greater flexibility when displaying a large number of
participants and maximizes the screen’s effectiveness.

High Definition Video Switching Mode

In Video Switching mode all participants see the same video picture (full
screen) and use only one CIF video resource for each connection. The
current speaker is displayed in full screen on all the participants'
endpoints, while the speaker sees the previous speaker. Switching
between participants is voice-activated; whenever a participant starts to
speak, he or she becomes the conference speaker and is viewed on all
screens. All conference participants must use the same line rate and video
parameters such as video protocol, frame rate, annexes and interlaced
video mode as no video processing is performed.

High Definition Video Switching is an ultra-high quality video resolution
enabling compliant endpoints to connect to conferences at resolutions
of 1280x720 pixels (720p) and at line rates ranging from 384kbp to 4Mbps
(with MPM) and 1920 x 1080 pixels (1080p) at line rates ranging from
384kbp to 6Mbps (with MPM+).

HD Video Switching uses less system resources. The maximum
conference size is 160 (RMX 2000) 1080p HD video participants at
2048Kbps, or 80 (RMX 2000) or 160 (RMX 4000) 1080p HD video
participants at 4096 Kbps.

Continuous Presence (CP) Conferencing

Video quality in Continuous Presence mode is affected by the conference
line rate (that determines the maximum line rate to be used by the
connecting endpoints), and the video capabilities of the endpoints such as
the video protocol, video resolution and frame rate.

The video protocol selected by the system determines the video
compression standard used by the endpoints. In Continuous Presence
conferences, the system selects the best video protocol for the endpoint
according to its capabilities.

2-2

The following Video protocols are supported:

• H.261 - the video compression algorithm mandatory to all endpoints.

It is used by endpoints that do not support other protocols.

• H.263 - a video compression algorithm that provides a better video

quality than H.261. This standard is not supported by all endpoints.

• H.264 - a video compression standard that offers improved video

quality, especially at line rates lower than 384 Kbps.

Video Resolutions in CP

The RMX always attempts to connect to endpoints at the highest line rate.
If the connection cannot be established, the RMX attempts to connect at
the next highest line rate at its highest supported resolution.

The video resolution is also defined by the Quality settings:

• Motion, when selected, results lower video resolution.

• Sharpness, when selected, sends higher video resolution.

The combination of frame rate and resolution affects the number of video
resources required on the MCU to support the call.

Polycom RMX 2000/4000 Administrator’s Guide

Table 2-1 Video Resolution by Line R at e, Frame Rate & Video Resources

Maximum

Resolution

CIF 128 30 11
2CIF/WCIF 256 30 2.66 2
SD 256 15 2.66 2
SD * 256 30 2.66 4
SD * 1024 60 4 Not Supported
HD720p 1024 30 44
HD720p 1920 60 8 Not Supported
HD1080p 4096 30 8 Not Supported

* SD includes all resolutions above 2CIF (576 x 352 pixels) and below HD (720 x 1280 pixels)..

Minimum

Line Rate Kbps

Maximum

Frame Rate

Video Resources Required

MPM+ MPM

2-3

Chapter 2-Additional Conferencing Information

Additional Video Resolutions in MPM+ Mode

The following higher video quality resolutions are available when the
RMX is working in MPM+ Mode:

• CIF 352 x 288 pixels at 50 fps.

• WCIF 512 x 288 pixels at 50 fps.

• WSD 848 x 480 pixels at 50 fps.

• W4CIF 1024 x 576 pixels at 30 fps.

• HD 720p 1280 x 720 pixels at 60 fps.

• HD 1080p 1920 x 1080 pixels at 30 fps.

The video resolution transmitted to any endpoint is determined by the
endpoint’s capabilities, the conference line rate, the Conference Profile’s

Motion and Sharpness settings and the RMX’s Card Configuration Mode
(MPM or MPM+).

Additional Intermediate Video Resolutions

Two higher quality, intermediate video resolutions replace the
transmission of CIF (352 x 288 pixels) or SIF (352 x 240 pixels) resolutions
to endpoints that have capabilities between:

• CIF (352 x 288 pixels) and 4CIF (704 x 576 pixels) – the resolution
transmitted to these endpoints is 432 x 336 pixels.

• SIF (352 x 240 pixels) and 4SIF (704 x 480 pixels) – the resolution
transmitted to these endpoints is 480 x 352 pixels.

The frame rates (depending on the endpoint’s capability) for both
intermediate resolutions are:

•In MPM Mode – 25 or 30 fps.

•In MPM+ Mode – 50 or 60 fps.

2-4

Polycom RMX 2000/4000 Administrator’s Guide

Video Display with CIF, SD and HD Video Connections

Although any combination of CIF, SD and HD connections is supported
in all CP conferences, the following rules apply:

• In a 1X1 Video Layout:

— SD: If the speaker transmits CIF, the MCU will send CIF to all

participants, including the SD participants. In any other layout
the MCU will transmit to each participant at the participant’s
sending resolution.

— HD: The MCU transmits speaker resolution (including input

from HD participants) at up to SD resolution. If 1x1 is the
requested layout for the entire duration of the conference, set the
conference to HD Video Switching mode.

• In asymmetrical Video Layouts:

— SD: A participant in the large frame that sends CIF is displayed

in CIF.

— HD: Where participants’ video windows are different sizes, the

RMX transmits HD and receives SD or lower resolutions.

• In panoramic Video Layouts:

— SD: Participants that send CIF also receive CIF.
— HD: the RMX transmits HD and receives SD or lower

resolutions, the RMX scales images from SD to HD resolution.

Setting the Maximum CP Resolution for Conferencing

The maximum CP resolution of the system is determined by the

MAX_CP_RESOLUTION system flag. The default setting of the flag is
HD 1080.

The flag values determine the maximum CP capability that each endpoint
can declare:

Table 2-2 System Flag – MAX_CP_RESOLUTION Values

MPM MPM+

Flag Value

Each endpoint can declare capability up to:

HD1080 HD HD1080
HD720 HD HD720

2-5

Chapter 2-Additional Conferencing Information

Table 2-2 System Fla g – MAX_CP_RESOLUTION Values (Continued)

MPM MPM+

Flag Value

Each endpoint can declare capability up to:

HD HD HD720
SD30 SD30 SD30
SD15 SD15 SD30
CIF CIF

For information about setting system flags, see "System Configuration” on
page 16-5.

CP Conferencing with H.263 4CIF

The video resolution of 4CIF in H.263 endpoints is only supported for
conferences in which the video quality is set to sharpness and for line
rates of 384 Kbps to 1920 Kbps as shown in Table 2-3.

2-6

Table 2-3 Video Quality vs. Line Rate

Video Quality

Endpoint
Line Rate
Kbps

Resolution

128 QCIF 30 CIF 30
256 CIF 30 CIF 30

384 - 1920+ CIF 30 4CIF 15

Motion Sharpness

Frame

Rate

Resolution

Frame

Rate

The RMX Web Client supports monitoring of H.263 4CIF information. The
H.245 or SDP tab includes the additional information.

Polycom RMX 2000/4000 Administrator’s Guide

The creation of a new H.263 4CIF slide is supported in the IVR Service in
addition to the current H.263 IVR slide. If users utilize the default
Polycom slides that are delivered with RMX 2000/4000, the slide’s

resolution will be as defined in the profile, i.e. SD, HD, CIF, etc.... If users

create a custom IVR slide, regardless of its resolution, the slide will be
displayed in CIF resolution.

H.263 4CIF Guidelines

• H.263 4CIF is supported with H.323, SIP and ISDN connection

endpoints.

• H.263 4CIF is supported in CP mode only. VSW is supported on the

RMX 2000/4000 in HD only.

• Click & View is supported in H.263 4CIF.

• AES encryption is supported with H.263 4CIF.

• H.263 4CIF is supported in recording by the RSS2000 and other

recording devices.

• All video layouts are supported in H.263 4CIF, except 1x1 layout. In a

1x1 layout, the resolution will be CIF.

• For information about Resource Usage see Table 16-10 on page 16-41.

• H.239 is supported in all 3 resolutions and based on the same

bandwidth decision matrix as for HD.

2-7

Chapter 2-Additional Conferencing Information

High Definition Video Switching

High Definition Video Switching enables compliant endpoints to connect
to conferences at resolutions of 1280x720 pixels (720p) at line rates ranging
from 384kbp to 4Mb and 1920 x 1080 pixels (1080p) at line rates ranging
from 384kbp to 6Mbps (with MPM+). Video display is in full screen mode
only and video is switched to the speaker.

HD Video Switching uses less system resources than HD CP: only one CIF
video resource per participant for HD resolution.

The supported conference size is up to 80 video participants and 120 voice
participants.

High Definition Video Switching conferences require:

• All participants to have HD compliant endpoints.

• All participants to connect using the same conference line rate.

High Definition Video Switching conferencing mode is unavailable to ISDN
participants.

The recommended number of connections at HD1080p resolution in an
RMX 2000 with two MPM+ cards/RMX 4000 with four MPM+ cards is:

Guidelines

2-8

Line Rate/Participants RMX 2000 RMX 4000

2Mbps 160 320
4Mbps 80 160
6Mbps 40 80

• The display aspect ratio is 4x3 or 16x9.

• Site names, skins, etc... are not supported in HD Video Switching.

• Video forcing is enabled at the conference and participant levels.

• Endpoints that do not support HD or are unable to meet these
requirements connect as Secondary (audio only).

Enabling HD Video Switching

For the MCU to run HD Video Switching conferences the following
criteria must be met:

•The HD_THRESHOLD_BITRATE flag must be set in the System

Configuration. The value of this flag is the system minimum threshold
bit rate.

The HD_THRESHOLD_BIT RATE flag is responsible for negotiation only,
It does not guarantee that the endpoint will open an HD channel or transmit on
an opened HD channel.

• The line rate selected in the conference Profile must be the same as or

higher than that specified by the HD_THRESHOLD_BITRATE flag.

•The High Definition Video Switching option must be selected in the

profile. For more information see "Defining Profiles” on page 1-8.

• The RMX must have available resources (ports).

• The endpoints must support HD.

Modifying the HD Video Switching Threshold Bit Rate

Polycom RMX 2000/4000 Administrator’s Guide

To Modify the HD Video Switching Threshold:

1 Click Setup>System Configuration.

The System Flags dialog box opens.

2 Set the HD_THRESHOLD_BITRATE flag to the required line rate

value (range 384kbps to 4Mbs, default is 768 Kbps).

3 Click OK.

The MCU must be reset the MCU for flag changes to take effect.

For more information see "System Configuration” on page 16-5.

Creating a High Definition Video Switching Profile

An HD Video Switching enabled Profile must be created prior to running
HD Video Switching conferences.

High Definition Video Switching conferences, Entry Queues and Meeting
Rooms are created by selecting an HD Video Switching-enabled Profile
and must be set to the same line rate as the target conference.

To connect to an HD Video Switching conference via an Entry Queue, the
Entry Queue must be HD Video Switching enabled. It is recommended to
use the same Profile for both the target conference and Entry Queue.

2-9

Chapter 2-Additional Conferencing Information

To Create an HD Enabled Profile:

1 In the New Profile – General tab, in the Line Rate field, enter a bit rate

that is higher than the defined HD threshold.

2 Select the High Definition Video Switching check box.

2-10

3 Select the resolution for the conference: HD720 or HD1080 (with

MPM+).

4 Click OK.

For more information, see "Defining Profiles” on page 1-8.

Polycom RMX 2000/4000 Administrator’s Guide

HD Conference

Monitoring High Definition Video Switching Conferences

HD conferences appear with the HD ( ) icon in the conferences list to
indicate the currently running HD conference(s).

Monitoring is done in the same way as for standard conferences.

For more information, see "Conference and Participant Monitoring” on
page 9-1.

2-11

Chapter 2-Additional Conferencing Information

H.239

The H.239 protocol allows compliant endpoints to transmit and receive
two simultaneous video streams:

• People Conference – Continuous Presence or Video Switched
conference

• Content Conference – Video Switching conference for content
sharing

By default, all conferences, Entry Queues, and Meeting Rooms launched
on the RMX 2000/RMX 4000 have H.239 capabilities.

To view Content, endpoints must use the same Bit Rate, Protocol, and
Resolution. An endpoint may not send Content while connecting to an
Entry Queue.

Endpoints without H.239 capability can connect to the video conference
without Content.

Cascade links declare H.239 capabilities and they are supported in Star
and MIH cascading topologies. For more details, see "Cascading
Conferences - H.239-enabled MIH Topology” on page 2-61.

Content Transmission Modes

The Content channel can transmit one of the following modes:

• Graphics – default mode, for standard graphics

• Hi-res Graphics – requiring a higher bit rate, for high quality display
or highly detailed graphics

• Live Video – highest bit rate, for video clips or live video display

The highest common Content bit rate is calculated for the conference each
time an endpoint connects. Therefore, if an endpoint connects to an
ongoing conference at a lower bit rate than the current bit rate, the
Content bit rate for the current conference is re-calculated and decreased.

Bit rate allocation by the MCU is dynamic during the conference and
when the Content channel closes, the video bit rate of the People conference
is restored to its maximum.

During a conference the MCU will not permit an endpoint to increase its
bit rate, it can however change its Content resolution. The RMX can
decrease the allocated Content bit rate during a conference.

2-12

Polycom RMX 2000/4000 Administrator’s Guide

The following table shows the bit rate allocated to the Content channel
from the video channel in each of the three Content modes:

Table 2-4 Bit Rate Allocation to Content Channel

Conf
Kbps /
Mode

Graphics 0 64 64 128 128 256 256 256
Hi-res

Graphics
Live

Video

Content Protocol

H.263 Annex T and H.264 protocols are supported for the Content
transmission.

H.264 provides higher video quality at video resolutions of up to HD.

Endpoint Capabilities

• If an endpoint that supports only H.263 for Content Sharing connects

• If an endpoint that does not support H.264 Content sharing

•The H239_FORCE_CAPABILITIES System Flag in system.cfg gives

64/

128 256 384 512 768 1024

96

0 64 128 192 256 384 384 512

0 64 128 256 384 512 768 768

1472/1920/
4096-VSW

to a conference with an Up to H.264 Content sharing Profile:
— H.263 is used for Content if that participant is the first to connect

to the conference

— Content sharing is stopped for all participants if the connection

occurs after Content sharing has started. When Content sharing
is restarted by the user, Content is shared using H.263.

disconnects from a conference with an Up to H.264 Content Sharing
Profile, the Content sharing continues using H.263. This is true even if
all the remaining connected endpoints support H.264. If Content
sharing is stopped and restarted by the user, Content sharing is
automatically upgraded to use H.264.

additional control over Content sharing.

When the flag is set to NO, the RMX only verifies that the endpoint
supports the content protocols: Up to H.264 or H.263.

2-13

Chapter 2-Additional Conferencing Information

When set to YES, the RMX checks frame rate, bit rate, resolution,
annexes and all other parameters of the Content mode as declared by
an endpoint during the capabilities negotiation phase. If the endpoint
does not support the Content capabilities of the MCU the participant
will not be able to send or receive content over a dedicated content
channel. The flag’s default value is NO.

If the System Flag, does not exist in the system, it must be created
using the RMX Menu – Setup option. For more information see the
RMX 2000/4000 Administrator’s Guide, "Modifying System Flags” on
page 16-5.

Entry Queues

• The selection of either H.263 or Up to H.264 in the Entry Queue Profile
does not affect how Content is shared.

• When the endpoint is moved to the conference from the Entry Queue,
the endpoint shares Content according to the guidelines set out under
Endpoint Capabilities and according to the content protocol that is
defined for the target conference.

Cascade Links

Content is shared across a Cascaded Link using H.263 irrespective of
whether either or both the cascade-enabled Entry Queue and the
Cascaded Link have Up to H.264 Content sharing defined in their profiles.

Defining Content Sharing Parameters for a Conference

To define Content Sharing Parameters:

1 In the RMX Management pane, click Conference Profiles.

2 In the Conference Profiles pane, click New Profile.

The New Profile – General dialog box opens.

3 Define the Profile General parameters.

4 Optional. Click the Advanced tab and define additional conference

parameters.

2-14

5 Click the Video Quality tab.

Polycom RMX 2000/4000 Administrator’s Guide

6 In the Content Video Definition section, select the Content Settings and

Protocol as follows:

Table 2-5 H.239 Content Options

Field Description

Content
Settings

Select the transmission mode for the Content channel:

• 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

Selection of a higher bit rate for the Content results in a
lower bit rate for the people channel.

2-15

Chapter 2-Additional Conferencing Information

Table 2-5 H.239 Content Options (Continued)

Field Description

Content
Protocol

H.263 – Content is shared using H.263 even if some
endpoints have H.264 capability.
Up to H.264 – H.264 is the default Content sharing
algorithm.
When selected:

• Content is shared using H.264 if all endpoints have

H.264 capability.

• Content is shared using H.263 if all endpoints do not

have H.264 capability.

• Endpoints that do not have at least H.263 capability

can connect to the conference but cannot share
Content.

7 Click OK.

Sending Content to Legacy Endpoints

The RMX can be configured to send Content to H.323/SIP/ISDN
endpoints that do not support H.239 Content (legacy endpoints) over the

video (people) channel, allowing the participants using the legacy
endpoints to view the Content as the other conference participants.

Guidelines for Sending Content to Legacy Endpoints

• This option is enabled only in MPM+ Card Configuration Mode and
Resource Allocation Mode is set to Flexible Mode.

• This option is valid when sending Content as a separate stream is
enabled in the System Configuration and the flag: ENABLE_H239 is set
to YES.

• One additional SD (3CIF) video resource is allocated to the
conference when Content is sent to legacy endpoints. The allocation
is done only when a legacy endpoint is connected to the conference
and a Content session is initiated and transmitted via the video
channel.
Once the resource is allocated, it remains allocated to the conference
until the conference ends.

2-16

Polycom RMX 2000/4000 Administrator’s Guide

If the system cannot allocate the resource required for sending the
Content, the conference status changes to “Content Resource
Deficiency” and Content will not be sent to the legacy endpoints.

As the resource required for sending Content to legacy endpoints is
allocated on the fly, when scheduling a reservation, in rare occasions
when the MCU is fully loaded, “Resource deficiency” may be
encountered. This may prevent participants from connecting to the
conference or from Content being sent to the legacy endpoint. To
ensure resource for sending Content to legacy endpoints, add one
resource to the number of resources defined in the Reserve Resources
for Video Participants field, in the Conference Properties - General dialog
box.

• Non-H.239 (legacy) endpoints receive the Content via the video

channel using the same video protocol and resolution with which
they receive video.

• The highest Content resolution is HD720p, even if HD1080p is

selected in the Profile.

• Content cannot be sent to legacy endpoints when Same Layout mode

is selected for the conference.

• This option in not supported in High Definition Video Switching

conferences.

• When Content is transmitted, the Site Name of the endpoints cannot

be viewed.

• Content can be sent to legacy endpoints in gateway calls.

• When moving a legacy participant to the Operator conference, Content

will not be available to the legacy endpoint.

Interoperability with Polycom CMA and DMA

The CMA uses the Profiles that are stored in the RMX. If the Send Content
to Legacy Endpoints option is enabled in the Conference Profile, this option

will be enabled in the conference started from the CMA that uses that
Profile. However, the CMA does not display an indication that this option
is enabled for the conference.

2-17

Chapter 2-Additional Conferencing Information

A new conference can be started on the DMA using a Conference Profile
that is defined on the RMX or by defining all the conference parameters.
The Send Content to Legacy Endpoints option can be enabled only in the
Conference Profile defined in the RMX, therefore, to include this option in
the conference started on the DMA use an RMX existing Profile. However,
the DMA does not display an indication that this option is enabled for the
conference.

Content Display on Legacy Endpoints

When Contents is sent to legacy endpoints, their video layout
automatically changes to a “Content layout” which is defined by the
system flag LEGACY_EP_CONTENT_DEFAULT_LAYOUT and the
Content is shown in the larger/top left (“speaker”) window. The video
layouts of the other conference participants do not change.

The switch to the Content layout occurs in the Auto Layout, Presentation
Mode, Lecture Mode and when a layout is selected for the conference.
However, in Lecture Mode, when Content is sent to legacy endpoints,
when switching to the Content layout, the Content is shown in the
“lecturer/speaker” window and the lecturer is show in a second window.
If the layout contains more than two windows, all other windows will be
empty. All other participants will see the lecturer in full screen.

In Same Layout mode, Content cannot be sent to legacy endpoints.

The LEGACY_EP_CONTENT_DEFAULT_LAYOUT Flag default is set to
a layout of 1+4 where the Content is shown in the large window and the
other conference participants are shown in the small windows. This
default value can be changed in the System Configuration.

When Content is stopped, the layout of the legacy participants returns to
the last video layout seen prior to the Content mode.

The Legacy participants can change their layout using Click&View. In such
a case, the Content is forced to the “speaker” window.

The RMX user can also change the layout for the participants the legacy
endpoints (selecting personal layout).

When forcing a video participant to the Content window (instead of
Content), the Content display can be restored only by selecting any other
video layout.

2-18

Polycom RMX 2000/4000 Administrator’s Guide

Enabling the Send Content to Legacy Endpoints Option

The Send Content to Legacy Endpoint option is enabled in the Conference
Profile - Video Settings tab. It is selected by default.

If High Definition Video Switching option is selected in the Conference Profile

- General tab, the Send Content to Legacy Endpoints selection is cleared and

the option is disabled.

If the Same Layout option is selected in the Conference Profile - Video Settings
tab, the Send Content to Legacy Endpoints selection is cleared and is
disabled.

2-19

Chapter 2-Additional Conferencing Information

Changing the Default Layout for Displaying Content on Legacy Endpoints

The default layout that will be used to display Content on the screens of
legacy endpoints is defined by the system flag

LEGACY_EP_CONTENT_DEFAULT_LAYOUT.

The configured default layout is 1+4 (

CP_LAYOUT_1P4VER). You can

change the default layout configuration by entering a new value for the
flag in the system configuration.

To modify system flags:

1 On the RMX 2000 menu, click Setup > System Configuration.

The System Flags dialog box opens.

2 In the MCMS_PARAMETERS

tab, click the

LEGACY_EP_CONTENT_DEFAULT_LAYOUT entry.
The Update Flag dialog box is displayed.

3 In the Value field, enter the flag value for the required layout as

follows:

Table 2-6 LEGACY_EP_CONTENT_DEFAULT_LAYOUT Flag Values

Layout Flag Value

CP_LAYOUT_1X1

CP_LAYOUT_1X2

CP_LAYOUT_1X2HOR

2-20

CP_LAYOUT_1X2VER

CP_LAYOUT_2X1

CP_LAYOUT_1P2HOR

Polycom RMX 2000/4000 Administrator’s Guide

Table 2-6 LEGACY_EP_CONTENT_DEFAULT_LAYOUT Flag Values

(Continued)

Layout Flag Value

CP_LAYOUT_1P2HOR_UP

CP_LAYOUT_1P2VER

CP_LAYOUT_2X2

CP_LAYOUT_1P3HOR_UP

CP_LAYOUT_1P3VER

CP_LAYOUT_1P4HOR_UP

CP_LAYOUT_1P4HOR

CP_LAYOUT_1P4VER

CP_LAYOUT_1P5

CP_LAYOUT_1P7

CP_LAYOUT_1P8UP

CP_LAYOUT_1P8CENT

CP_LAYOUT_1P8HOR_UP

CP_LAYOUT_3X3

2-21

Chapter 2-Additional Conferencing Information

Table 2-6 LEGACY_EP_CONTENT_DEFAULT_LAYOUT Flag Values

Layout Flag Value

4 Click OK.

The flag is updated in the

5 Click OK.

For flag changes to take effect, reset the MCU. For more information, see the

RMX 2000/4000 Administrator’s Guide, "Resetting the RMX” on page 16-107.

(Continued)

CP_LAYOUT_2P8

CP_LAYOUT_1P12

CP_LAYOUT_4X4

MCMS_PARAMETERS list.

Stopping a Content Session

In some cases, when one participant ends the Content session from his/
her endpoint, the Content token is not released and other participants
cannot send Content.

The RMX User can withdraw the Content token from the current holder
and to return it to the MCU for assignment to other endpoints.

To end the current Content session:
>> In the Conferences list pane, right-click the conference icon and then

click Abort H.239 Session.

2-22

Lecture Mode

Lecture Mode enables all participants to view the lecturer in full screen
while the conference lecturer sees all the other conference participants in
the selected layout while he/she is speaking. When the number of sites/
endpoints exceeds the number of video windows in the 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.

Enabling Lecture Mode

Lecture Mode is enabled at the conference level by selecting the lecturer.

Automatic switching between participants viewed on the lecturer’s screen
is enabled in the conference Profile.

Enabling the Automatic Switching

>> In the Profile Properties - Video Settings dialog box, select the Lecturer

View Switching check box.

Polycom RMX 2000/4000 Administrator’s Guide

This option is activated when the conference includes more sites than
windows in the selected layout. If this option is disabled, the
participants will be displayed in the selected video layout without
switching.

For more information about Profile definition, see "Defining Profiles”
on page 1-8.

2-23

Chapter 2-Additional Conferencing Information

Selecting the Conference Lecturer

A conference can be set to Lecture Mode when:

• Defining a new ongoing Conference, after the adding or defining the
participant to be designated as lecturer

• During an ongoing conference, after the participant (to be designated
as lecturer) has connected to the conference.

To enable Lecture Mode for the Conference:
>> In the Conference Properties - Participant dialog box, select the Lecturer

from the list.

2-24

Restricting Content Broadcast to Lecturer

Content broadcasting can be restricted to the conference lecturer only,
when one of the conference participants is set as the lecturer (and not
automatically selected by the system). Restricting the Content Broadcast
prevents the accidental interruption or termination of H.239 Content that
is being shared in a conference.

Content Broadcast restriction is enabled by setting the

RESTRICT_CONTENT_BROADCAST_TO_LECTURER system flag to
ON. When set to OFF (default) it enables all users to send Content.

When enabled, the following rules apply:

• Content can only be sent by the designated lecturer. When any other

participant tries to send Content, the request is rejected.

• If the RMX user changes the designated lecturer (in the Conference

Properties - Video Settings dialog box), the Content of the current
lecturer is stopped immediately and cannot be renewed.

• The RMX User can abort the H.239 Session of the lecturer.

• Content Broadcasting is not implemented in conferences that do not

include a designated lecturer and the lecturer is automatically
selected by the system (for example, in Presentation Mode).

Lecture Mode Monitoring

A conference in which the Lecture Mode is enabled is started as any other
conference. The conference runs as an audio activated Continuous
Presence conference until the lecturer connects to the conference. The
selected video layout is the one that is activated when the conference
starts. Once the lecturer is connected, the conference switches to the
Lecture Mode.

When Lecturer View Switching is activated, it enables automatic switching
between the conference participants in the lecturer’s video window. The
switching in this mode is not determined by voice activation and is
initiated when the number of participants exceeds the number of
windows in the selected video layout. In this case, when the switching is
performed, the system refreshes the display and replaces the last active
speaker with the current speaker.

When one of the participants is talking, the automatic switching is
suspended, showing the current speaker, and it is resumed when the
lecturer resumes talking.

If the lecturer is disconnected during an Ongoing Conference, the
conference resumes standard conferencing.

Forcing is enabled at the Conference level only. It applies only to the
video layout viewed by the lecturer as all the other conference
participants see only the lecturer in full screen.

Polycom RMX 2000/4000 Administrator’s Guide

2-25

Chapter 2-Additional Conferencing Information

Participant designated as the

Lecturer

If an asymmetrical video layout is selected for the lecturer (i.e. 3+1, 4+1,
8+1), each video window contains a different participant (i.e. one cannot
be forced to a large frame and to a small frame simultaneously).

When Lecture Mode is enabled for the conference, the lecturer is indicated
by an icon ( ) in the Role column of the Participants list.

To control the Lecture Mode during an Ongoing Conference:

During the Ongoing Conference, in the Conference Properties - Video
Settings dialog box you can:

• Enable or disable the Lecture Mode and designate the conference
lecturer in the Lecturer list; select None to disable the Lecture Mode or
select a participant to become the lecturer to enable it.

2-26

Polycom RMX 2000/4000 Administrator’s Guide

• Designate a new lecturer.

• Enable or disable the Lecturer View Switching between participants

displayed on the lecturer monitor window by selecting or clearing
the Lecturer View Switching check box.

• Change the video layout for the lecturer by selecting another video

layout.

2-27

Chapter 2-Additional Conferencing Information

Closed Captions

Endpoints can provide real-time text transcriptions or language
translations of the video conference by displaying closed captions. The

captions for a conference may be provided by the captioner who is
present in the conference, or the captioner may use a telephone or web
browser to listen to the conference audio. When the captioner sends a unit
of text, all conference participants see it on the main monitor for 15
seconds. The text then disappears automatically.

The captioner may enter caption text using one of the following methods:

• Remotely, via a dial-up connection to the system’s serial RS-232 port.

• In the room using equipment connected directly to the serial port.

• In the room or remotely, using the Polycom HDX web interface.

Closed Captions Guidelines

• The Captions display properties are configured on the endpoint
sending the captions.

• Closed Captions content is defined from the endpoint. The RMX only
transmits it to the endpoints.

• When enabled, Closed Captions are available to all endpoints
supporting FECC.

• Closed Captions are supported in H.323 and SIP connections.

• The FECC indications during ongoing conferences are used when
closed captions are active.

• When Closed Captions are enabled, muting an endpoint may cause
the display of the “Far Mute” indication on all the screens of the
endpoints connected to the conference.

• The Closed Captions option is not supported in cascading
conferences (they can only be viewed in the local conference) as
FECC is not supported in cascading links.

• Site name display is not affected by closed captions display.

• Closed Captions are supported by the RMX in the following
configurations and conferencing modes:

— MPM and MPM+ Card Configuration Modes.
— High Definition Video Switching and Continuous Presence

conferencing modes.

2-28

— Encrypted and non-encrypted conferences.
— Conferences with Content.

Enabling Closed Captions

Closed Captions are enabled by a system flag. By default, Closed Captions
are disabled.

To change the flag value:

1 On the RMX 2000 menu, click Setup > System Configuration.

The System Flags dialog box opens.

Polycom RMX 2000/4000 Administrator’s Guide

2 In the MCMS_PARAMETERS

tab, click the New Flag ()

button.
The New Flag dialog box is displayed.

3 In the New Flag field enter ENABLE_CLOSED_CAPTION.

4 In the Value field enter YES to enable Closed Captions or NO to disable

their display.

5 Click OK to close the New Flag dialog box.

The new flag is added to the flags list.

6 Click OK to close the System Flags dialog box.

For flag changes to take effect, reset the MCU. For more information, see the
RMX 2000/4000 Administrator’s Guide, "Resetting the RMX” on page 16-107.

2-29

Chapter 2-Additional Conferencing Information

Media Encryption

Encryption is available at the conference and participant levels, based on
AES 128 (Advanced Encryption Standard) and is fully H.233/H.234
compliant and the Encryption Key exchange DH 1024-bit (Diffie­Hellman) standards.

Media Encryption Guidelines

• Encryption is not available in all countries and it is enabled in the
MCU license. Contact Polycom Support to enable it.

• Endpoints must support both AES 128 encryption and DH 1024 key
exchange standards which are compliant with H.235 (H.323) to
encrypt and to join an encrypted conference.

• The encryption mode of the endpoints is not automatically
recognized, therefore the encryption mode must be set for the
conference or the participants (when defined).

• Media Encryption for ISDN/PSTN participants is implemented in RMX
systems with MPM+ cards only.

• Conference level encryption must be set in the Profile, and cannot be
changed once the conference is running.

• If an endpoint connected to an encrypted conference stops encrypting
its media it is disconnected from the conference.

• Mixing encrypted and non-encrypted endpoints in one conference is
possible, based on system flag settings:
(ALLOW_NON_ENCRYPT_PARTY_IN_ENCRYPT_CONF).
The behavior is different for H.323 and ISDN participants.

• In Cascaded conferences, to encrypt the conferences the link between
the cascaded conferences must be encrypted.

• Media Encryption for ISDN/PSTN (H.320) participants is not
supported in cascaded conferences.

• The recording link from an encypted conference to the RSS set to
encryption can be encrypted. For more details, see "Recording Link
Encryption” on page 10-5.

You can define whether access to conferences for encrypted and non­encrypted participants is done at the conference level or at the participant
level.

2-30

Polycom RMX 2000/4000 Administrator’s Guide

Conference Access

When H.323 and ISDN participants connect directly to the conference,
they can be defined or undefined participants. Undefined Participants can
connect to an encrypted conference only if the endpoint’s encryption is set
to YES; otherwise, the endpoint’s encryption is considered as if set to NO.

Encrypted ISDN/PSTN Participant can connect to a non-encrypted
conference while encrypted H.323 participants cannot connect to a non­encrypted conference.

Non-encrypted participants can connect to an encrypted conference only
if they are defined in the conference’s participants list (defined
participants) and the system flag
ALLOW_NON_ENCRYPT_PARTY_IN_ENCRYPT_CONF is set to YES.
This flag does not apply to undefined participants. Table 2-7 summarizes

the conference access options for defined participants:

Table 2-7 Defined H.323 Participant Connection to the Conference Based on the

Encryption Settings

ALLOW_NON_
ENCRYPT_PARTY_
IN_ENCRYPT_CONF

NO Yes Auto Yes (encrypted)
NO Yes No No
NO Yes Yes Yes (encrypted)
NO No Auto Yes (non-encrypted)
NO No No Yes (non-encrypted)
NO No Yes No
YES Yes Auto Yes (encrypted)
YES Yes No Yes (non-encrypted)
YES Yes Yes Yes (encrypted)
YES No Auto Yes (non-encrypted)
YES No No Yes (non-encrypted)
YES No Yes No

Conference
Encryption
Setting

Participant
Encryption
Setting

Participant
Connection
Permitted

2-31

Chapter 2-Additional Conferencing Information

Defined ISDN participant connection to the conference is enabled
according to the flag setting and the conference encryption setting.

Table 2-8 Defined ISDN Participant Connection to the Conference Based on the

Encryption Settings

ALLOW_NON_
ENCRYPT_PARTY_
IN_ENCRYPT_CONF

NO Yes Auto Yes (encrypted)
NO Yes No No
NO Yes Yes Yes (encrypted)
NO No Auto Yes (non-encrypted)
NO No No Yes (non-encrypted)
NO No Yes Yes (encrypted)
YES Yes Auto Yes (encrypted)
YES Yes No Yes (non-encrypted)
YES Yes Yes Yes (encrypted)
YES No Auto Yes (non-encrypted)
YES No No Yes (non-encrypted)
YES No Yes Yes (encrypted)

Conference
Encryption
Setting

Participant
Encryption
Setting

Participant
Connection
Permitted

2-32

Entry Queue Access

To be able to join a conference from an Entry Queue as an encrypted
participant, encryption must be enabled in the Profile assigned to the
Entry Queue. All non-encrypted participants connecting to an encrypted
Entry Queue are disconnected from the MCU.

When an undefined participant connects to an Entry Queue the
participant inherits the encryption characteristics of the Entry Queue as
defined in the Entry Queue’s profile.

Polycom RMX 2000/4000 Administrator’s Guide

The participant’s move to the destination conference will be successful
depending on the Encryption flag setting and the destination conference
encryption setting, as summarized in Table 2-9:

Table 2-9 Encryption: Flag vs. Conference and Entry Queue Settings When

H.323 Participant Encryption is set to Auto

ALLOW_NON_
ENCRYPT_PARTY_
IN_ENCRYPT_CONF

NO Yes No No
NO Yes Yes Yes
NO No No Yes
NO No Yes No
YES Yes No No
YES Yes Yes Yes
YES No No Yes
YES No Yes Yes

Table 2-10 Encryption: Flag vs. Conference and Entry Queue Settings When

ISDN Participant Encryption is set to Auto

ALLOW_NON_
ENCRYPT_PARTY_
IN_ENCRYPT_CONF

Entry Queue
Encryption
Setting

Entry Queue
Encryption
Setting

Destination
Conference
Encryption
Setting

Destination
Conference
Encryption
Setting

Enable
Participant
Move from EQ
to Conference

Enable
Participant
Move from EQ
to Conference

NO Yes No Yes
NO Yes Yes Yes
NO No No Yes
NO No Yes No
YES Yes No Yes
YES Yes Yes Yes

2-33

Chapter 2-Additional Conferencing Information

Table 2-10 Encryption: Flag vs. Conference and Entry Queue Settings When

ISDN Participant Encryption is set to Auto (Continued)

ALLOW_NON_
ENCRYPT_PARTY_
IN_ENCRYPT_CONF

YES No No Yes
YES No Yes Yes

Move Guidelines

• When participants are moved to another conference their encryption
settings are evaluated to determine if the move is permitted. If not,
the move fails and the participants remain in their original conference.

•

When the flag is set to
that have different encryption settings. For example, encrypted
participants can move to encrypted and non-encrypted conferences.

• When the flag is set to NO, the participant’s encryption setting must
match the conference encryption setting to be moved to the other
conference. For example, encrypted participants can move only from
an encrypted conference to another encrypted conference.

Encryption Flag Settings

To modify the Encryption flag:

1 Click Setup>System Configuration.

The System Flags dialog box opens.

2 Set the ALLOW_NON_ENCRYPT_PARTY_IN_ENCRYPT_CONF

flag to YES or NO.

3 Click OK.

For more information, see "System Configuration” on page 16-5.

>> Reset the MCU for flag changes to take effect.

Entry Queue
Encryption
Setting

YES

, participants can move between conferences

Destination
Conference
Encryption
Setting

Enable
Participant
Move from EQ
to Conference

2-34

Enabling Encryption in the Profile

Encryption for the conference is in the Profile and cannot be changed once
the conference is running.

To enable encryption at the conference level:
>> In the Conference Profile Properties – Advanced dialog box, select the

Encryption check box.

Polycom RMX 2000/4000 Administrator’s Guide

The recording link from an encypted conference to the RSS set to
encryption can be encrypted. For more details, see "Recording Link
Encryption” on page 10-5.

Enabling Encryption at the Participant Level

You can select the encryption mode for each of the defined participants.
Encryption options are affected by the settings of the flag in the system
configuration. Undefined participants are connected with the Participant
Encryption option set to Auto, inheriting the conference/Entry Queue
encryption setting.

2-35

Chapter 2-Additional Conferencing Information

To enable encryption at the participant level:
>> In the Participant Properties – Advanced dialog box, in the Encryption

list, select one of the following options: Auto, On, or Off.

2-36

— Auto - The participant inherits the conference/Entry Queue

encryption setting. The participant connects as encrypted only if
the conference is defined as encrypted.

— Yes - The participant joins the conference/Entry Queue is

encrypted.

— No - The participant joins the conference/Entry Queue is

non-encrypted.

Monitoring the Encryption Status

The conference encryption status is indicated in the Conference Properties ­General dialog box.

The participant encryption status is indicated by a check mark in the
Encryption column in the Participants list pane.

An encrypted participant who is unable to join a conference is
disconnected from the conference. The disconnection cause is displayed
in the Participant Properties – Connection Status tab, Security Failure
indication, and the Cause box identifies the encryption related situation.

For more information about monitoring, see "Conference and Participant
Monitoring” on page 9-1.

Polycom RMX 2000/4000 Administrator’s Guide

2-37

Chapter 2-Additional Conferencing Information

LPR – Lost Packet Recovery

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

Packet Loss

Packet Loss refers to the failure of data packets, transmitted over an IP
network, to arrive at their destination. Packet Loss is described as a
percentage of the total packets transmitted.

Causes of Packet Loss

Network congestion within a LAN or WAN, faulty or incorrectly
configured network equipment or faulty cabling are among the many
causes of Packet Loss.

Effects of Packet Loss on Conferences

Packet Loss affects the quality of:

• Video – frozen images, decreased frame rate, flickering, tiling,
distortion, smearing, loss of lip sync

• Audio – drop-outs, chirping, audio distortion

• Content – frozen images, blurring, distortion, slow screen refresh rate

Lost Packet Recovery

The Lost Packet Recovery (LPR) algorithm uses Forward Error Correction
(FEC) to create additional packets that contain recovery information.
These additional packets are used to reconstruct packets that are lost, for
whatever reason, during transmission. Dynamic Bandwidth Allocation
(DBA) is used to allocate the bandwidth needed to transmit the additional
packets.

2-38

Polycom RMX 2000/4000 Administrator’s Guide

Lost Packet Recovery Guidelines

• LPR is supported in H.323 networking environments only.

•In LPR-enabled Continuous Presence conferences:

— Both LPR-enabled and non LPR-enabled endpoints are

supported.

— The LPR process is not applied to packet transmissions from non

LPR-enabled H.323, SIP and H.320 endpoints.

•In LPR-enabled Video Switched conferences:

— SIP and H.320 endpoints are not supported.
— Cascaded links to MGC are not supported.
— Non H.323 participants cannot be created, added or moved to

LPR-enabled Video Switched conferences.

• When connecting via an Entry Queue:

— A participant using an LPR-enabled endpoint cannot be moved

to a non LPR-enabled conference.

— SIP and H.320 participants cannot be moved to LPR-enabled

Video Switched conferences.

• If packet loss is detected in the packet transmissions of either the

video or Content streams:

— LPR is applied to both the video and Content streams.
— DBA allocates bandwidth from the video stream for the insertion

of additional packets containing recovery information.

Enabling Lost Packet Recovery

LPR is enabled or disabled in the Conference Profile dialog box.

• CP Conferences – LPR is enabled by default in the New Profile –

Advanced dialog box.

• HD VSW Conferences – If High Definition Video Switching is selected,

the LPR check box is automatically cleared and LPR is disabled. LPR
can be enabled for HD VSW conferences but H.320 and SIP
participants will not be able to connect.

For more information, see "Defining Profiles” on page 1-8.

2-39

Chapter 2-Additional Conferencing Information

Monitoring Lost Packet Recovery

In the Participant Properties – H.245 tab, LPR activity is displayed in all
three panes.

2-40

Polycom RMX 2000/4000 Administrator’s Guide

In the Participant Properties – Channel Status tab, check box indicators show
LPR activation in the local and remote (transmit and receive) channels.

2-41

Chapter 2-Additional Conferencing Information

Telepresence Mode

RMX 2000 supports the Telepresence Mode allowing multiple
participants to join a telepresence conference from RPX and TPX high
definition rooms as well as traditional, standard definition video
conferencing systems.

TPX (Telepresence) and RPX (Realpresence) room systems are configured
with high definition cameras and displays that are set up to ensure that all
participants share a sense of being in the same room.

Figure 2-1 Realpresence Participants using two RPX HD 400 Room Systems

The following are examples of situations where an RMX is needed for
Telepresence configurations:

•RPX to TPX

• RPX 2-cameras/screens to RPX 4-cameras/screens

•3 or more RPXs

•3 or more TPXs

RMX Telepresence Mode Guidelines

System Level

• The RMX system must be licensed for Telepresence Mode.

• The system must be activated with a Telepresence enabled license key.

2-42

Polycom RMX 2000/4000 Administrator’s Guide

Conference Level

• If the RMX is not licensed for Telepresence Mode, the Telepresence

option is not displayed in the New Profile dialog box

•A Telepresence conference must have Telepresence Mode enabled in its

profile.

• When Telepresence mode is selected in a conference profile, the

following options are disabled:

— borders
— site names
— speaker indication
— skins
— same layout
— presentation mode
— auto layout
— lecture mode

• The master (center) camera is used for video, audio and content.

• Conference Templates can be used to simplify the setting up

Telepresence conferences where precise participant layout and video
forcing settings are crucial. Conference Templates:

— Save the conference Profile.
— Save all participant parameters including their Personal Layout

and Video Forcing settings.

• An ongoing Telepresence conference can be saved to a Conference

Template for later re-use.

For more information see "Conference Templates” on page 8-1.

Room (Participant/Endpoint) Level

• To the RMX, each camera in a Telepresence room is considered to be an

endpoint and is configured as a participant.

•The Telepresence Mode field is always displayed in the New Participant

dialog box. If the system is not licensed for Telepresence this field is
automatically set to None.

• Telepresence participants (endpoints) must be specified as:

— RPX – transmitting 4:3 video

or

— TPX – transmitting 16:9 video

2-43

Chapter 2-Additional Conferencing Information

4:3

4:3

4:3 4:3 4:3 4:3
4:3 4:3 4:3 4:3

4:3 4:3 4:3 4:3

4:3 4:3

4:34:3

4:3

4:34:3

4:3

4:3 4:3 4:3 4:3

RPX and TPX Video Layouts

Additional video layouts have been created to give Telepresence operators
more video layout options when configuring TPX and RPX room systems.
These additional video layout options are only available when
Telepresence is selected in the conference profile.

Table 2-11 TPX / RPX – Additional Video Layouts

Number of

Endpoints

1

2

3

Layouts

TPX RPX

2-44

4

Polycom RMX 2000/4000 Administrator’s Guide

Table 2-11 TPX / RPX – Additional Video Layouts (Continued)

Number of
Endpoints

5

9

10+

Layouts

TPX RPX

2-45

Chapter 2-Additional Conferencing Information

Standard TPX Layout
Camera Zoomed Out

Alignment of back-projectors
eliminates the display of the
vertical blank areas of the
video layouts

TPX View

3 Screens 16:9

RPX View

4 Screens 4:3

The following example illustrates the use of standard and additional RMX
Telepresence layouts when connecting four Room Systems as follows:

• Two TPX Room Systems

— 2 active cameras
— 6 screens

• Two RPX Room Systems

— 8 cameras
— 8 screens

Figure 2-2 RPX and TPX Room System connected using RMX 2000/4000

2-46

Enabling Telepresence

Conference Level

Telepresence Mode must be configured in a new or existing Conference
Profile.

To enable Telepresence in a new or existing Conference Profile:

1 In the RMX Management pane, click Conference Profiles.

2 Click the New Profiles ( ) button or open an existing Conference

Profile.

3 Define the fields of the profile and click the Video Settings tab.

For more information on defining Profiles, see the RMX 2000/4000
Administrator’s Guide, "Defining Profiles” on page 1-8.

4 Select Telepresence Mode to enable the feature in the Conference

Profile.

Polycom RMX 2000/4000 Administrator’s Guide

2-47

Chapter 2-Additional Conferencing Information

5 Select the required video layout.

When Telepresence Mode is enabled, the Skin options are disabled as the
system uses a black background and the frames and speaker indication are
disabled.

6 Click OK.

Room (Participant/Endpoint) Level

Setting the participant/endpoint Telepresence Mode configures the RMX to
receive the video format of the RPX or TPX room endpoints.

To configure a participant/endpoint for Telepresence:

1 In the Address Book pane, click New Participant () or double-click

an existing Telepresence endpoint.

The New Participant or Participant Properties - General dialog box is
displayed.

2-48

2 If defining a new participant, enter the required information in the

New Participant – General dialog box for the participant.

Polycom RMX 2000/4000 Administrator’s Guide

For more information, see the RMX 2000/4000 Administrator’s Guide,
“Adding a new participant to the Address Book” on page 4-4.

3 Click the Advanced tab.
4 Select the Telepresence Mode for the participant:

Table 2-12 New Participant – Telepresence Mode

Mode Description

RPX Select this option for room endpoints that transmit

4:3 video format.

TPX Select this option for room endpoints that transmit

16:9 video format.

None Select this option for endpoints that are neither RPX

or TPX room endpoints.

5 Click OK.

Saving an Ongoing Conference as a Template

Any conference that is ongoing can be saved as a template.

To save an ongoing conference as a template:

1 In the Conferences List, select the conference you want to save as a

Template.

2 Click the Save Conference

() button.

or
Right-click and select Save Conference.

The conference is saved to a template whose name is taken from the
ongoing conference Display Name.

2-49

Chapter 2-Additional Conferencing Information

Starting an Ongoing Conference From a Template

An ongoing conference can be started from any Template saved in the
Conference Templates list.

To start an ongoing conference from a Template:

1 In the Conference Templates list, select the Template you want to start

as an ongoing conference.

2 Click the Start Ongoing Conference

() button.

or
Right-click and select Start Ongoing Conference.

The conference is started.

The name of the ongoing conference in the Conferences list is taken from
the Template display name of the template.

2-50

Polycom RMX 2000/4000 Administrator’s Guide

Conference

A

Conference

B

MCU A

MCU B

EQ

Cascaded

Link

Cascaded

Link

Cascading Conferences - Star Topology

Cascading enables administrators to connect one conference directly to
another conference using an H.323 connection, 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, for example,

different communication protocols, such as, serial connections, ISDN,

etc....

The link between the two conferences is created when a participant that is
defined as a dial-out cascaded link in one conference (Conference A)
connects to the second conference (Conference B) via a special cascaded
Entry Queue (EQ). When MCU A dials out to the cascaded link to connect
it to conference A, it actually dials out to the cascaded Entry Queue
defined on MCU B.

Figure 2-3 Cascaded Conferences - Star Topology

Though the process of cascading conferences mentioned in this section
refers to conferences running on two different RMX units, it is possible to
cascade conferences running between RMX units and other MCUs.

Simple cascade links are treated as endpoints in CP conferences and are
allocated resources according to Table 2-3 on page 2-6. Cascaded links in
1x1 video layout are in SD resolution.

In HD Video Switching, simple cascade links behave like HD endpoints if
all HD prerequisites are met - if not, the link is audio only.

2-51

Chapter 2-Additional Conferencing Information

Video layout of Conf. B in

window of Conf. A

Video layout of Conf. A in

window of Conf. B

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.

Without
Cascade

During
Cascading

Conference A Conference B

2-52

Figure 2-4 Video Layouts in Cascaded Conferences

The following features are not supported by the cascaded link and
therefore are not supported in the combined conference:

• DTMF codes are enabled in cascaded conference, but only in their
local conference. The operations executed via DTMF codes are not
forwarded between linked conferences.

• FECC (Far End Camera Control will only apply to conferences
running in their local MCU).

Enabling Cascading

Cascading two conferences requires that the following procedures are
implemented:

• Creating the cascade-enabled Entry Queue

A cascade-enabled Entry Queue must be created in the MCU hosting
the destination conference (Conference B). The cascade-enabled Entry
Queue is used to establish the dial-in link between the destination
conference and the linked conference and bypassing standard Entry
Queue, IVR prompt and video slide display.

• Creating a cascade-enabled Dial-out link

The creation of a cascade-enabled dial-out link (participant) in the
linked conference (Conference A). This dial-out participant functions
as the link between the two conferences.

• (Optional) Enabling the cascaded linked participant to connect to the

linked conference (Conference A) without entering the conference
password. This can be done by modifying the default settings of the
relevant system flag.

Creating the Cascade-enabled Entry Queue

Polycom RMX 2000/4000 Administrator’s Guide

The cascade-enabled Entry Queue maintains the correct behavior of the
cascaded link when it dials into it.

The cascade-enabled Entry Queue should be used only to connect cascaded
links and should not be used to connect standard participants to conferences.

When cascading High Definition (HD) conferences, the cascade-enabled
Entry Queue must have the same settings as both cascaded conferences
and the participants in both conferences must use the same line rate and
HD capabilities as set for the conferences and Entry Queue.

To define a Cascade-Enabled Entry Queue:

1 In the RMX Management pane, click the Entry Queues button.

The Entry Queues list pane is displayed.

2 Click the New Entry Queue button.

The New Entry Queue dialog box is displayed.

2-53

Chapter 2-Additional Conferencing Information

3 Define the standard Entry Queue parameters (as described in

Chapter 3).

4 In the Cascade field, select Master or Slave depending on the Master/

Slave relationship.
— Set this field to Master if the Entry Queue is defined on the MCU

that is at the center of the topology and other conferences dial
into it (acting as the Master).

— Set this field to Slave if the Entry Queue is defined on the MCU

acting as a Slave, that is, to which the link from the Master MCU
(MCU at the center of the topology) is dialing.

2-54

If you are defining an HD cascaded Entry Queue, it is recommended
to select the same Profile that is selected for both conferences.

5 Click OK.

The new Entry Queue enabling cascading is created.

Polycom RMX 2000/4000 Administrator’s Guide

Creating the Dial-out Cascaded Link

The dial-out link (participant) is created or added in the linked conference
(Conference A). The dial-out string defined for the participant is the
dialing string required to connect to the destination conference
(Conference B) Entry Queue defined on the MCU hosting the destination
cascaded conference. The dial-out participant can be defined in the
Address Book and added to the conference whenever using the same
cascade-enabled Entry Queue and a destination conference (with the
same ID and Password).

To define the Dial-out Cascaded Link:

1 Display the list of participants in the linked conference

(Conference A).

2 In the Participant List pane, click the New Participant button.

The New Participant - General dialog box is displayed.

3 In the Name field, enter a participant name.

4 In the Dialing Direction field, select Dial-out.

5 In the Type list field, verify that H.323 is selected.

2-55

Chapter 2-Additional Conferencing Information

For Example: 78485#24006#1234

Cascade-enabled

EQ ID

Destination

Conference ID

Password (optional)

For Example: 92578485#24006#1234

Cascade-enabled

EQ ID

Conference ID

Password (optional)MCU Prefix as

registered in the

gatekeeper

6 There are two methods to define the dialing string:

A Using the MCU’s IP Address and the Alias string.

B Using only the Alias string (requires a gatekeeper).

Method A (If no gatekeeper is used):

In the IP Address field, enter the IP address of the Signaling Host of
the MCU hosting the destination
MCU B).

In the Alias Name/Type field, enter the ID of the cascade-enabled Entry
Queue (EQ), the Conference ID and Password of the destination
conference (MCU B) as follows:
EQ ID#Destination Conference ID#Password (Password is optional).

Method B (Using a gatekeeper):

In the Alias Name field, enter the Prefix of MCU B, EQ ID, Destination
Conference ID, and Password, as follows:

MCU Prefix EQ ID#Conference ID#Password (Password is optional)

conference (in the example,

7 Click the Advanced tab.

2-56

Polycom RMX 2000/4000 Administrator’s Guide

8 In the Cascade field, select:

— Slave, if the participant is defined in a conference running on a

Slave MCU and will connect to the Master MCU (in the center of
the topology).

—

Master

the Master MCU
Master MCU to the Slave MCU

, if the participant is defined in a conference running on

(in the center of the topology)

dialing from the

.

9 Click OK.

The cascade-enabled dial-out link is created and the system
automatically dials out to connect the participant to the linked
conference, as well as the destination conference.

2-57

Chapter 2-Additional Conferencing Information

Enabling Cascaded Conferences without Password

If a password is assigned to the linked conference, cascaded links will be
prompted for a password when connecting to it (Conference A).
Administrators have the option of altering the MCU settings to enable
cascaded links to connect without a password.

To enable cascaded links to connect without a password:

1 In the RMX web client connected to MCU A (where the linked

conference is running), click Setup>System Configuration.
The System Flags dialog box opens.

2 Set the

_WITHOUT_PASSWORD

3 Click OK.

For more information, see "System Configuration” on page 16-5.

>> Reset the MCU for flag changes to take effect.

ENABLE_CASCADED_LINK_TO_JOIN

flag to YES.

2-58