Polycom® RealPresence® Collaboration Server
800s, Virtual Edition Administrator’s Guide
Trademark Information
POLYCOM® 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 may be protected by one or more U.S. and foreign patents and/or pending patent
applications held by Polycom, Inc.
This software has not achieved UC APL certification.
This document provides the latest information for security-conscious users running Version 8.1 software.
The information in this document is not intended to imply that DoD or DISA certifies Polycom RealPresence
Collaboration Server systems.
End User License Agreement
Use of this software constitutes acceptance of the terms and conditions of the Polycom® RealPresence®
Collaboration Server 800s, Virtual Edition system end-user license agreements (EULA).
The EULA for your version is available on the Polycom Support page for the Polycom® RealPresence®
Collaboration Server 800s, Virtual Edition system.
Polycom, Inc.
6001 America Center Drive
San Jose CA 95002
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.
About the RealPresence Collaboration Server 800s
Administrator’s Guide
The Polycom® RealPresence Collaboration Server 800s Administrator’s Guide provides
instructions for configuring, deploying, and administering Polycom Multipoint Control
Units (MCUs) for video conferencing. This guide will help you understand the Polycom
video conferencing components, and provides descriptions of all available conferencing
features. This guide will help you perform the following tasks:
•Customize the Collaboration Server conferencing entities such as conference Profiles,
IVR Services, Meeting Rooms, Entry Queues, etc., to your organization’s needs.
•Define Collaboration Server Users.
•Advanced conference Management
•Define Video Protocols and Resolution Configuration for CP Conferencing
•Configure Templates, the Address Book and schedule Reservations.
•Record Conferences
•Configure the Collaboration Server to support special call flows and conferencing
requirements, such as Cascading Conferences.
•Configure the Collaboration Server for special applications and needs by setting
various system flags.
•Manage and troubleshoot the Collaboration Server’s performance.
1
The Polycom® RealPresence Collaboration Server 800s Getting Started Guide provides
description of basic conferencing operations. It will help you perform the following tasks:
•Unpack the Collaboration Server system and install it on a rack.
•Connect the required cables to the Collaboration Server.
•Perform basic configuration procedures.
•Start a new conference and connect participants/endpoints to it.
•Monitor ongoing conferences
•Perform basic operations and monitoring tasks
Polycom, Inc.1-1
Polycom® RealPresence Collaboration Server 800s Administrator’s Guide
Who Should Read This Guide?
System administrators and network engineers should read this guide to learn how to
properly set up Polycom Collaboration Server systems. This guide describes administrationlevel tasks.
For detailed description of first time installation and configuration, description of the
Collaboration ServerWeb Client, and basic operation of your Collaboration Server system, see
the Polycom® RealPresence Collaboration Server 800s Getting Started Guide.
Prerequisites
This guide assumes the user has the following knowledge:
•Familiarity with Windows® XP or Windows 7 operating systems and interface.
•Familiarity with Microsoft® Internet Explorer® Version 7, 8 or 9.
•Basic knowledge of video conferencing concepts and terminology.
How This Guide is Organized
The following typographic conventions are used in this guide to distinguish types of in-text
information.
Table 1-1Typographic Conventions
ConventionDescription
BoldHighlights interface items such as menus, soft keys, flag names, and
directories. Also used to represent menu selections and text entry to the
phone.
ItalicsUsed to emphasize text, to show example values or inputs, file names and to
show titles of reference documents available from the Polycom Support Web
site and other reference sites.
Underlined Blue
Blue TextUsed for cross referenced page numbers in the same or other chapters or
<variable name>Indicates a variable for which you must enter information specific to your
>Indicates that you need to select an item from a menu. For example,
Used for URL links to external Web pages or documents. If you click on text in
this style, you will be linked to an external document or Web page.
documents. If you click on blue text, you will be taken to the referenced
section.
Also used for cross references. If you click the italic cross reference text, you
will be taken to the referenced section.
installation, endpoint, or network. For example, when you see <IP address>,
enter the IP address of the described device.
Administration > System Information indicates that you need to select
System Information from the Administration menu.
1-2Polycom, Inc.
Chapter 1-RealPresence Collaboration Server 800s Overview
Collaboration Server
Web Client
Desktop
IP Phone
Endpoints
Polycom® RealPresence
Collaboration Server 800s
LAN
Mobile
About the Polycom® RealPresence Collaboration Server
800s System
The RealPresence Collaboration Server 800s system is a high performance, scalable, IP-network
(H.323 and SIP) MCU that provides feature-rich and easy-to-use multipoint voice and video
conferencing.
The MCU can be used as a standalone device to run voice and video conferences or it can be
used as part of a solution provided by Polycom. This solution may include the following
components:
•Polycom® RSS™ 4000 - provides one-touch recording and secure playback on video
conferencing systems, tablets and smartphones, or from your Web browser.
•Polycom® Distributed Media Application™ (DMA™) - provides call control and MCU
virtualization with carrier-grade redundancy, resiliency and scalability.
•Polycom Real Presence Resource Manager - centrally manages, monitors and delivers
Cloud based Video as a Service (VaaS) and enterprise video collaboration.
•Polycom® RealPresence® Access Director™ (RPAD) - removes communication barriers
and enables internal and external teams to collaborate more easily and effectively over
video.
The following diagram describes the multipoint video conferencing configuration with the
Collaboration Server as a standalone system.
Polycom, Inc.1-3
Figure 1-1 Multipoint Video Conferencing using a Polycom Collaboration Server
Polycom® RealPresence Collaboration Server 800s Administrator’s Guide
R
The RealPresence Collaboration Server 800s unit can be controlled via the LAN by the
Collaboration Server Web Client application using Internet Explorer installed on the user’s
workstation, or the RMX Manager application. The RMX Manager can control several
Collaboration Server units. For more information about the RMX Manager see "RMX Manager Application” on page 19-1.
Network Services Guidelines
IP Networks
In the , system management and IP conferencing are performed via a single LAN port.
Management uses Lan1 and IP network Services use Lan2. When enabling multiple services,
management and the IP network service (1) share Lan1, the second IP network service (2)
uses Lan2. The networks can be separated in Maximum Security Environments.
Workstation Requirements
The Collaboration Server Web Client and RMX Manager applications can be installed in an
environment that meets the following requirements:
•Minimum Hardware – Intel® Pentium® III, 1 GHz or higher, 1024 MB RAM,
500 MB free disk space.
•Workstation Operating System – Microsoft® Windows® XP, Vista®, Windows® 7.
•Network Card – 10/100 Mbps.
•Web Browser - Microsoft® Internet Explorer® Version 7, 8 and 9.
•Collaboration Server Web client and RMX Manager are optimized for display at a
resolution of 1280 x 800 pixels and a magnification of 100%.
.Net Framework 2.0 SP1 or above is required and installed automatically.
Internet Explorer must be enabled to allow running Signed ActiveX.
If ActiveX installation is blocked please see the Polycom® RealPresence Collaboration Server 800s Administrator’s Guide, "ActiveX Bypass” on page 20-57.
Collaboration Server Web Client does not support larger Windows text or font sizes. It is
recommended to set the text size to 100% (default) or Normal in the Display settings in Windows
Control Panel on all workstations. Otherwise, some dialog boxes might not appear properly aligned.
To change the text size, select Control Panel>Display. For Windows XP, click the Appearance tab,
select Normal for the Font size and click OK. For Windows 7, click the Smaller - 100% option and
click OK.
When installing the Collaboration Server Web Client, Windows Explorer >Internet Options>
Security Settings must be set to Medium or less.
It is not recommended to run Collaboration Server Web Client and Polycom CMAD applications
simultaneously on the same workstation.
For Windows 7™ Security Settings, see the Polycom® RealPresence Collaboration Server 800s
Getting Started Guide, "Microsoft Windows 7™ Security Settings” on page 1-10.
For Internet Explorer 8 configuration, see the Polycom® RealPresence Collaboration Server 800s
Getting Started Guide, "Internet Explorer 8 Configuration” on page 1-12.
1-4Polycom, Inc.
Conference Profiles
Profiles stored on the MCU enable you to define all types of conferences. Profiles include
conference parameters such as Conferencing Mode, Conference Session Type, Conference
Line Rate, Video Layout, Encryption, Lost Packet Recovery etc.
The maximum number of Conference Profiles that can be defined is 80.
Conference Profiles are assigned to Conferences, Meeting Rooms, Reservations and Entry
Queues. The same Profile can be assigned to different conferencing entities. When modifying
the Profile parameters, the changes will be applied to all the conferencing entities to which
the profile is assigned.
Conference Profile options differ according to the selected Conferencing Mode and Conference
Type. Profiles can be defined for AVC (Advanced Video Codec) CP conferencing Mode or
SVC (Scalable Video Codec) conferencing Mode. AVC Conferencing Mode, offers two Video
session types: Continuous Presence (CP) conferences and Video Switching (VSW)
Conferences, and a special functional conference - Operator Conferences.
Conference Profiles can be 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 11, “Using Conference Templates” .
2
Conferencing Modes
The MCU system offers the following Conferencing Modes:
•Transcoding - AVC Conferencing
•Media Relay - SVC Conferencing
•Mixed Mode - Mixed AVC (CP) and SVC Conferencing
CP Transcoding - AVC-based Conferencing
A transcoded CP (Continuous Presence) conference is also described as an AVC (Advanced
Video Coding) conference. It supports the standard video protocols. In this mode, video is
received from all the endpoints using different line rates, different protocols (SIP, H.323)
and video parameters:
•Video protocols: H.263, H.264 Base and High profile and RTV
•Video Resolutions: from QCIF, CIF and up to 720p
•Frame rates up to 30 fps
All endpoints that do not support the H.264 SVC protocol such as H.263, H.264, or RTV, are
considered AVC endpoints.
The MCU process the received video, transcodes it and send the resulting video streams to
the endpoints. The video processing that is required differs according to the video session
set for the conference, with all the processing performed by the MCU. For more details, see ,
"AVC Conferencing - Video Session Types” on page 2-4.
Polycom, Inc.2-1
Polycom® RealPresence Collaboration Server 800s Administrator’s Guide
Media Relay - SVC Conferencing
Media Relay SVC Conferencing is based on the SVC (Scalable Video Codec) video protocol
and SAC audio protocol. It offers high resolution video conferencing with low end-to-end
latency, improved Error Resiliency and higher system capacities.
The Polycom multipoint media server, serves as an integrated media relay engine that
provides media streams for displaying conferences at low latency video experience in video
conferences. For more details, see , "SVC-based Conferencing” on page 2-9.
Mixed CP and SVC Conferencing
This type of conference enables participants with SVC-enabled endpoints and AVC
endpoints to participate in the same conference.
Each endpoint connects according to its capabilities. The MCU processes the AVC video
streams and converts them into SVC video Streams and relays them to the SVC participants
that constructs the video layout on the endpoint.
In the same way, the MCU processes the video streams received from the SVC participants,
converts them into AVC video and then transcodes all the video streams to compose the
video layout that is sent to the AVC endpoints.
Conferencing Capabilities in the Various Conferencing Modes
The following table summarizes the conferencing capabilities and options available in the
different Conferencing Modes.
Table 2-1Conferencing Capabilities in the Different Conferencing Modes
FeatureCP OnlyMixed CP & SVCSVC Only
Reservations
Operator
Conferences
Entry Queues
Dial Out
Cascading
IVR
Permanent
Conference
LPR
***
****
******
(AVC Only)
Reduced IVR set for
SVC endpoints
Auto Redial
2-2Polycom, Inc.
Chapter 2-Conference Profiles
Table 2-1 Conferencing Capabilities in the Different Conferencing Modes (Continued)
FeatureCP OnlyMixed CP & SVCSVC Only
Content
Presentation Mode
Lecture Mode
Same Layout
Layout Selection
Skins
Encryption
Recording
Site Names
PAll Content
Settings, All Content
Protocols
Graphics Only,
H.264 Cascade &
SVC Optimized
AVC endpoints only
AVC endpoints only
AVC recording only
AVC endpoints only
Graphics Only, H.264
Cascade & SVC
Optimized
Layout set to Auto
Layout and defined on
the endpoint
Managed by the
endpoint (not via MCU)
* Entry Queue & Destination Conference must have the same profile (i.e. SVC only to SVC only, Mixed
CP and SVC to Mixed CP and SVC)
** Only Basic Cascading is available
*** For AVC, the LPR error resiliency is used, however for SVC endpoints, new error resiliency
methods are used.
Polycom, Inc.2-3
Polycom® RealPresence Collaboration Server 800s Administrator’s Guide
AVC Conferencing - Video Session Types
All endpoints have AVC capabilities and can connect to AVC conferences running on the
MCU. AVC-based Endpoints can connect using different signaling protocols and different
video protocols.
Continuous Presence (CP) Conferencing
The dynamic Continuous Presence (CP) capability of the Collaboration Server system
enables viewing flexibility by offering multiple viewing options and window layouts for
video conferencing.
Endpoints can connect to the conference using any signaling protocol (H.323, SIP and RTV),
line rate (up to a maximum line rate defined for the conference), Video Protocol (H.261,
H.263, H.264 Base and High Profile) and at any resolution and frame rate (provided they
meet the minimum requirements set for the conference).
In Continuous Presence conferences, the MCU receives the video stream from each
endpoint at the video rate, video resolution and frame rate that it is capable of sending, and
it superimposes all the received streams into one video stream that includes the input from
the other endpoints arranges in the selected video layout.
Participants do not see themselves in the video layout. By Default, the speaker is shown in
the top left layout cell in symmetric layouts, in the larger cell in asymmetric layouts, or in
full screen. The speaker sees the previous speakers (their number depends on the number of
cells on the speaker’s layout.
The Continuous Presence video session offers 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. Each participant
can select his/her layout for viewing during the conference, as can be seen in Figure 2-1.
For conferences with more participants than display squares, the Collaboration Server
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.
2-4Polycom, Inc.
Chapter 2-Conference Profiles
Figure 2-1 AVC Continuous Presence (CP) video streams and built layouts
Video quality in Continuous Presence conferences 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. Content sharing is available in all CP conferences.
This requires extensive processing of the video sent to each participant in the conference.
The higher the video rate and resolution, the more processing power is required.
By default every conference, Entry Queue and Meeting Room has the ability to declare the
maximum CP resolution as defined for the system. This includes conferences launched by
the Collaboration Server Web Client and conferences started via the API.
CP conferencing is defined in the Conference profile by settings the following main features:
•Setting the Conferencing Mode to AVC only
•Conference Line Rate
•Video Layout
Video Protocol Support in CP Conferences
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 each of the endpoint according to he endpoint’s capabilities.
The following Video protocols are supported in CP conferences:
•H.261 - the legacy 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.
Polycom, Inc.2-5
Polycom® RealPresence Collaboration Server 800s Administrator’s Guide
•H.264 Base Profile - a video compression standard that offers improved video quality,
especially at line rates lower than 384 Kbps.
H.264 High Profile allows higher quality video to be transmitted at lower line rates.
•RTV - a video protocol that provides high quality video conferencing capability to
Microsoft OCS (Office Communicator Server) endpoints at resolutions up to HD720p30.
(SIP only).
AVC Conferencing Parameters
Basic Conferencing Parameters
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 Continuous Presence (CP) standard
conferencing. Continuous Presence conferencing enables several participants to be viewed
simultaneously and each connected endpoint uses its highest video, audio and data
capabilities up to the maximum line rate set for the conference.
The main parameters that define the quality of a video conference are:
•Line (Bit) Rate - The transfer rate of video and audio streams. The higher the line (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 Collaboration Server 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
Collaboration Server will send 4CIF (H.263) at 15fps instead of CIF (H.264) at 30fps.
— H.264 High Profile protocol provides better compression of video images in line
rates lower than 384 Kbps and it will be automatically selected for the endpoint if it
supports H.264 High Profile. If the endpoint does not support H.264 High Profile,
the Collaboration Server will try H.264 Base Profile which provides good
compression of video images in line rates lower than 384 Kbps (better than H.263
and not as good as H.264 High Profile).
— When working with Collaboration Servers at low bit rates (128, 256, or 384Kbps),
HDX endpoints will transmit SD15 resolution instead of 2CIF resolution.
When using a full screen (1x1) conference layout, the Collaboration Server 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.
•Supported resolutions:
— 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 do not
support H.264. It is only supported for conferences in which the video quality is set
to sharpness and for lines rates of 384kbps to 1920kbps.
2-6Polycom, Inc.
Chapter 2-Conference Profiles
— Standard Definition (SD) - A high quality video protocol which uses the H.264
and H.264 High Profile video algorithms. It enables compliant endpoints to
connect to Continuous Presence conferences at resolutions of 720 x 576 pixels for
PAL systems and 720 x 480 pixels for NTSC systems. For more information, see
"Video Resolutions in AVC-based CP Conferencing” on page 4-1.
— High Definition (HD) – HD is an ultra-high quality video resolution that uses he
H.264 and H.264 High Profile video algorithms. Depending on the Collaboration
Server’s Card Configuration mode compliant endpoints are able to connect to
conferences at the following resolutions:
•720p (1280 x 720 pixels)
For more information, see "Video Resolutions in AVC-based CP Conferencing” on
page 4-1.
Supplemental Conferencing Features
In addition to Standard Conferencing the following features can be enabled:
•Content Sharing (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 "Content Sharing” on page 3-1.
•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 (AVC CP Only)” on page 3-42.
•Presentation Mode (CP Conferences only) – 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.
•Encryption – Used to enhance media security at conference and participant levels. For
more information, see "Audio Algorithm Support” on page 3-25.
•Conference Recording - The Collaboration Server enables audio and video recording of
conferences using Polycom RSS recording system.
Polycom, Inc.2-7
Polycom® RealPresence Collaboration Server 800s Administrator’s Guide
Default Profile Settings in CP Conferencing Mode
The Collaboration Server is shipped with a default Conference Profile for CP conferences
which allows users to immediately start standard ongoing CP conferences. These are also
the default settings when creating a new Profile.
Table 2-2Default CP Only Conference Profile Settings
SettingVal ue
Profile NameFactory_Video_Profile
Line Rate384Kbps
Operator Conference Disabled
EncryptionDisabled
The default settings are as follows
:
Packet Loss Compensation (LPR
and DBA)
Auto Terminate
Enabled
•After last participant quits - Enabled
•When last participant remains - Disabled
Auto RedialingDisabled
Exclusive Content ModeDisabled
Enable FECCEnabled
Video QualitySharpness
Maximum ResolutionAuto
Content SettingsGraphics
Content ProtocolH.263 & H.264 Auto Selection
Presentation ModeDisabled
Same LayoutDisabled
Lecturer View SwitchingDisabled
Auto Scan IntervalDisabled (10)
Auto LayoutEnabled
Mute participants except the lecturerDisabled
SkinPolycom
IVR NameConference IVR Service
RecordingDisabled
Site Names displayDisabled
Network Services - SIP RegistrationDisabled
Network Services - Accept CallsEnabled
2-8Polycom, Inc.
SVC-based Conferencing
The SVC-Based conferencing mode provides video without transcoding by the MCU, hence
requiring less video resources while providing better error resiliency and lower latency.
Using the SVC video protocol, SVC conferences provide video bit streams at different
resolutions, frame rates and line rates to SVC-enabled endpoints with various display
capabilities and layout configurations.
In the SVC-based conference, each SVC-enabled endpoint transmits multiple bit streams,
called simulcasting, to the Polycom® RealPresence® Collaboration Server. Simulcasting
enables each endpoint to transmit at different resolutions and frame rates such as 720p at
30fps, 15fps, and 7.5fps, 360p at 15fps and 7.5fps, and 180p at 7.5fps.
The Polycom SVC-enabled endpoints (such as Polycom® RealPresence® Desktop and
Polycom® RealPresence® Mobile) compose the layout according to their layout settings and
video capabilities. This enables the MCU to send or relay the selected video streams to each
endpoint without processing the video streams and sending the composite video layout to
the endpoints.
Chapter 2-Conference Profiles
-
Figure 2-2 SVC video streams and Layouts
The video streams displayed in the conference layout on each endpoint is obtained from the
different streams received from each of the endpoints displayed in the layout. Depending on
the size of the video cell in the configured layout, the endpoint requests the video stream in
the required resolution from the RealPresence Collaboration Server. The higher the display
quality and size, the higher the requested resolution will be sent to the endpoint. The
endpoint creates the displayed layout from the different video streams it receives.
Polycom, Inc.2-9
Polycom® RealPresence Collaboration Server 800s Administrator’s Guide
For instance, an SVC endpoint might want to receive three video streams at different frame
rates and resolutions, and create a conference layout with the received video streams. Each
SVC-enabled endpoint sends encoded SVC bit streams to the MCU to relay to the other
SVC-enabled endpoints in the conference.
The endpoints encode the video in multiple resolutions and decodes the multiple video
input streams.
For example:
RealPresence mobile client (2) will transmit two resolutions; one that is suited for
RealPresence Desktop client (3) and a second that is suited for two other endpoints:
RealPresence Desktop client (4) and (1).
RealPresence Desktop client (1) transmits two resolutions; one that is suited for
RealPresence Mobile client (2) and a second that is suited for RealPresence Desktop
client (4).
The MCU determines which of the incoming resolutions to send to each endpoint. It does
not perform any SVC encoding and decoding, or any transcoding of the video streams. The
RealPresence Collaboration Server functions as the multipoint media relay to the endpoints.
For voice activated selection of the video streams, the RealPresence Collaboration Server
determines which of the incoming bit streams to send to each endpoint.
Advantages of SVC Conferencing
SVC increases the scalability of video networks and enables mass desktop video
deployments. Some of the advantages of SVC conferencing are:
•Offers high-resolution video conferencing with low end-to-end latency, improved error
resiliency and higher system capacities.
•Allows the SVC-enabled video endpoints to manage display layouts, supporting
multiple line rates, resolutions and frame rates.
•The RealPresence Collaboration Server functions as a media relay server providing low
cost production benefits. The RealPresence Collaboration Server reduces bandwidth
usage by only selecting the necessary video stream to be sent to the endpoints.
Guidelines
•SVC conferences are supported only with the following: