Polycom 4000, (RMX) 1500, 1800, 2000 Creating Multiple Cascade Links Between Telepresence Conferences

RealPresence Collaboration Server (RMX) 1500/1800/2000/4000 Administrator’s Guide
Polycom®, Inc. 198
Creating Multiple Cascade Links Between
Telepresence Conferences
You can create multiple Cascading links between Collaboration Servers hosting conferences that include
Immersive Telepresence Rooms (ITP) such as Polycom’s OTX and RPX Room Systems.
Guidelines for Creating Multiple Cascading Links between
Conferences
●Basic Cascading topology is used. For more information see the RealPresence Collaboration Server
800s Administrator’s Guide, Basic Cascading using IP Cascaded Link.
●Multiple Cascade Links between conferences are implemented by creating a Link Participant which
consists of a main link and sub-links which are automatically generated and sequentially numbered.
For more information see Creating a Link Participant, Creating a Link Participant.
●All cascaded links must use H.323 protocol.
●Multiple Cascade Links are supported in CP conferencing mode.
●The number of cascading links is defined manually according to the maximum number of Room
System cameras in the cascaded conference.
●When the active speaker is in an Immersive Telepresence Room, Multiple Cascade Links are used,
one link for each of the Room System’s cameras.
An RPX 4xx Room System requires 4 Cascaded Links to carry the video of its 4 cameras.
An RPX 2xx Room System requires 2 Cascaded Links to carry the video of its 2 cameras.
An OTX 3xx Room System requires 3 Cascaded Links to carry the video of its 3 cameras. The
OTX Room System must be configured as Room Switch in order to send multiple streams. When
configured in CP Mode, its cameras zoom out and all 3 screens are sent as one stream.
●The number of links is defined when creating the Link Participant. Each conference in the cascade
must have a Link Participant with the same number of Multiple Cascade Links defined. Calls from
Link Participants not defined with the same number of links are rejected. Number of cascading links
is not identical for all conferences is listed as the Call Disconnection Cause. For more information see
Creating a Link Participant and Monitoring Multiple Cascade Links.
●Although it is possible to disconnect and reconnect specific Multiple Cascade Links using the
RealPresence Collaboration Server Web Client / RealPresence Collaboration Server Manager it not
advisable to do so.
If the main link is disconnected all sub-links are disconnected and deleted.
Reconnecting the main link reconnects all sub-links.
If a sub-link is disconnected it remains disconnected until it is manually reconnected.
The number of Multiple Cascade Links cannot be modified while any of the links are in a
disconnected state. All previous links must be deleted before modification is possible.
For more information see Monitoring Multiple Cascade Links.
● A Link Participant can be dragged from the address book into a conference.
If it is the first Link Participant in the conference, the number of Multiple Cascade Links defined
for the participant are created and connected.
If it is not the first Link Participant in the conference, the number of Multiple Cascade Links defined
for the participant is ignored.