Polycom IMMERSIVE TELEPRESENCE User Manual

Polycom® Immersive Telepresence (ITP) Deployment Guide

Revision A | February 2011 | 3725-26703-002/A

Version 1.0 | July, 2009 | 3725-?????-001

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.

© 2011 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.

ii

About this Guide

The Polycom Immersive Telepresence (ITP) Deployment Guide provides the best
practices for configuring multipoint conferences on Polycom RMX™ 4000 and
RMX 2000® real-time multimedia conference platforms with the following
telepresence solutions:

• Polycom RPX™ HD 400 Series

• Polycom RPX HD 200 Series

• Polycom OTX™ 300

• Polycom TPX® HD 306M

• Polycom TPX HD 204M

• Polycom ATX 300

• Polycom ATX SDK (which supports the ATX 200, ATX 300, and ATX 400

hardware platforms)

This guide is intended for Immersive Telepresence (ITP) administrators and
for Polycom RMX 4000 and RMX 2000 administrators who manage
telepresence calls. The ITP and RMX administrators should have:

• Prior knowledge and experience with the RMX 4000 and RMX 2000 and

with the Polycom Multipoint Layout Application (MLA).

• Familiarity with configuring both overall conference settings and with

configuring the personal layouts of the conference sites.

• Access to Polycom RMX 4000, RMX 2000, RPX, OTX, TPX, ATX, and MLA

product documentation.

iii

Polycom Immersive Telepresence (ITP) Deployment Guide

iv

Contents

Contents

1 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Software and Hardware Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1

MLA and ATX SDK Version 2.0 Compatibility . . . . . . . . . . . . . . . . . . 1–3

Microsoft Unified Communications (UC) Compatibility . . . . . . . . . . . . . 1–3

Microsoft Office Communications Server (OCS) Compatibility . . . . 1–4

Meeting Composer Considerations . . . . . . . . . . . . . . . . . . . . . . . . 1–4

Polycom Conferencing for Microsoft Outlook (PCO) Compatibility 1–4

Obtaining More Information about UC Compatibility . . . . . . . . . . . . 1–5

User-Initiated Multipoint Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5

2 Multipoint Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Calculating and Naming Conference Sites . . . . . . . . . . . . . . . . . . . . . . . . . 2–2

Calculating Total Conference Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2

Naming Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–2

Understanding Multipoint with OTX, TPX, and ATX . . . . . . . . . . . . . . . . 2–4

Using Video Switching with TPX and ATX 300

(for RMX 2000 Systems with MPM Only) . . . . . . . . . . . . . . . . . . . . . . . 2–5

Using Single Touch Multipoint with OTX, TPX, and ATX . . . . . . . . 2–6

Recording Telepresence Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6

Cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6

Other Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7

3 Configuring RMX Settings for ITP Systems . . . . . . . . . . . . . 3-1

Configuring the RMX Settings for 1080p HD Video . . . . . . . . . . . . . . . . . 3–1

Configuring the RMX Settings for 720p/60 HD Video . . . . . . . . . . . . . . . 3–4

Configuring the RMX Settings for 720p/30 HD Video . . . . . . . . . . . . . . . 3–6

Configuring Other RMX Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–9

Configuring RMX Settings for Large Conferences . . . . . . . . . . . . . . . . . . 3–10

A Multipoint Framing Scenarios for Immersive Telepresence . A-1

B Manual Video Layout Framing Examples . . . . . . . . . . . . . . B-1

Polycom, Inc. v

Polycom Immersive Telepresence (ITP) Deployment Guide

vi Polycom, Inc.

Compatibility

This chapter includes the following compatibility information:

• Software and hardware compatibility

• Microsoft Unified Communications (UC) compatibility

• User-initiated multipoint compatibility

1

Software and Hardware Compatibility

The information in this guide applies to the following software releases:

Product Software Release

ATX SDK Version 2.0 and Version 2.0.1 (which supports the

ATX 200 and ATX 400 hardware platforms, as well
as continued support for the ATX 300 hardware
platform)

Version 1.0.1
Version 1.0*

CMA™ Version 5.4.0

Version 5.3.0
Version 5.0.0
Version 4.1.4

Immersive Telepresence
(ITP)

Version 2.7 and Version 2.7.1
Version 2.6 (and Version 2.6.1 for ATX 300)
Version 2.5 (RPX and TPX only)
Version 2.0.3
Version 1.5 (RPX and TPX only)

1–1

Polycom Immersive Telepresence (ITP) Deployment Guide

Product Software Release

Multipoint Layout
Application (MLA)

RMX 2000 Version 7.1.0.121

RMX 4000 Version 7.1.0.121

Version 2.7 and Version 2.7.1
Version 2.5*

Version 7.0.2.68
Version 6.0.1.12

Version 7.0.2.68
Version 6.0.1.12

*Note that ATX SDK Version 1.0 and MLA Version 2.5 are certified with RMX
4000 and RMX 2000 Version 6.0.1 only.

The following table indicates the hardware compatibility.

RMX 2000 and RMX 4000 Hardware

Software Version

7.1.0 —

7.0.2 — ✔✔

MPM MPM+ MPMx

✔✔

6.0.1 ✔✔—

The following table indicates the software compatibility.

RMX Software Version

ITP Software Version 6.0.1 7.0.2 7.1.0

Version 2.7 and 2.7.1

Version 2.6 ✔
Version 2.5 ✔

Version 2.0.3 ✔

Version 1.5

ATX SDK Software

Version

Version 2.0 and 2.0.1

Version 1.1 ✔
Version 1.0

✔

✔

✔

✔

✔

✔

6.0.1 7.0.2 7.1.0

✔

✔

✔

✔

✔

✔

✔

✔

✔

—
—

✔

—
—

1–2 Polycom, Inc.

Compatibility

MLA and ATX SDK Version 2.0 Compatibility

MLA Version 2.7 or later is required when using ATX SDK Version 2.0. This
applies whether you have the ATX 200, ATX 300, or ATX 400 hardware
platform.

When using the MLA user interface with an ATX 200 or ATX 400:

• The MLA treats ATX 200 systems the same way as TPX 204 systems.

Therefore, the MLA user interface will display ATX 200 systems as site
type TPX 204. Additionally, if you create a layout template for an ATX 200,
you must select TPX 204 as the Type.

• The MLA treats ATX 400 systems the same way as RPX 400 systems.

Therefore, the MLA user interface will display ATX 400 systems as site
type RPX 400. Additionally, if you create a layout template for an ATX 400,
you must select RPX 400 as the Type.

Microsoft Unified Communications (UC) Compatibility

ITP systems participate in the Polycom Unified Communications experience
in the following ways:

• With ITP Version 2.5 and later (and ATX SDK Version 1.0 and later), ITP

systems can communicate with Office Communicator (OC) clients via an
RMX conference, when the RMX is configured in a Microsoft Office
Communications Server environment.

• With ITP Version 2.7 and later (and ATX SDK Version 2.0), ITP systems are

enabled (via their HDX codecs) for Polycom Conferencing for Microsoft
Outlook. Participants using a Touch Panel can use it to view a list of
scheduled meetings and join those meetings.

This section describes these features and provides guidance for where to
obtain information to configure and activate the features.

Polycom Implementation and Maintenance services provide support for Polycom
solution components only. Additional services for supported third-party Unified
Communications (UC) environments integrated with Polycom solutions are
available from Polycom Global Services and its certified Partners to help customers
successfully design, deploy, optimize, and manage Polycom visual communication
within their third-party UC environments. UC Professional Services for Microsoft
Integration is mandatory for Polycom Conferencing for Microsoft Outlook and
Microsoft Office Communications Server integrations. For additional information
and details, see http://www.polycom.com/services/professional_services/index.html
or contact your local Polycom representative

.

Polycom, Inc. 1–3

Polycom Immersive Telepresence (ITP) Deployment Guide

Microsoft Office Communications Server (OCS) Compatibility

With ITP software Version 2.5 and later (and ATX SDK Version 1.0 and later),
an RMX in an OCS environment and ITP endpoints can be supported together
in the same conference. Note that point-to-point calls involving ITP suites and
Office Communicator (OC) clients are not supported; the only way to enable
them to communicate with each other is through the RMX.

Meeting Composer Considerations

If you want to access an OC client when creating a multipoint call with the ITP
Meeting Composer feature, you must add the OC client to the local directory
of the ITP suite. This is because OC clients are not listed in the global directory
of the Polycom Converged Management Application (CMA).

To add an OC client to the local directory of an ITP suite:

1 Log into the Polycom HDX web UI for the Primary codec.

2 Fill in the SIP Address and Name fields of the OC client as a single site

entry.

Once you have configured this (and assuming that you have also enabled
Meeting Composer and configured the RMX for integration into the Microsoft
OCS environment), you can select OC clients for any of the Meeting Composer
activities.

Alternatively, if you do not wish to use the Meeting Composer feature, the
RMX operator will set up the call directly, dialing out from the RMX to the ITP
suites and OC clients. In this case, you do not need to add the OC client to the
local directory of the ITP suite.

Polycom Conferencing for Microsoft Outlook (PCO) Compatibility

ITP 2.7 extends the HDX implementation of PCO into the ITP suite. The only
difference from the HDX implementation is that, for ITP, the UI for the feature
is on the Touch Panel instead of on the HDX UI.

In the case of ITP, only the Primary codec system's calendaring settings are
configured. CMA automatic provisioning of calendaring is NOT supported
with ITP HDXs, and the other HDXs in the ITP suite are not configured.

With ITP Version 2.7 and PCO, private meeting details are displayed on the ITP
system Touch Panel, even if the primary HDX system is not configured to Show
Private Meeting Details. This limitation has been fixed in ITP Version 2.7.1.

1–4 Polycom, Inc.

Compatibility

Obtaining More Information about UC Compatibility

For more information about:

• Polycom RMX in a Microsoft Office Communications Server environment,

refer to the Deploying Visual Communications Administration Guide.

• Enabling Polycom Conferencing for Outlook for ITP systems, Meeting

Composer, and configuring the local directory for ITP systems, refer to the
Polycom Immersive Telepresence (ITP) Administrator's Guide.

• Configuring the RMX for integration into the Microsoft OCS environment,

refer to the Polycom RMX Administrator's Guide.

• OCS environment software version compatibility with the RMX, refer to

the Polycom RMX Release Notes.

User-Initiated Multipoint Compatibility

You can configure your ITP solution to enable four different types of
user-initiated multipoint conferences:

• Polycom Conferencing for Microsoft Outlook: Using the Touch Panel,

users can view a list of scheduled meetings and join those meetings.

• Meeting Composer: Using the Touch Panel, users can launch multipoint

calls directly from the ITP room by choosing all of the conference
participants from the directory. Once the conference is connected, users
can add and drop conference participants as needed.

• Multipoint Speed Dial: Using the Touch Panel, users can launch RMX

calls to multiple sites at one time simply by pressing a Speed Dial button
that the administrator has configured to dial a pre-determined list of sites.

• Single Touch Multipoint: Using the Touch Panel, users can call an RMX

Virtual Meeting Room (VMR) simply by pressing a Speed Dial button that
the administrator has configured to dial into the VMR.

These user-initiated multipoint conference features are available only to sites
using an RMX and the MLA in automatic conference layout mode. MLA
supports two types of automatic conference layout modes:

• Room Continuous Presence: In this standard mode, the multipoint view

is automatically generated either to follow the general principles of
Polycom immersive telepresence multipoint (that is, all participants are
"present" during a multipoint conference) or to fit a custom-set view
configured by the conference administrator for the combination of sites in
a particular conference.

• Voice Activated Room Switching (VARS): VARS is different from the

standard Room Continuous Presence mode in that the speaker's site is the
only site seen by others. The view of the speaker's site is sized to be as large

Polycom, Inc. 1–5

Polycom Immersive Telepresence (ITP) Deployment Guide

as possible on all of the other participants' displays. The current speaker
sees the previous speaker's site (that is, the speaker's layout remains
unchanged). Layouts used in VARS are not customizable.

VARS should not be used during Polycom Conferencing for Microsoft Outlook or
Single Touch Multipoint conferences that have participants at OTX, TPX, or ATX
sites. Instead, you should configure those conferences for Room Continuous
Presence mode.

1–6 Polycom, Inc.

Multipoint Best Practices

In Polycom Immersive Telepresence Series suites, the video is delivered using
two, three, or four independent Polycom HDX video codecs. This creates
additional multipoint complexity over traditional video conferencing because,
from the perspective of the RMX, all of the codecs in an RPX, OTX, TPX, or
ATX site would typically be treated as though they were separate sites.

Continuous presence transcoding is normally used for telepresence multipoint
today. Until recently, the endpoints in telepresence rooms were “framed”
together on the RMX by the multipoint conference platform administrator,
using the personal layout control of each conference site. This approach
ensured that the rooms appeared properly within the various continuous
presence views.

2

With the introduction of Version 2.0 of the Polycom Multipoint Layout
Application (MLA), the process of managing telepresence conferences became
greatly simplified. With MLA, layouts are applied automatically for each
telepresence site in a conference.

Polycom’s suggested best practice is to set up the MLA to configure all
telepresence conference layouts automatically. You can also use MLA to
define custom layout templates for automatic application. For more
information, refer to the Polycom Multipoint Layout Application User Guide for
use with Polycom Telepresence Solutions.

2–1

Polycom Immersive Telepresence (ITP) Deployment Guide

Calculating and Naming Conference Sites

As the RMX administrator, you must be familiar with configuring both the
overall conference settings and the personal layouts of the conference sites. For
more information, refer to the Polycom RMX Administrator’s Guide.

Calculating Total Conference Sites

To calculate the total site connections required for a multipoint conference, use
the following formula:

(RPX HD 200 Series suites * 2) +
(RPX HD 400 Series suites and ATX 400 sites * 4) +
(OTX sites and TPX 306 sites and ATX 300 sites * 3) +
(TPX 204 sites and ATX 200 sites *2) +
(Traditional videoconferencing systems * 1) =
Total conference sites required for the conference

Naming Sites

Naming the telepresence sites appropriately in the RMX 4000 and RMX 2000
address book is a critical step towards helping to frame the sites correctly.

When naming the sites, you must follow these naming conventions:

Telepresence Site Naming Conventions

Telepresence Suite Naming Convention

RPX HD 200 Series,
TPX HD 204M, and ATX 200

RPX HD 400 Series and
ATX 400

OTX, TPX HD 306M, and
ATX 300

Append the site name with “2” for left and “1” for
right.

Append the site name with “4” for left, “2” for
center left, “1” for center right, and “3” for right.

Append the site name with “2” for left, “1” for
center, and “3” for right.

2–2

RPX 200/TPX 204/ATX 200

RPX 400/ATX 400

OTX 300/TPX 306/ATX 300

Multipoint Best Practices

When naming the sites, keep the following in mind:

• The codec associated with the camera that shows the right side of the room
from the camera point of view is the same codec that drives the right display
from the point of view of the participants seated at the table.

• Codec 1 in all telepresence rooms is the primary codec. The primary codec is
the codec through which the audio and content video are sent and received. The
remaining (non-primary) codecs handle people video only.

For the MLA to work properly with dial-in conferences, the naming convention
requirement extends to the HDX codecs in the telepresence suites. In this mode,
the H.323 Name and System Name fields of the codecs must also be named as
indicated in this section. For more information, refer to the “Setting Up Naming on
the HDXs” section of the Polycom Immersive Telepresence Administrator ’s Guide.

Example

An RPX 200 Series suite at Acme in New York uses the name “Acme NY 18th
Floor 1” and “Acme NY 18th Floor 2”. These names suggest to the RMX
administrators that codec 1 is looking at the right side of the room and codec
2 is looking at the left side of the room.

The figure below shows a visual representation of telepresence site naming.

Telepresence Site Naming Example

2–3

Polycom Immersive Telepresence (ITP) Deployment Guide

Understanding Multipoint with OTX, TPX, and ATX

In Room Continuous Presence multipoint calls, the camera views with OTX,
TPX, ATX 200, and ATX 300 are handled differently than with RPX and ATX

400. While OTX, TPX, ATX 200, and ATX 300 use one camera to capture the
full-room view, RPX and ATX 400 capture a full-room view using all the
cameras, with each camera capturing a different portion of the room.

• At sites with TPX systems with Eagle Eye 1080 cameras, the cameras capture
only the center four seats, not all six, when showing the full room view. TPX
systems with Eagle Eye HD or Eagle Eye II cameras show the outer two seats
partially obscured from view. This also applies to ATX sites where the table is
placed at 110” (2.79 m).

• When viewing a 3x3 layout on an OTX, TPX, or ATX screen, the video may be
shifted slightly to the right side of the screen.

This camera positioning makes multipoint video layouts straightforward. For
an OTX, TPX, ATX 200, or ATX 300 site to be seen by another site, it needs only
a single window in a continuous presence layout. If there are few sites in the
conference, this could even be a single window with full screen layout. The
camera view also allows a wide aspect ratio window to be used, such as in the
layout illustrated below. For the wide viewing windows, the top and bottom
of the OTX, TPX, ATX 200, and ATX 300 view are cropped, but the people are
still visible.

2–4

Sample Layout Showing Wide Aspect Ratio Views

You can use any of the cameras in the OTX, TPX, ATX 200, or ATX 300 room
as the source for video from the room. However, to achieve optimal eye
contact, choose the camera closest to the display where the other site’s people
are seen.

Multipoint Best Practices

For example, suppose TPX site A is viewing site B on the left display (codec
number 2). When choosing the layout for site B, use the video from the right
camera (codec number 3) in the TPX room because camera 3 is closest to
display 2.

TPX HD 306M Framing Example Illustrating Optimal Eye Contact

Using Video Switching with TPX and ATX 300 (for RMX 2000 Systems with MPM Only)

In multipoint conferences that include up to four TPX HD 306M or ATX 300
sites or up to three TPX HD 204M sites with no other sites, the RMX supports
HD Video Switching mode. This mode provides full screen HD video without
transcoding delay. Note that Video Switching does not apply to OTX.

To enable Video Switching for TPX or ATX 300:

1 In the RMX conference profile settings, select the High Definition Video

Switching check box.

2 Set the Line Rate to 1920 Kbps and the Video Quality to Sharpness. This

will result in 720p/30 video.

With Video Switching, each endpoint can still be forced to receive video from
another particular endpoint, in much the same manner as personal layouts for
continuous presence mode. The only difference is that there is no choice in the
layout arrangement; it is limited to full screen video.

2–5

Polycom Immersive Telepresence (ITP) Deployment Guide

Video Switching modedoesnotallowyoutoforceblackvideotoany
particulardisplay. Therefore,ifyouhadonlythreeTPXHD306MorATX300
sitesinamultipointcall,youwouldseetheothertwositesontwoofthe
displays,andyouwouldseeeitheraduplicateimage,
display.

Using Single Touch Multipoint with OTX, TPX, and ATX

When an OTX, TPX, or ATX site connects via Single Touch Multipoint to an
RMX meeting room, and the telepresence layouts are configured so that a 1x1
layout from an RPX site is sent to an OTX, TPX, or ATX display, the OTX, TPX,
or ATX will show 4:3 video on its display. This “pillarbox” effect is not
optimal, especially if your intent is to display the view from the RPX suite
across two OTX, TPX, or ATX displays.

A multipoint call with two OTX, TPX, or ATX sites and one RPX 200 Series site
is the most likely scenario where this would occur. As a workaround, you can
create an alternative layout scenario for the OTX, TPX, or ATX that avoids
specifying 1x1 layouts from RPX sites.

oryourself,onthethird

Refer to the Polycom Immersive Telepresence (ITP) Administrator’s Guide for a
complete set of application notes regarding Single Touch Multipoint.

Recording Telepresence Conferences

With MLA, you can use the Polycom RSS™ 2000 Single Point Recording
feature with the RMX 4000 or RMX 2000 to easily record ITP conferences.

When an ITP conference that is under management by the MLA has recording
enabled, the recorded video on the RSS 2000 will feature the layout view
normally sent to a one-screen, traditional video conferencing system. The
remaining sites in the conference will see the layout that they would typically
see if recording was not enabled.

Cascading

Multi-codec telepresence conferences are not supported across cascaded RMX
links. However, an RMX 4000 or RMX 2000 that is hosting a telepresence
conference can be cascaded to another RMX 4000 or RMX 2000 conference with
traditional endpoints. From the perspective of the telepresence conference, the
video source from the cascaded link will be treated as a traditional endpoint.

2–6

Multipoint Best Practices

Other Considerations

Note the following considerations regarding multipoint conferences:

• When participants drop out of a multipoint call, the remaining sites must

be re-framed to account for the change in the number of codecs. If you
have configured the MLA to automatically apply layouts for your
conference, MLA will re-frame the sites for you.

• If one of the HDX codecs at a telepresence site inadvertently becomes

disconnected from a multipoint call, you may have to disconnect all of the
remaining HDX codecs from that site in order to reconnect properly. This
is because the system can be configured to disallow incoming calls to the
HDX codecs when one or more of the codecs is in a call. For more
information, refer to the Do Not Disturb timer information in the Polycom
Immersive Telepresence (ITP) Administrator’s Guide.

2–7

Polycom Immersive Telepresence (ITP) Deployment Guide

2–8

Configuring RMX Settings for ITP Systems

This chapter lists the RMX 4000 and RMX 2000 settings for:

• 1080p HD video

• 720p/60 HD video

3

• 720p/30 HD video

In addition, this chapter lists the other RMX settings that you should
configure, as well as the settings you should configure for large conferences.

Configuring the RMX Settings for 1080p HD Video

1080p HD video requires MPMx or MPM+ hardware. In addition, you must
use one of these RMX 4000 or RMX 2000 versions:

• Version 6.0.1.12

• Version 7.0.2.68

• Version 7.1.0.121

(For specific ITP and ATX SDK compatibility information, refer to the
Software Compatibility table on page 1-2.)

The following tables list which HDX software version you must use for each
product release.

RPX OTX 300 TPX ATX 300

ITP 2.7.1 HF-2.6.1.3_00_

ITP271-5267

HF-2.6.1.3_00_
ITP271-5267

HF-2.6.1.3_00_
ITP271-5267

HF-2.6.1.3_00_
ITP271-5267

ITP 2.7 HF-2.6.1_00_

ITP27-5201

HF-2.6.1_00_
ITP27-5201

HF-2.6.1_00_
ITP27-5201

HF-2.6.1_00_
ITP27-5201*

3–1

Polycom Immersive Telepresence (ITP) Deployment Guide

RPX OTX 300 TPX ATX 300

ITP 2.6 HF-2.5.0.7_

ITP25-4803

ITP 2.5 HF-2.5.0.7_

ITP25-4803

ITP 2.0.3 HF-2.5.0.5_04-3562 N/A HF-2.5.0.5_04-3562 HF-2.5.0.5_04-3562

N/A HF-2.5.0.7_

ITP25-4803

N/A HF-2.5.0.7_

ITP25-4803

HF-2.5.0.7_
ITP25-4803

N/A

*Also applies to ATX 300 Version 2.6.1.

A TX SDK

Version 2.0.1 HF-2.6.1.3_00_ITP271-5267
Version 2.0 release-2.6.3-5807
Version 1.1 HF-2.6.1_atx_sdk_1_0-5803
Version 1.0 HF-2.5.0.7_ITP-4833

By configuring the RMX settings as described in this section, the RMX will
send the following:

• 1080p HD resolution continuous presence to ITP sites with HDX 8000

Series codecs.

• 720p/30 HD resolution continuous presence to ITP sites with HDX 9004

codecs.

3–2

• It is normal to see occasional video stuttering (jerkiness) when using this
conference profile.

• If you have ITP Version 2.7 or earlier and you have an RMX with MPMx
hardware, do not use this conference profile if you include RPX systems in the
call. Instead, use the 720p/60 HD video profile described in the Configuring the

RMX Settings for 720p/60 HD Video on page 3-4. This limitation has been fixed

in ITP Version 2.7.1.

1080p HD Video Conference Profile Settings

This setting.... Should be set to...

General Line Rate 4096 Kbps (3072 Kbps for

MPMx if all ITP systems in the
call are enabled for H.264 High

Profile)
High Definition Video Switching Unchecked
Operator Conference Unchecked

Configuring RMX Settings for ITP Systems

This setting.... Should be set to...

Advanced LPR Checked

Encryption Optional
Auto Terminate Optional
Echo Suppression Checked
Keyboard Suppression Optional

Gathering Settings Enable Gathering Optional
Video Quality People Video: Video Quality Sharpness

People Video: Video Clarity Unchecked

Video Quality
(continued)

Video Settings Telep res ence Mode Auto

Skins Not Applicable
IVR (If desired, create an IVR service

Recording Optional

Content Video: Content Settings Graphics
Content Video: Content Protocol Up to H.264

Telep res ence Layout Mode Continuous Presence
All other check boxes Unchecked

that disables the video splash
screen and audio greetings.

NOTE: If you are planning to
include OTX, TPX, or ATX
systems, you must create an IVR
service that disables the video
splash screen and audio greetings.
There is a known issue where the
interaction of IVR and 16:9 displays
results in video with an incorrect
aspect ratio on the 16:9 display.)

Conference Requires Chairperson Unchecked

When configuring the RMX settings for 1080p HD video, note the following:

• Beginning with RMX Version 7.0.2 there is a new system flag,
ITP_CERTIFICATION. This flag must be set to YES.

For more information about configuring RMX system flags, refer to the
Polycom RMX Administrator’s Guide.

3–3

Polycom Immersive Telepresence (ITP) Deployment Guide

• You should validate that the system flag MAX_CP_RESOLUTION is set to
HD1080 for the 1080p HD profile. (HD1080 is the default setting.)

For more information about setting this flag for large conferences, see

Configuring RMX Settings for Large Conferences on page 3-10.

• To avoid seeing a slight vertical shift in the onscreen video when content
is shared (on RMX systems with MPM+ hardware only), go to Setup >
Resolution Configuration and do the following:

— Select Manual in the Resolution Configuration field.

— Set the Sharpness HD 1080p30 slider to 3072 kbps.

Configuring the RMX Settings for 720p/60 HD Video

720p/60 HD video requires MPMx or MPM+ hardware. In addition, you must
use one of these RMX 4000 or RMX 2000 versions:

• Version 6.0.1.12

• Version 7.0.2.68

• Version 7.1.0.121

(For specific ITP and ATX SDK compatibility information, refer to the
Software Compatibility table on page 1-2.)

The following tables list which HDX software version you must use for each
product release.

RPX OTX 300 TPX ATX 300

ITP 2.7.1 HF-2.6.1.3_00_

ITP271-5267

ITP 2.7 HF-2.6.1_00_

ITP27-5201

ITP 2.6 HF-2.5.0.7_

ITP25-4803

ITP 2.5 HF-2.5.0.7_

ITP25-4803

ITP 2.0.3 HF-2.5.0.5_04-3562 N/A HF-2.5.0.5_04-3562 HF-2.5.0.5_04-3562

HF-2.6.1.3_00_
ITP271-5267

HF-2.6.1_00_
ITP27-5201

N/A HF-2.5.0.7_

N/A HF-2.5.0.7_

HF-2.6.1.3_00_
ITP271-5267

HF-2.6.1_00_
ITP27-5201

ITP25-4803

ITP25-4803

HF-2.6.1.3_00_
ITP271-5267

HF-2.6.1_00_
ITP27-5201*

HF-2.5.0.7_
ITP25-4803

N/A

*Also applies to ATX 300 Version 2.6.1.

3–4

Configuring RMX Settings for ITP Systems

A TX SDK

Version 2.0.1 HF-2.6.1.3_00_ITP271-5267
Version 2.0 release-2.6.3-5807
Version 1.1 HF-2.6.1_atx_sdk_1_0-5803
Version 1.0 HF-2.5.0.7_ITP-4833

By configuring the RMX settings as described in this section, the RMX will
send the following:

• 720p/60 HD resolution continuous presence to ITP sites with HDX 8000
Series codecs.

• SD/60 resolution continuous presence to ITP sites with HDX 9004 codecs
(RPX sites receive 4SIF 4:3 aspect ratio at 60 fps; TPX sites receive 720x400
16:9 aspect ratio at 60 fps).

It is normal to see occasional video stuttering (jerkiness) when using this
conference profile on an RMX with MPMx hardware.

720p/60 HD Video Conference Profile Settings

This setting... Should be set to...

General Line Rate 4096 Kbps (3072 Kbps for

MPMx if all ITP systems in the
call are enabled for H.264 High

Profile)
High Definition Video Switching Unchecked
Operator Conference Unchecked

Advanced LPR Checked

Encryption Optional
Auto Terminate Optional
Echo Suppression Checked
Keyboard Suppression Optional

Gathering Settings Enable Gathering Optional
Video Quality People Video: Video Quality Motion

Content Video: Content Settings Graphics
Content Video: Content Protocol Up to H.264

3–5

Polycom Immersive Telepresence (ITP) Deployment Guide

This setting... Should be set to...

Video Settings Telepresence Mode Auto

Telep r esence Layout Mode Continuous Presence
All other check boxes Unchecked

Skins Not Applicable
IVR (If desired, create an IVR service

that disables the video splash
screen and audio greetings.

NOTE: If you are planning to
include OTX, TPX, or AT X systems,
you must create an IVR service that
disables the video splash screen
and audio greetings. There is a
known issue where the interaction
of IVR and 16:9 displays results in
video with an incorrect aspect ratio
on the 16:9 display.)

Conference Requires Chairperson Unchecked

Recording Optional

When configuring the RMX settings for 720p/60 HD video, note the following:

• Beginning with RMX Version 7.0.2 there is a new system flag,
ITP_CERTIFICATION. This flag must be set to YES.

For more information about configuring RMX system flags, refer to the
Polycom RMX Administrator’s Guide.

• You should validate that the system flag MAX_CP_RESOLUTION is set to
either HD720 or HD1080 for the 720p/60 HD conference profile.

For more information about setting this flag for large conferences, see

Configuring RMX Settings for Large Conferences on page 3-10.

Configuring the RMX Settings for 720p/30 HD Video

720p/30 HD video is supported on all RMX hardware platforms. However,
you must use one of these RMX 4000 or RMX 2000 versions:

• Version 6.0.1.12

• Version 7.0.2.68

3–6

• Version 7.1.0.121

(For specific ITP and ATX SDK compatibility information, refer to the
Software Compatibility table on page 1-2.)