Version 8.3 | DOC2759A Polycom® RealPresence® SVC …support.polycom.com/.../products/network/RMX_SVC_Deployment_G… · Polycom® RealPresence® SVC-Based Conferencing Solutions

Polycom, Inc.

0[Type the document title]

Polycom Document Title 1

Version 8.3 | January 2014 | DOC2759A

Polycom® RealPresence® SVC-Based Conferencing Solutions Deployment Guide

Polycom RealPresence SVC-Based Conferencing Solutions Deployment Guide

Polycom, Inc.

© 2014 Polycom, Inc. All rights reserved.

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.

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 document provides the latest information for security-conscious users running Version 8.0 software. The information in this document is not intended to imply that DoD or DISA certifies Polycom RealPresence Collaboration Server systems.

This software has not achieved UC APL certification.

Table of Contents

Table of Contents

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1About the Polycom® RealPresence® SVC-Based Conferencing Solutions Deployment Guide ................................................................................................................. 1-1

Scope of This Document ................................................................................................ 1-1Intended Audience ......................................................................................................... 1-2Acronym Definitions ...................................................................................................... 1-2

SVC Conferencing Solution Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1SVC Conferencing Overview ................................................................................................ 2-1

Overview of SVC ............................................................................................................ 2-1Using the Polycom® RealPresence® SVC-Based Conferencing Solution ...................... 2-2

Overview of the RealPresence SVC-Based Conferencing Solution ......................... 2-2Using SVC-Enabled Endpoints in a Mixed AVC CP and SVC Conference ........... 2-4Allocating Available Bandwidth During Calls .......................................................... 2-8SVC Encryption .............................................................................................................. 2-9Optimizing Video Traffic .............................................................................................. 2-9B2B Support using the RealPresence SVC-Based Conferencing Solution .............. 2-9Detecting SVC/SIP Endpoint Disconnections ......................................................... 2-10

SVC Conferencing System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1System Architecture for Enterprise Deployment .............................................................. 3-1

User Plane ........................................................................................................................ 3-2Access Plane .................................................................................................................... 3-2Media Plane ..................................................................................................................... 3-3Call Control Plane .......................................................................................................... 3-3Management and Provisioning Plane ......................................................................... 3-4

Polycom System Environment Components ...................................................................... 3-4RealPresence Access Director ....................................................................................... 3-4RealPresence Vitualization Manager (DMA) ............................................................. 3-4RealPresence Collaboration Server (RMX) ................................................................. 3-5RealPresence Collaboration Server 800s, Virtual Edition ......................................... 3-5RealPresence Resource Manager .................................................................................. 3-5

Interoperability ....................................................................................................................... 3-6A Typical SVC-Based Conference Deployment Scenario ................................................. 3-8

SVC Support for Endpoints .......................................................................................... 3-9Deploying the RealPresence Vitualization Manager (DMA) in the Enterprise Environment .................................................................................................................... 3-9Deploying the RealPresence Resource Manager in the Enterprise Environment . 3-9

Supported Features in the RealPresence Collaboration Server ..................................... 3-10Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Configuring the RealPresence Collaboration Server (RMX) for SVC Only Conferences ............................................................................................................................. 4-1Configuring the RealPresence Collaboration Server 800s for SVC Only Conferences 4-7Configuring the RealPresence Collaboration Server (RMX) for Mixed CP and SVC Conferences ........................................................................................................................... 4-15

Polycom, Inc i


Resource Capacities for Mixed CP and SVC Conferences ......................................4-31Configuring the RealPresence Collaboration Server 800s for Mixed AVC CP and SVC Conferences ...................................................................................................................4-34

Resource Capacities for Mixed CP and SVC Conferences ......................................4-34Resource Report ............................................................................................................4-35

Configuring the RealPresence Virtualization Manager (DMA) .....................................4-36Configuring the RealPresence Distributed Media Application (DMA) for SVC-Based Conferences ...............................................................................................4-36Configuring the RealPresence Virtualization Manager (DMA) for Mixed AVC CP and SVC Conferences ...................................................................................4-37

SVC-Enabled Conference Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1Using the Polycom RealPresence SVC-Enabled Endpoints .............................................5-1Configuring the RealPresence Group Series .......................................................................5-1Making a Conference Call .....................................................................................................5-2

Point-to-Point Calls .........................................................................................................5-2Multipoint Conferences .................................................................................................5-3

SVC-Based Conferencing Solution Specifications . . . . . . . . . . . . . . . . . . . . A-1Solution Specifications ..........................................................................................................A-1Supported Conferencing Features .......................................................................................A-3Video Resource Capacity.......................................................................................................A-3MCU Supported Resolutions ...............................................................................................A-4

ii Polycom, Inc

1
SVC Conferencing Solution Overview
This chapter describes the Polycom RealPresence SVC Conferencing solution, a general description of SVC, and using the SVC conferencing solution.This chapter includes the following topics:• "SVC Conferencing Overview” • "Using the Polycom® RealPresence® SVC-Based Conferencing Solution”

SVC Conferencing OverviewThis section provides a general description of the SVC protocol and video conferencing using the SVC protocol.

Overview of SVC

Scalable Video Coding (SVC), an extension of the H.264/MPEG4-AVC video protocol, is a powerful video compression protocol that enables the standardization of encoding high-quality video streams to provide scalable adaptation to various application requirements such as display and processing capabilities of video devices, and varying transmission conditions.SVC provides network-friendly scalability at a bit-stream level with a moderate increase in encoder and decoder complexity relative to the single layer H.264 AVC protocol. SVC enables high flexibility for implementation and optimization in various application scenarios. It provides a wide-range of display and processing capabilities of target devices and varying transmission conditions for video conferencing to serve the various needs of users with different displays and CPUs (video conference endpoints, laptops, tablets, and mobile phones) connected through different network links such as LAN and wireless.In video conferencing, efficient scalable video coding provides certain benefits in the transmission of video streaming. For example, a video conference with heterogeneous clients where multiple bit streams of the same video content differing in picture size, frame rate and bit rate should be provided simultaneously. An SVC solution could make use of simulcasting, in which multiple SVC streams are made available to the different clients, allowing each client to select the picture size, frame rate, and bit rate that best suits its needs. This provides a scalable bit stream set from which representations with lower resolution or quality can be obtained. A video client with restricted resources such as display resolution, processing power, or battery power, needs to decode the lowest available bit stream.

1-1


The following diagram illustrates an example of the various devices and bandwidths that can be used in an SVC-based video conferencing environment:

Using the Polycom® RealPresence® SVC-Based Conferencing Solution

This section describes the Polycom® RealPresence® SVC-Based Conferencing solution and its components.This section includes the following topics:• "Overview of the RealPresence SVC-Based Conferencing Solution” • "Using SVC-Enabled Endpoints in a Mixed AVC CP and SVC Conference” • "Allocating Available Bandwidth During Calls” • "SVC Encryption” • "Optimizing Video Traffic” • "B2B Support using the RealPresence SVC-Based Conferencing Solution” • "Detecting SVC/SIP Endpoint Disconnections”

Overview of the RealPresence SVC-Based Conferencing Solution

The RealPresence SVC-Based conferencing solution is a powerful and innovative video conferencing mode that, in some cases, provides high-quality video streaming between endpoints with lower resolutions, frame rates, and line rates. SVC conferences also provide up to three high video capacity resolutions, 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.

1-2

Chapter 1-SVC Conferencing Solution Overview

In the SVC-based conference, each SVC-enabled endpoint transmits multiple resolutions and temporal layers, to the Polycom® RealPresence® Collaboration Server 1500/1800/2000/4000 or the Polycom® RealPresence® Collaboration Server 800s, enabling each endpoint to transmit at different resolutions and frame rates such as 180p at 7.5fps and 15fps, 360p at 7.5 fps, 15fps and 30fps, 720p at 7.5fps, 15fps, and 30fps.Polycom SVC-enabled endpoints (Polycom® RealPresence® Desktop, Polycom® RealPresence® Mobile, and the Polycom® RealPresence® Group Series 300/500/700) enable video conference layouts to be automatically assembled by the endpoint giving more flexibility to the endpoint. This enables the RealPresence Collaboration Server to send or relay the selected video streams to the endpoints without sending the entire video layout to the endpoints.The video streams displayed in the conference layout on each endpoint are 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.The following diagram illustrates how the RealPresence Collaboration Server is used as a media relay server in an SVC-based conference:

1-3


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 and receives encoded SVC bit streams to and from the RealPresence Collaboration Server.For example, the SVC stream sent from a RealPresence Desktop client (1) will transmit bit streams suited for both a RealPresence Mobile client (2) and a RealPresence Desktop client (4). The transmitted bit streams might contain a compressed video with a lower bit rate to support the capability of the receiving client.The RealPresence Collaboration Server determines which of the incoming bit streams to send to each endpoint. It does not perform any 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.

SVC video conferences provides a robust bandwidth-efficient technology that delivers a consistently high-quality user experience across networks with varying degrees of quality of service. 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 high system capacity.• Allows the SVC-enabled video endpoints to manage display layouts, support multiple

resolutions and data rates. SVC provides simulcasting at different resolutions with more layout building options on the endpoint. Flexible in-stream selection to accommodate various endpoint capabilities such as bandwidth, CPU, screen resolution, and so forth.

• Supports video layouts on two display monitors for the RealPresence Group Series endpoints.

• 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.

Using SVC-Enabled Endpoints in a Mixed AVC CP and SVC Conference

There are three types of conferences that are defined in the RealPresence Collaboration Server:• AVC CP Only• SVC Only• Mixed AVC CP and SVCIn an AVC CP Only conference, endpoints that use various protocols such as H.263, H.264 AVC, and RTV can be connected to the conference. Additionally, all Polycom SVC-enabled endpoints support the H.264 AVC protocol and can connect to an AVC CP Only conference. In an SVC Only conference, only the H.264 SVC protocol is supported. Endpoints that do not support the H.264 SVC protocol cannot connect to an SVC Only conference. However, in a mixed AVC CP and SVC conference, both AVC-capable and SVC-enabled endpoints can be supported in the same conference.

1-4


The RealPresence Collaboration Server 1500/2000/4000 in addition to the RealPresence Collaboration Server 800s - Virtual Edition, can manage a mixed AVC CP and SVC conference.In a mixed AVC CP and SVC conference, SVC endpoints transmit multiple resolutions and temporal layers to the RealPresence Collaboration Server, while AVC endpoints send only one H.264 AVC video stream to the Collaboration Server. Other endpoint types can send different kinds of video streams. The Collaboration Server relays SVC-decoded video streams to the SVC-enabled endpoints in the conference according to their display capabilities. This enables the video conference layouts to be automatically assembled by the endpoint. AVC endpoints connected to the conference send a single H.264 AVC video stream to the Collaboration Server, which is then transcoded to SVC video streams. AVC endpoints receive a single video bit stream with the defined video conference layout from the Collaboration Server. SVC-enabled endpoints receive the AVC converted video bit streams through the Collaboration Server from the AVC endpoints as a single SVC video bit stream. In this mixed AVC CP and SVC conferencing, both SVC and AVC endpoints in the conference receive the same AVC CP layout.The following diagram illustrates an example of a mixed AVC CP and SVC conferencing mode:

In this example, an SVC endpoint (1) receives three video streams at different frame rates and resolutions, and creates the conference layout with the received video streams. The video bit stream that the SVC endpoint receives from the AVC endpoint (3) is transcoded in the Collaboration Server and then encoded into an SVC bit stream in the required resolution.

1-5


Alternatively, an AVC endpoint (4) sends a single resolution video stream to the Collaboration Server. The Collaboration Server first converts the SVC bit stream into AVC, then transcodes the video received from the other endpoints to the required resolution. The Collaboration Server composes the video layout for the AVC endpoint and sends a single resolution video stream with the video layout to the participant. In the displayed example, the Collaboration Server creates different video layouts for each AVC endpoint.In a mixed AVC CP and SVC conference when packet loss occurs, the Collaboration Server uses the Polycom proprietary Lost Packet Recovery (LPR) component to recover lost packets for AVC-capable endpoints and uses the Error Resiliency and the Media Bandwidth Allocation (MBA) components to retransmit lost packets for SVC-enabled endpoints.

Video Layouts in the Mixed AVC CP and SVC Conference ModeVideo layouts used in the mixed AVC CP and SVC conferencing mode depends on the endpoint of the participant. SVC endpoints display the same video layouts whether in an SVC Only conference or in a mixed AVC CP and SVC conference. AVC endpoints display video layouts as configured by the Collaboration Server.The RealPresence Group Series endpoints can use dual monitors to display various video layouts. The video layouts for the RealPresence Group Series endpoints differ from the video layouts displayed in the Polycom SVC applications (RealPresence Desktop and RealPresence Mobile) and AVC endpoints. For a detailed description of the video layouts for the RealPresence Group Series, see "Video Layouts for the RealPresence Group Series” .Using the Polycom SVC applications and AVC-capable endpoints, the participant that is currently speaking is displayed with a colored border (orange or yellow) depending on the type of skin of the conference while the participants that are listening are displayed in the other panes.

The following table illustrates how participants are displayed in video layouts for both SVC and AVC endpoints:

AVC endpoints can use the PiP (Picture in Picture) option, which displays the participant’s self-view. This can change the video layouts view.

Table 1-1 Video Layouts for Mixed AVC CP and SVC Conferences

Number of Participants

SVC Endpoints (RPD)AVC Endpoints(Auto Layout)

2

3

1-6


4

5

6

7

8

9

10

Table 1-1 Video Layouts for Mixed AVC CP and SVC Conferences (Continued)



1-7


AVC endpoints can support up to 16 participants in a video layout.In the AVC endpoints video layout for 10 participants, the current speaker is displayed in a larger video pane. The other seven smaller panes display the participants who have previously spoken in the conference. The video layout displays the participants in speaker order - the participant who was the speaker before the other participants displayed in the video layout is not anymore displayed.In layout 2+8, the two central windows display the last two speakers in the conference: the current speaker and the “previous” speaker. To minimize the changes in the layout, when a new speaker is identified, the “previous” speaker is replaced by the new speaker while the current speaker remains in their window.

Allocating Available Bandwidth During Calls

As SVC-enabled endpoints transmit video streams to the Collaboration Server, the Collaboration Server is used as a relay server sending media streams between other SVC-enabled endpoints. Video conferences deliver media streams as datagrams (packets) across the internet and are subject to possible packet loss. Polycom’s AVC video conferencing endpoints can minimize packet loss by using Lost Packet Recovery (LPR). Additionally, the MCU reduces or increases the bandwidth, when required, to avoid network congestion using the Dynamic Bandwidth Allocation (DBA). The DBA dynamically adapts the bandwidth used to the network status.However, SVC-based conferencing is different from the traditional ACV CP conferencing as there is no transcoding of the media streams. Therefore, different error resiliency methods are used.

11

12

Table 1-1 Video Layouts for Mixed AVC CP and SVC Conferences (Continued)



1-8


Using Polycom’s Media Relay Bandwidth Allocation (MBA) algorithm, designed specifically for SVC-enabled endpoints, media streams are retransmitted when packet loss occurs because of network congestion. Similar to the DBA for AVC conferences, the MBA reduces the effective bandwidth used to avoid network congestions and decrease the packet loss percentage. This provides recovery of lost packets while maintaining and adjusting the bandwidth of the endpoint.Media Relay Bandwidth Allocation is beneficial for both constrained pipes and momentarily network congestions using the following methods:• Constrained Pipe - Identifies that available bandwidth in each direction is lower than

defined in the beginning of the call and is adjusted accordingly.• Dynamic Congestion - Measures the effective bandwidth during the call and

dynamically modifies the effective bandwidth accordingly.Using these methods to handle packet loss, MBA provides available bandwidth allocation to SVC-enabled endpoints for packet loss recovery with a quick transition to the endpoint.

SVC Encryption

SVC media streams are encrypted using SRTP protocol with AES 128 encryption. The SIP signaling is encrypted using SIP over TLS secured signaling. SVC encryption is supported in both SVC conferences and mixed AVC CP and SVC conferences.

Optimizing Video Traffic

To reduce the computational and network resources used by a sending endpoint, the MCU optimizes the amount of uplink video traffic to endpoints in the conference. Endpoints that do not need to receive video streams, such as enabling the Pause Video option, will have video streams suspended from being sent to these endpoints. The sending endpoint only transmits the negotiated simulcast video stream that is actually requested by the other endpoints in the conference. This enables the endpoint to save CPU usage needed to encode the simulcast streams in addition to the uplink bandwidth. Only streams that should be relayed to the downlink are received. The total uplink bandwidth is reduced, making the endpoints less susceptible to network problems such as jitter, packet loss, and traffic congestion.

This video traffic optimization procedure applies only to the uplink of video and has no affect on video downlink, conference behavior, audio streams, or speaker change.

B2B Support using the RealPresence SVC-Based Conferencing Solution

Business-to-Business (B2B) conferences are supported in the RealPresence SVC-based Conferencing solution. The RealPresence SVC-based conferencing solution provides multiple Polycom UC environments to communicate with each other to establish conferences using Polycom’s SVC technology. Additionally, mixed AVC CP and SVC conferences are supported for B2B conferences.

1-9


The following diagram illustrates an example of Polycom B2B support:

In this B2B diagram example, multiple enterprises can connect to conferences outside the enterprise environment. Using the Polycom® RealPresence® Access Director (RPAD) for secured firewall traversal in the enterprise environments, the environments can be configured to communicate with one another’s peers in a federated list. After the RPADs of each enterprise have been configured to accept calls from the other enterprises, the following call scenarios can be implemented:• A conference participant from one enterprise can call a Virtual Meeting Room (VMR) of

another enterprise• A participant from one enterprise can call another participant in another enterprise• A participant from one enterprise can call a remote participant in another enterprise• A remote participant from one enterprise can call a VMR of another enterprise• A remote participant from one enterprise can call a participant in another enterprise• A remote participant from one enterprise can call anther remote participant from

another enterprise

Detecting SVC/SIP Endpoint Disconnections

When an abnormal disconnection of SIP endpoints occurs because of network problems or client application failures, SIP endpoints remain connected to the conference causing connection disruptions. For example, the video freezes in the layout or blocks content for SIP endpoints when a quick re-connection is performed. It can take several minutes to detect the SIP endpoint disconnection using the SIP standard behavior.

1-10


To detect the disconnection of SIP endpoints in a reasonable amount of time, a new system flag can be defined to specify the amount of time that the MCU should wait for an RTCP or RTP message from the SIP endpoint before the endpoint starts the disconnection process. The system default value is automatically set to 20 seconds.The system flag, DETECT_SIP_EP_DISCONNECT _TIMER, contains the amount of time in seconds to wait for an RTCP or RTP message to be received from the endpoint. When the time that was set in the system flag has elapsed and no RTCP or RTP audio or video message has been received on either the audio or the video channel, the MCU disconnects the SIP endpoint from the conference. A CDR event record is created with a Call Disconnection Cause of “SIP remote stopped responding”.For more information, see the Realpresence Collaboration Server 1500/2000/4000 Administrator’s Guide.

1-11


1-12

2
SVC Conferencing System Architecture
This chapter describes the Polycom RealPresence SVC Conferencing System Architecture, a general description of SVC, and using the SVC conferencing solution.This chapter includes the following topics:• "System Architecture for Enterprise Deployment” • "Polycom System Environment Components” • "A Typical SVC-Based Conference Deployment Scenario” • "Supported Features in the RealPresence Collaboration Server”

System Architecture for Enterprise DeploymentThe following diagram illustrates the SVC-based conferencing system architecture and each plane is detailed in the sections below the diagram:

2-1


The SVC-based conferencing system architecture diagram is divided into the following sections:• "User Plane” • "Access Plane” • "Media Plane” • "Call Control Plane” • "Management and Provisioning Plane”

User Plane

The User plane describes the various endpoints that can be deployed in the RealPresence UC Platform, which can include room and mobile endpoints, Telepresence systems, voice and audio.In the SVC conferencing solution, only SVC-enabled endpoints such as RealPresence Desktop, RealPresence Mobile, and RealPresence Group Series can use the SVC encoding and decoding capabilities for compressed video files.

Access Plane

The Access plane controls the flow of data from the endpoints to the media servers. The Access plane can deploy devices such as ISDN PBX, Polycom RealPresence® Access Director™, and so forth. These devices are used to control and manage information security. Firewalls can be deployed for additional security.

The Polycom® RealPresence® Access Director™ (RPAD) enables expanded firewall traversal options for secured video conferencing connectivity within the enterprise environment or with conference participants outside the enterprise firewall.

2-2

Chapter 2-SVC Conferencing System Architecture

Alternatively, the Acme Packet SBC (Session Border Controller) can be deployed in the enterprise environment to provide secured communications across IP network borders.

Media Plane

The Media Plane contains the Polycom components such as the Polycom RealPresence Collaboration Server 1500/1800/2000/4000 (RMX) or the RealPresence Collaboration Server 800s, Virtual Edition as the MCU (Multipoint Control Unit) that enables the transcoding, relay, and collaboration of the media for SVC-based conferencing. Some components such as the Polycom RSS 4000, which is used for video recording, archiving, and streaming, are optional for this level.

In this SVC conferencing solution, the RealPresence Collaboration Server communicates with the Polycom® RealPresence® Distributed Media Application (DMA) as the SIP Server. Additionally, the RealPresence Vitualization Manager (DMA) is used to manage conferences, call control, and signaling. For more information about the RealPresence Vitualization Manager (DMA) in the SVC-based conferencing solution, see the "RealPresence Vitualization Manager (DMA)” section.

Call Control Plane

The Call Control Plane contains the RealPresence Vitualization Manager (DMA) that is responsible for call control, signaling, and acts as the conference focus. Additionally, the RealPresence Vitualization Manager (DMA) is used as the SIP Server for the SVC conferencing solution.

2-3


Management and Provisioning Plane

This level contains the Polycom® RealPresence® Resource Manager component. The RealPresence Resource Manager controls and manages all enterprise management applications and servers such as Authentication, DNS, Email, in addition to client provisioning through the enterprise Management User Interface (UI). Additionally, this level contains the enterprise Active Directory (AD), which communicates with the RealPresence Resource Manager as well as the RealPresence Vitualization Manager (DMA).

Polycom System Environment ComponentsThis section describes the Polycom RealPresence components that are used in the SVC conferencing solution. Additionally, it describes the component and endpoint interoperability.

RealPresence Access Director

The RealPresence Access Director (RPAD) is an expanded firewall traversal solution that makes it easier for conference participants, inside or outside the firewall, to video conference safely with anyone in the organization, whether they are in a secure environment at the office or an unsecure environment at home or away. For more information on using the RealPresence Access Director, see the Polycom® RealPresence® Access Director™ System Administrator’s Guide.

RealPresence Vitualization Manager (DMA)

The RealPresence Vitualization Manager (DMA), is the primary server communicating between the SVC endpoints and the RealPresence Collaboration Server (RMX). The DMA is responsible for managing conferences, call control, and signaling and acting as the conference focus. It communicates with the RealPresence Collaboration Server using the SIP protocol. Additionally, the DMA provides a REST API for creating Virtual Meeting Rooms (VMRs). Enabling SVC-based conferences on VMRs can be done by configuring the Conference Template in the DMA. For details on configuring the DMA for SVC-based conferences, see "Configuring the RealPresence Virtualization Manager (DMA)” on page 3-36.For more information on using the RealPresence Vitualization Manager (DMA), see the Polycom® DMA 7000™ System Operations Guide.

2-4


RealPresence Collaboration Server (RMX)

In the SVC conferencing environment, the Polycom RealPresence Collaboration Server (RMX) functions as a media relay server. The RealPresence Collaboration Server (RMX) does not perform encoding and decoding or any transcoding between the endpoints as it would normally do in an AVC conferencing environment. The RealPresence Collaboration Server (RMX) determines in real-time which of the incoming video streams to send to each endpoint.In addition, the RealPresence Collaboration Server (RMX) controls and manages non-SVC multipoint video and audio conferences at the same time.

For more information on the RealPresence Collaboration Server (RMX), see the Polycom® RealPresence® Collaboration Server 1500/1800/2000/4000 Administrator’s Guide.

RealPresence Collaboration Server 800s, Virtual Edition

The Polycom® RealPresence® Collaboration Server 800s, Virtual Edition, is the industry’s first multi-protocol, integrated software MCU that runs on industry-standard servers. The Collaboration Server 800s, Virtual Edition delivers open standards-based SVC that results in 3X HD multipoint video capacity for greater scalability. For SVC-based conferencing, the RealPresence Collaboration Server 800s performs similar functions as the RealPresence Collaboration Server (RMX). In addition, the Collaboration Server 800s controls and manages mixed AVC CP and SVC video conferences as well as non-SVC multipoint video and audio conferences at the same time.

The RealPresence Collaboration Server 800s system is installed on the Dell® PowerEdge™ R620 E5-2690 Rack Server.

For more information on the RealPresence Collaboration Server 800s, see the Polycom® RealPresence® Collaboration Server 800s, Virtual Edition Administrator’s Guide.

Licensing for SVC-Based ConferencingBefore using SVC-based conferencing on the RealPresence Collaboration Server 800s, it is necessary to register the product and the various software licences and obtain an Activation key. Specifically, you are required to register the Collaboration Server with an SVC license to run SVC-based conferences.For more information on registering the RealPresence Collaboration Server 800s, see the Polycom® RealPresence® Collaboration Server 800s - Virtual Edition Getting Started Guide.

RealPresence Resource Manager

The RealPresence Resource Manager system is an integrated scheduling and device management platform for video conferencing that can include these features:

To be able to handle a mixed AVC CP and SVC conference, all RealPresence Collaboration Servers (RMX) that is connected to the DMA Pool must be installed with version 8.1.

The RealPresence Collaboration Server 800s, Virtual Edition does not support the RealPresence Group Series endpoints.

2-5


• Endpoint management, including provisioning, updating, monitoring, and troubleshooting.

• Conference scheduling and monitoring on both RealPresence Resource Manager system resources and the RealPresence Vitualization Manager (DMA) system (when integrated with the RealPresence Resource Manager system).

• Conference, network device, and system monitoring and management including network typology by geography and visual alarm reporting.

• Directory and user management including address books and presence.• The Polycom RealPresence Desktop client for Windows operating systems—an easy-to-

use video and audio conferencing application that lets your users see and hear the people they call on their desktop system.

• Automatic provisioning for dynamically-managed endpoint systems and scheduled provisioning for standardly-managed and legacy endpoints.

• Automatic software updates for dynamically-managed endpoint systems and scheduled software updates for standardly-managed and legacy endpoints.

• Firewall management capabilities which enable video conferencing across firewalls.• Access to user and room directories for on-demand and scheduled calls.

Directory services include:— Presence and contact list functionality for dynamically-managed endpoints (except

for RealPresence Mobile clients).— Global Address Book for a single directory structure or Multiple Address Books for

multiple managed directories.— H.350 and LDAP directory functionality. H.350 defines a directory services

architecture for multimedia conferencing for H.323, H.320, SIP and generic protocols.

• Device monitoring and management, including bridges and access controllers such as firewalls and SBCs.

• An optional high-availability, redundant management server configuration.The RealPresence Resource Manager system supports up to 10,000 managed devices. It integrates with the RealPresence Vitualization Manager (DMA) system for call control via H.323 gatekeeper and SIP proxy functions.

For more information about the Polycom RealPresence Resource Manager, see the Polycom® RealPresence® Resource Manager™ System Operations Guide.

InteroperabilityThe following table describes the Polycom components and endpoints supported in the SVC solution:

Table 2-1 Polycom Components Supported in the SVC Solution

Component Product Version Description

RealPresence Access Director

3.0 The RealPresence Access Director is a firewall traversal solution for secured video conferencing.

2-6


RealPresence Vitualization Manager (DMA)

6.0.2 The RealPresence Vitualization Manager (DMA) is the primary server communicating between the SVC endpoints and the RealPresence Collaboration Server.

RealPresence Collaboration Server 1500/1800/2000/4000 (RMX)

8.1.7 The RealPresence Collaboration Server functions as a media relay server for SVC Only conferences. Additionally, the RealPresence Collaboration Server can run mixed AVC CP and SVC conferences.


8.1.7 The Polycom® RealPresence® Collaboration Server 800s, Virtual Edition, is a multi-protocol, integrated software MCU that runs on industry-standard servers. It is used as a media relay server for SVC-based conferences and for SVC endpoints in a mixed AVC CP and SVC conference.

RealPresence Resource Manager

7.1.1 The RealPresence Resource Manager is an integrated scheduling, provisioning, and device management platform for video conferencing.

Endpoints

RealPresence Desktop 3.0 The RealPresence Desktop application enables SVC conferences on PC desktop and laptop endpoint devices.

RealPresence Mobile 3.0 The RealPresence Mobile application enables SVC conferences on iPad tablets and iPhone devices.

RealPresence Group Series 300 / 500 / 700

4.1.1 The RealPresence Group Series systems are cutting-edge visual collaboration tools that provide high quality video and sound. The systems us the most up-to-date video communications technology to deliver the most natural video conferencing experience.Note: The RealPresence Group Series 4.0.2 is only supported in the RealPresence Collaboration Server (RMX), version 7.8.

Table 2-1 Polycom Components Supported in the SVC Solution

Component Product Version Description

To be able to handle a mixed AVC CP and SVC conference, all RealPresence Collaboration Servers (RMX) that is connected to the DMA Pool must be installed with version 8.1.7.

2-7


A Typical SVC-Based Conference Deployment ScenarioPolycom’s migration path for SVC-based conferencing enables a smooth and incremental transition for enterprises that have existing Polycom UC infrastructure such as the RealPresence Collaboration Server (RMX) or the RealPresence Collaboration Server 800s - Virtual Edition, RealPresence Vitualization Manager (DMA), and the RealPresence Resource Manager. Software upgrades to the various Polycom components are performed to provide deployment of SVC-based conferencing, enabling the enterprise to keep their initial investments and upgrading costs to a minimum. Additionally, POCN, Cisco TIP, ISDN, PSTN, and H.323 are supported in the RealPresence Collaboration Server (RMX) for AVC-based conferences.

The RealPresence Collaboration Server automatically assigns AVC and SVC resources and can be expanded as needed. Upgrading the RealPresence Collaboration Server software enables managing and operating SVC-based conferences, mixed AVC CP and SVC conferences, and AVC-based conferences.

Polycom’s SVC-based conferencing solution does not require any special training and does not require changing existing dial plans. SVC-based conferencing possess exceptional audio quality — Polycom’s proprietary Scalable Audio Coding (SAC) is supported.The following diagram illustrates an example of the Polycom SVC-based conferencing solution topology:

Cisco TIP, ISDN, and PSTN are not supported in the RealPresence Collaboration Server 800s, Virtual Edition.

SVC-based conferencing requires that the RealPresence Vitualization Manager (DMA) component be installed as a SIP Proxy server.

2-8


SVC Support for Endpoints

Supported endpoints for SVC-based conferencing are Polycom’s RealPresence Desktop for PCs and Laptops, RealPresence Mobile for iPad and iPhone, and RealPresence Group Series systems for room-based video conferencing systems. The following table describes the SVC support for each type of endpoint:

Deploying the RealPresence Vitualization Manager (DMA) in the Enterprise Environment

The RealPresence Vitualization Manager (DMA) is used as the primary video conferencing call controller. It provides conference management, call control, port signaling and functions as the conference focus. Additionally, the RealPresence Vitualization Manager (DMA) communicates with the provisioning server to configure conferences, create virtual meeting rooms (VMR), and connects participants to conferences.The RealPresence Vitualization Manager (DMA) is used as the SIP Proxy server when making SVC-based calls. Upgrading the RealPresence Vitualization Manager (DMA) software to version 5.2 enables the enterprise deployment to keep the existing Polycom DMA component and use the RealPresence Vitualization Manager (DMA) for SVC-based conferencing.For more information on the RealPresence Vitualization Manager (DMA), see the Polycom® DMA™ 7000 System Operations Guide.

Deploying the RealPresence Resource Manager in the Enterprise Environment

The RealPresence Resource Manager is an integrated scheduling and device management platform for video conferencing. The RealPresence Resource Manager handles the provisioning of the conference participant endpoints and the scheduling of video conferencing. Additionally, it communicates with the enterprise’s management applications and servers such as user authentication, DNS, and Email servers.

Table 2-2 SVC Support for Endpoints

Endpoint SVC Support

RealPresence Desktop • Sends and receives up to 720p30

• Layout up to 1+10

• Content is added to the layout (double-click to view full screen)

RealPresence Mobile • Receives up to 360p30 (for iPad2 and iPad3)

• Sends up to 270p at 15fps

• Layout up to 1+5 on iPad and up to 2x2 on iPhone

• Content is added to the layout on iPad (double-click to view full screen)

RealPresence Group Series • Sends and receives up to 720p30

• Layout up to 4 participants and/or content plus self-view using a single monitor. Using dual monitors, the active speaker or content appears on the second display.

2-9


The RealPresence Resource Manager replaces the CMA 4000/5000 in the SVC-based conferencing architecture. An existing CMA server may be used in an enterprise deployment but with limited SVC-based conferencing support - the scheduling of SVC-based conferences are not supported.

Supported Features in the RealPresence Collaboration ServerThis section describes the features supported or not supported in the varying RealPresence Collaboration Server components, between the RealPresence Collaboration Server 1500/1800/2000/4000 (RMX) and the RealPresence Collaboration Server 800s, Virtual Edition.The following table describes the features for SVC Only conferences, AVC Only conferences, and mixed AVC CP and SVC conferences for each Collaboration Server component:

Table 2-3 Supported Features Per Collaboration Server Component

Feature

RealPresence Collaboration Server (RMX) 1500/1800/2000/4000


AVC SVCMixed AVC CP and SVC

AVC CP SVCMixed AVC CP and SVC

Operator Conferences

Entry Queues 1 1 1

Reservations

Dial Out 2 2

Gateway Profiles

Cascading 3 3

IVR 4 4 4

FECC

Encryption

LPR5

SVC Error Resiliency 6

Auto Redial

Cisco TIP

Force Layout

2-10


Media Recording 7 7

Message Overlay

Site Names 8 7 7 7

Presentation Mode

Content Graphics only,H.264 Cascade & SVC Optimized

Graphics only,H.264 Cascade & SVC Optimized



Lecture Mode

Skins 9 10

1. Entry Queue and destination conference must have the same Profile (that is, SVC Only to SVC Only and AVC CP and SVC to AVC CP and SVC)

2. AVC Only participants3. Only Basic Cascading is available4. Reduced IVR set for SVC endpoints (also for Mixed AVC CP-SVC)5. For AVC endpoints, LPR is used. However, for SVC endpoints, new SVC error resiliency

methods are used.6. SVC endpoints only7. AVC recording only8. For SVC endpoints, Site Names are managed by the endpoint, not by the MCU.9. AVC Only participants10.AVC Only participants

Table 2-3 Supported Features Per Collaboration Server Component (Continued)

Feature

RealPresence Collaboration Server (RMX) 1500/1800/2000/4000


AVC SVCMixed AVC CP and SVC

AVC CP SVCMixed AVC CP and SVC

2-11


2-12

3
Configuration
This chapter describes how to configure the Polycom components for SVC-based conferencing.The RealPresence Collaboration Server (RMX), the RealPresence Collaboration Server 800s, and the RealPresence Virtualization Manager (DMA) are the only Polycom components that require configuration for SVC-based conferences. All other components do not need any special configuration.This chapter includes the following topics:• "Configuring the RealPresence Collaboration Server (RMX) for SVC Only Conferences” • "Configuring the RealPresence Collaboration Server 800s for SVC Only Conferences” • "Configuring the RealPresence Collaboration Server 800s for SVC Only Conferences” • "Resource Capacities for Mixed CP and SVC Conferences” • "Configuring the RealPresence Virtualization Manager (DMA)”

Configuring the RealPresence Collaboration Server (RMX) for SVC Only Conferences

This section describes how to configure the RealPresence Collaboration Server (RMX) for SVC-based conferences.

To define an SVC Only Profile:

1 In the RMX Management pane, click Conference Profiles.

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

3-1


The New Profile – General dialog box opens.

By default, the Profile is set to AVC Only Conferencing Mode. 3 In the Conferencing Mode list, select SVC Only to define an SVC Profile.

3-2

Chapter 3-Configuration

The profile tabs and options change accordingly and only supported options are available for selection. Unsupported options are disabled (grayed out).

4 Define the Profile name and, if required, the Profile - General parameters:

Table 3-1 New SVC 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.Note: This field is displayed in all tabs.

Line Rate Select the conference bit rate. The line rate represents the combined video, audio and Content rate.The default setting for SVC Only conference is 1920kbps.Notes:

• This field is displayed in all tabs.

3-3


5 Click the Advanced tab.

The New Profile – Advanced dialog box opens.

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.

Table 3-1 New SVC Profile - General Parameters (Continued)


3-4


6 Define the following supported parameters:

7 Click the Video Quality tab.

The New Profile – Video Quality dialog box opens.

Table 3-2 New SVC Profile - Advanced Parameters


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 participant 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). It is not recommended to select this option for SVC Conferences. Default idle time is 1 minute.

Exclusive Content Mode

When selected, Content broadcasting is limited to one participant preventing other participants from interrupting the Content broadcasting while it is active.

FW NAT Keep Alive When selected, an FW NAT Keep Alive message is sent at an interval defined in the field below the check box.

Interval The time in seconds between FW NAT Keep Alive messages.

3-5


8 Define the following parameters:

9 Click the Network Services tab.

The New Profile - Network Services tab opens.

Registration of conferencing entities such as ongoing conferences, Meeting Rooms, and SIP Factories with SIP servers is done per conferencing entity. This allows better control of the number of entities that register with each SIP server. Selective registration is enabled by assigning a conference Profile in which registration is configured for the required conferencing entities. Assigning a conference Profile in which registration is not configure for conferencing entities will prevent them from registering. By default, Registration is disabled in the Conference Profile, and must be enabled in Profiles assigned to conferencing entities that require registration.

Table 3-3 New SVC Profile - Video Quality Parameters


Content Video Definition

Content Settings Only Graphics is available in SVC Conferencing Mode for transmission of Content. It offers the basic mode, intended for normal graphics.For more information, see "H.239 Protocol” on page 4-2.

Content Protocol H.264 Cascade and SVC Optimized is the only available Content Protocol for content sharing during SVC-based conferences.In this mode, all Content is shared using the H.264 content protocol and all endpoints must use the set video resolution and frame rate (720p 5fps). Endpoints that do not support these settings cannot share content.

3-6



11 Click OK to complete the Profile definition.A new Profile is created and added to the Conference Profiles list.

Configuring the RealPresence Collaboration Server 800s for SVC Only Conferences

This section describes how to configure the RealPresence Collaboration Server 800s for SVC-based conferences.

To define an SVC Only Profile:



Table 3-4 New SVC Profile - Network Services Parameters

Parameter Description

IP Network Services:

Service Name This column lists all the defined Network Services, one or several depending on the system configuration.

SIP Registration To register the conferencing entity to which this profile is assigned with the SIP Server of the selected Network Service, click the check box of that Network Service in this column.When SIP registration is not enabled in the conference profile, the RMX's registering to SIP Servers will each register with an URL derived from its own signaling address. This unique URL replaces the non-unique URL, dummy_tester, used in previous versions.

Accept Calls To prevent dial in participants from connecting to a conferencing entity when connecting via a Network Service, clear the check box of the Network Service from which calls cannot connect to the conference.

3-7


The New Profile - General dialog box is displayed.

By default, the Profile is set to the CP and SVC conferencing mode.3 In the Conferencing Mode list, select SVC Only to define an SVC Profile.


3-8




The New Profile - Advanced dialog box is displayed.

Table 3-5 New SVC Profile - General Parameters







Line Rate Select the conference bit rate. The line rate represents the combined video, audio and Content rate.The default setting for SVC Only conference is 1920kbps.Notes: This field is displayed in all tabs.

Routing Name Enter the Profile name using the 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 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.

3-9




Table 3-6 New SVC Profile - Advanced Parameters






Interval The time in seconds between FW NAT Keep Alive messages

3-10


The New Profile - Video Quality dialog box is displayed.


9 Click the Audio Settings tab.

Table 3-7 New SVC Profile - Video Quality Parameters



Content Settings Only Graphics is available in SVC Conferencing Mode for transmission of Content. It offers the basic mode, intended for normal graphics.For more information, see the RealPresence Collaboration Server Administrator’s Guide, “H.239”.

Content Protocol H.264 Cascade and SVC Optimized is the only available Content Protocol for content sharing during SVC-based conferences.In this mode, all Content is shared using the H.264 content protocol and all endpoints must use the set video resolution and frame rate (720p 5fps). Endpoints that do not support these settings cannot share content.

3-11


The New Profile - Audio Settings dialog box is displayed.


11 Click the IVR tab.

Table 3-8 New SVC Profile - Audio Settings Parameters


Speaker Change Threshold (Sec)

Select the amount of time a participant must speak continuously before becoming the speaker. The possible values are:

• Auto (Default, 3 seconds)

• 1.5 seconds

• 3 seconds

• 5 seconds

3-12


The New Profile - IVR dialog box is displayed.



Table 3-9 New SVC Profile - IVR Parameters


Conference IVR Service

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

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.Note: This feature is implemented only if the System Flag TERMINATE_CONF_AFTER_CHAIR_DROPPED is set to YES.

3-13


The New Profile - Network Services dialog box is displayed.

Registration of conferencing entities such as ongoing conferences, Meeting Rooms, and SIP Factories with SIP servers is done per conferencing entity. This allows better control of the number of entities that register with each SIP server. Selective registration is enabled by assigning a conference profile in which registration is configured for the required conferencing entities. Assigning a conference profile in which registration is not configure for conferencing entities will prevent them from registering. By default, Registration is disabled in the Conference Profile, and must be enabled in the Conference Profiles assigned to conferencing entities that require registration.





Service Name This column lists all the defined Network Services, one or several depending on the system configuration


3-14


15 Click OK to complete the Conference Profile definition.

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

Configuring the RealPresence Collaboration Server (RMX) for Mixed CP and SVC Conferences

To define a mixed AVC CP and SVC Profile:



The New Profile – General dialog box is displayed.

By default, the Profile is set to AVC CP (Continuous Presence). 3 In the Conferencing Mode list, select CP and SVC to define a mixed AVC CP and SVC

conference.




3-15




Table 3-11 New AVC CP and SVC Profile - General Parameters







Line Rate Select the conference bit rate. The line rate represents the combined video, audio and Content rate.The default setting for an AVC CP and SVC conference is 1920kbps.Notes:

• This field is displayed in all tabs.

3-16



The New Profile – Advanced dialog box is displayed.

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

Table 3-11 New AVC CP and SVC Profile - General Parameters (Continued)


3-17



Table 3-12 New AVC CP and SVC Profile - Advanced Parameters


Encryption Select one of the following types of encryption for the conference:

• Encrypt All - Encryption is enabled for the conference and all conference participants must be encrypted.

• No Encryption - Encryption is disabled for the conference.

• Encrypt when possible - enables the negotiation between the MCU and the endpoints and let the MCU connect the participants according to their capabilities, where encryption is the preferred setting. For connection guidelines see "Mixing Encrypted and Non-encrypted Endpoints in one Conference” . in the RealPresence Collaboration Server (RMX) Administrator’s Guide.

For more information, see "Packet Loss Compensation (LPR and DBA) AVC CP Conferences” in the RealPresence Collaboration Server (RMX) Administrator’s Guide.

Packet Loss Compensation (LPR and DBA)

For AVC endpoints only. When selected, Lost Packet Recovery creates additional packets that contain recovery information used to reconstruct packets that are lost during transmission.

For more information, see "Packet Loss Compensation (LPR and DBA) AVC CP Conferences” in the RealPresence Collaboration Server (RMX) Administrator’s Guide.





Interval The time in seconds between FW NAT Keep Alive messages.

3-18



The New Profile – Video Quality dialog box is displayed.


Table 3-13 New AVC CP and SVC Profile - Video Quality Parameters


People Video Definition

Maximum Resolution For AVC endpoints only. This setting overrides the Maximum Resolution setting of the Resolution Configuration dialog box.The administrator can select one of the following Maximum Resolution options:

• Auto (default) - The Maximum Resolution remains as selected in the Resolution Configuration dialog box.

• CIF

Maximum Resolution settings can be monitored in the Profile Properties - Video Quality and Participant Properties - Advanced dialog boxes.Notes:The Resolution field in the New Participant - Advanced dialog box allows Maximum Resolution to be further limited per participant endpoint.The Maximum Resolution settings for conferences and participants cannot be changed during an ongoing conference.

3-19


9 Click the Video Settings tab.

The New Profile – Video Settings dialog box is displayed.


Content Settings Graphics is the only option used for mixed AVC CP and SVC conferences:

• Graphics — basic mode, intended for normal graphics

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

For a detailed description of each of these options, see "Content Sharing Parameters in Content Highest Common (Content Video Switching) Mode” in the RealPresence Collaboration Server (RMX) Administrator’s Guide.

Content Protocol H.264 Cascade and SVC Optimized is the only option used for mixed AVC CP and SVC conferences. All Content is shared using the H.264 content protocol and is optimized for use in Cascaded Conferences.When Multiple Resolutions is selected, this feature is hidden.

Content Resolution Content Resolution is always set to 720 5fps and the bit rate is always set to 128 Kbps for mixed AVC CP and SVC conferences.

Table 3-13 New AVC CP and SVC Profile - Video Quality Parameters (Continued)


3-20



11 Click the Audio Settings tab.

Table 3-14 New AVC CP and SVC Profile - Video Settings Parameters


Same Layout For AVC endpoints only. Select this option to force the selected layout for all AVC participants in a conference (non-cascaded). This displays the same video stream to all AVC participants and personal selection if the video layout is disabled. In addition, if participants are forced to a video layout window, they can see themselves using the PiP self-view.

Auto Layout For AVC endpoints only. When selected, the system automatically selects the conference layout based on the number of participants currently connected to the conference. When a new video participant connects or disconnects, the conference layout automatically changes to reflect the new number of video participants.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” in the RealPresence Collaboration Server (RMX) Administrator’s Guide.Note: In some cases, the default layout automatically selected for the conference contains more cells than the number of connected participants, resulting in an empty cell. For example, if the number of connected participants is 4, the default layout is 2x2, but as only 3 participants are displayed in the layout (the participants do not see themselves), one cell is empty.

3-21


The New Profile - Audio Settings tab is displayed.


13 For AVC endpoints only. Click the Skins tab to modify the background and frames.

The New Profile - Skins dialog box is displayed.

Table 3-15 New AVC CP and SVC Profile - Audio Settings Parameters


Speaker Change Threshold (Sec)

The Speaker Change Threshold is the amount of time a participant must speak continuously before becoming the speaker. When defining or editing a conference profile, you can define the Speaker Change Threshold.Select the desired threshold:

• Auto (Default, 3 seconds)

• 1.5 seconds

• 3 seconds

• 5 seconds

Auto mute noisy endpoints

For AVC endpoints only. When selected, this option automatically mutes noisy endpoints that other participants can hear such as background noises, typing keyboard noises, and so forth.

3-22


14 Select the desired Skin.

15 Click the IVR tab.

The New Profile - IVR dialog box is displayed.

3-23



17 Optional. Click the Recording tab to enable conference recording with Polycom RSS 2000/4000.

The New Profile - Recording tab is displayed.

Table 3-16 New AVC CP and SVC Profile - IVR Parameters


Conference IVR Service

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

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.Note: This feature is implemented only if the System Flag TERMINATE_CONF_AFTER_CHAIR_DROPPED is set to YES.

Terminate Conference after Chairperson Drops

This option is only available when the Conference Requires Chairperson is selected. When this option is selected, the conference terminates after the chairperson has disconnected from the conference.

3-24



19 For AVC endpoints only. Click the Site Names tab.

Table 3-17 New AVC CP and SVC Profile - Recording Parameters


Enable Recording Select this check box to enable the Recording settings. If no Recording Links are found an error message is displayed.Note: Recording is not supported in SVC Only mode.

Recording Link Select the Recording Link to be used for conference recording.Recording Links defined on the RealPresence Collaboration Server can be given a descriptive name and can be associated with a Virtual Recording Room (VRR) saved on the Polycom® RSS™ 4000 Version 6.0 Recording and Streaming Server (RSS). For more information see the “Recording Conferences” chapter in the RealPresence Collaboration Server (RMX) Administrator’s Guide.

Start Recording Select one of the following:

• Immediately – conference recording is automatically started upon connection of the first participant.

• Upon Request – the operator or chairperson must initiate the recording (manual).

Audio Only Select this option to record only the audio channel of the conference.Note: This option can be used only if there are Voice ports configured in the Video/Voice Port Configuration. For more information, see "Video/Voice Port Configuration” in the RealPresence Collaboration Server (RMX) Administrator’s Guide.

Display Recording Icon

This option is automatically selected to display a Recording Indication to all conference participants informing them that the conference is being recorded.

The Recording participant does not support H.264 High Profile. If recording a conference that is set to H.264 High Profile, the Recording participant connects as Audio Only and records the conference Audio.

3-25


The New Profile - Site Names dialog box is displayed.

Using the Site Names dialog box, you can control the display of the site names by defining the font, size, color, background color and transparency, and position within the Video Window. For a detailed description of the site names options, see "Site Names Definition” in the RealPresence Collaboration Server (RMX) Administrator’s Guide.

20 For AVC Endpoints only, define the following parameters:

Table 3-18 Site Names Parameters - for AVC Endpoints Only

Field Description

Display Mode Select the display mode for the site names:

• Auto - Display the Site Names for 10 seconds whenever the Video Layout changes.

• On - Display the Site Names for the duration of the conference.

• Off (default) - Do not display the Site Names.

Note: The Display Mode field is grayed and disabled if Video Switching mode is selected in the Profile - General tab. If Display Mode is Off, all other fields in this tab are grayed and disabled.Selecting Off enables Video Switching for selection in the Profile - General tab (if the conference is not already ongoing).

3-26


Font Size Click the arrows to adjust the font size (in points) for the Site Names display.Range: 9 - 32 pointsDefault: 12Note: Choose a Font Size that is suitable for viewing at the conference’s video resolution. For example, if the resolution is CIF, a larger Font Size should be selected for easier viewing.

Background Color Select the color of the Site Names display text.The color and background for Site Names display text is dependent on whether a Plain Skin or a Picture Skin was selected for the conference in the Profile - Skins tab.The choices are:

Note: Choose a Background Color combination that is suitable for viewing at the conference’s video resolution. At low resolutions, it is recommended to select brighter colors as dark colors may not provide for optimal viewing.

Table 3-18 Site Names Parameters - for AVC Endpoints Only (Continued)

Field Description

Plain Skin Picture Skin

Default:White Text No Background

(For contrast, no background is shown as black when the text is white.)

Default:White TextRed Background

3-27


Display Position Select the pre-set position for the display of the Site Names.

Selection Site Names Position

LeftTop (Default)

Top

RightTop

LeftMiddle

RightMiddle


Field Description

3-28



Display Position(cont.)

LeftBottom

Bottom

RightBottom

Custom The current Site Names display position becomes the initial position for Site Names position adjustments using the Horizontal and Vertical Position sliders.

Horizontal Position Move the slider to the left to move the horizontal position of the Site Names to the left within the Video Windows.Move the slider to the right to adjust the horizontal position of the Site Names to the right within the Video Windows.

Note: Use of these sliders will set the Display Position selection to Custom.

Vertical Position Move the slider to the left to move the vertical position of the Site Names upward within the Video Windows.Move the slider to the right to move the vertical position of the Site Names downward within the Video Windows.


Field Description

3-29


The New Profile - Network Services tab is displayed.

Registration of conferencing entities such as ongoing conferences, Meeting Rooms, and SIP Factories with SIP servers is done per conferencing entity. This allows better control of the number of entities that register with each SIP server. Selective registration is enabled by assigning a conference Profile in which registration is configured for the required conferencing entities. Assigning a conference Profile in which registration is not configure for conferencing entities will prevent them from registering. By default, Registration is disabled in the Conference Profile, and must be enabled in Profiles assigned to conferencing entities that require registration.


Table 3-19 New AVC CP and SVC Profile - Network Services Parameters



Service Name This column lists all the defined Network Services, one or several depending on the system configuration.


3-30


23 Click OK to complete the Profile definition.A new Profile is created and added to the Conference Profiles list.

Resource Capacities for Mixed CP and SVC Conferences

In a mixed CP and SVC conference, video resources are allocated according to the MCU type and the translation pools (AVC to SVC and SVC to AVC) used to convert video streams. Translation pools are dynamically allocated, when the conference becomes a mixed CP and SVC conference; resources are not released when the conference stops being a mixed CP and SVC conference. The translation pools send one SVC to AVC stream with a resolution of 360p, two AVC to SVC streams with a resolution of 360p and 180p for AVC HD endpoints, and one video stream with a resolution of 180p for AVC SD endpoints. When a video stream with a resolution of 360p is not available, a video stream with a resolution of 180p is sent instead.Translations between different endpoints can be done without using the highest resolution, thus saving translation resources. CP video layouts in mixed CP and SVC conferences support the standard resolutions as in normal CP conferences.Taking these factors into consideration and the type of MCU deployed in the environment, the resource capacities for a mixed CP and SVC conference can vary.The following table describes an example of the resource capacity allocations for the RealPresence Collaboration Server (RMX):


Table 3-19 New AVC CP and SVC Profile - Network Services Parameters (Continued)


System Resources are now reported in terms of HD720p30 CP ports. One HD video port equals 3 CIF video ports.

Table 3-20 Resource Capacity Allocations

Resource Type

Number of Available Ports

RMX 20002x MPMx

RMX 40004x MPMx

Mixed CP and SVC (HD)(Example)

20 AVC90 SVC

40 AVC180 SVC

HD720p30 60 120

SD (@ 30 fps) 120 240

SVC Only 180 360

CIF (@ 30 fps) 180 360

3-31


The first four resource types in the resource capacity allocations table are endpoints in a CP only conference or a mixed CP and SVC conference before the actual resource allocations occur.In a mixed CP and SVC conference, video resources are used according to the amount of both AVC and SVC participants in the conference and according to the actual type of the conference - mixed CP and SVC conferences or CP only conferences. The ratio of resources in a mixed conference is one AVC HD (720p30) video resource to three SVC video resources, meaning for each AVC HD video resource, three SVC video resources can be allocated.In this resource capacity allocations example, the mixed CP and SVC conference can allocate a combination of AVC and SVC ports depending on the endpoints that are defined in the actual conference. For example, a conference can be defined as a mixed CP and SVC conference but will only allocate resources as a mixed conference when both AVC and SVC endpoints join the conference. When there are only one resource type of endpoints participating in the conference, such as AVC or SVC, the resource allocations are assigned according to the type of endpoint. For instance, a mixed CP and SVC conference with HD endpoints assigned, can have 60 or 120 ports allocated depending on the server configuration. When an SVC endpoint joins the conference, the conference becomes an actual mixed conference and the resource allocations are divided between the AVC and SVC endpoints. The Resource Report will reflect this by showing an increase in the resource usage.The following diagram illustrates the amount of AVC to SVC port resources that are used in an actual mixed CP and SVC conference:

When viewing the Collaboration Server resource report for mixed CP and SVC conferences, the resource allocations are described in AVC HD720p30 units. A port ratio of 1 AVC HD port will equal 2 AVC SD ports, which equals 3 SVC ports (in a non-mixed conference). When the Collaboration Server is reporting the available capacity, it will appropriately round up the remaining capacity to the nearest whole value of available ports. For example, one SVC endpoint in a conference is equal to 1/3 of the resource value. The resource report displays this as one full resource used. Two SVC endpoints is equal to 2/3 of the resource value. Therefore, the resource report displays this as one full resource used, and so forth.

3-32


The following table explains the actual resource capacity utilization for both CP only and mixed CP and SVC conferences:

* Resources are consumed at this rate only after the conference contains mixed endpoints.

The Resource Capacity Utilization table indicates the total amount of ports used for each port type for one MPMx media board in full capacity.The following diagram displays the RealPresence Collaboration Server (RMX) Resource Report, displaying a resource graph that indicates the number of voice and video ports that are available or occupied in the MCU.

Table 3-21 Resource Capacity Allocation Per Port Type

Port Type Non-Mixed ConferencesMixed CP and SVC

Conferences

AVC HD 1 1.5 *

AVC SD 0.5 0.75 *

AVC CIF 0.333 0.75 *

SVC 0.333 0.333

Table 3-22 Resource Capacity Utilization Per Port Type per MPMx Card

Port TypeMaximum Ports in Non-mixed

ConferencesMaximum Ports in Mixed CP

and SVC Conferences

Maximum number of licences

30

AVC HD 30 20

AVC SD 60 40

AVC CIF 90 40

SVC 90 90

3-33


Configuring the RealPresence Collaboration Server 800s for Mixed AVC CP and SVC Conferences

The RealPresence Collaboration Server 800s can be configured for mixed AVC CP and SVC conferences in addition to AVC CP only conferences.

To configure a mixed AVC CP and SVC conference:1 In the RealPresence Collaboration Server Management pane, click Conference Profiles.


The New Profile - General dialog box is displayed.

By default, the Profile is set to the CP and SVC conferencing mode.3 In the Conferencing Mode list, ensure that CP and SVC is selected to define a mixed CP

and SVC conference.

4 Define the rest of the Conference Profile parameters for the mixed AVC CP and SVC conference as detailed in the Polycom RealPresence Collaboration Server 800s Administrator’s Guide.

Resource Capacities for Mixed CP and SVC Conferences

In a mixed AVC CP and SVC conference, video resources are used according to the amount of both AVC and SVC participants connected to the conference. The ratio of resources in a conference is one AVC HD (720p30) video resource to three SVC video resources, meaning that three SVC video endpoints will consume one AVC HD resource.

3-34


The following table describes the resource capacity allocations for the RealPresence Collaboration Server 800s per resource type.

For example, the RealPresence Collaboration Server 800s with 20 AVC HD resources can support a single conference with 10 HD (720p) AVC endpoints and 30 HD (720p) SVC endpoints.The following figure illustrates the number and ratio of AVC to SVC endpoints that can be simultaneously connected to the MCU.

Figure 3-1 Resources - AVC to SVC Endpoint Ratio

Resource Report

When viewing the Collaboration Server resource report, the resource allocations are described in AVC SD/CIF units. A port ratio of 1 AVC HD port will equal 2 AVC SD ports, which equals 3 SVC ports. This signifies that when the Collaboration Server is reporting the available capacity, it will appropriately round up the remaining capacity to the nearest whole value of available ports. For a detailed description of the Collaboration Server resource report, see the Polycom® RealPresence® Collaboration Server Administrator’s Guide.

Table 3-23 Resource Capacity per Resource Type

Resource Type Number of Resources

VoIP Ports 120

CIF Ports 40

SD Ports (4CIF) 40

HD 720p30 Ports 20

VGA RTV Ports 20

SVC Only Ports 60

3-35


Configuring the RealPresence Virtualization Manager (DMA)This section describes how to configure of the RealPresence Distributed Media Application (DMA) for SVC-Based conferences and mixed CP and SVC conferences.

Configuring the RealPresence Distributed Media Application (DMA) for SVC-Based Conferences

To configure the RealPresence Virtualization Manager (DMA) for SVC-based conferences:1 In the Add Conference Template dialog box, click RMX General Settings.

2 In the Conference mode setting, click the drop-down menu arrow and select SVC only.

3 Select any of the other settings that is relevant for the conference.

4 Click OK.

DMA 6.0.2 support AVC only, SVC only, and Mixed AVC and SVC conference modes.

Selecting this setting disables most of the other template settings such as Encryption, LPR, and TIP compatibility.

3-36


Configuring the RealPresence Virtualization Manager (DMA) for Mixed AVC CP and SVC Conferences

To configure the RealPresence Virtualization Manager (DMA) for mixed AVC CP and SVC conferences:1 In the Add Conference Template dialog box, click RMX General Settings.

2 In the Conference mode setting, click the drop-down menu arrow and select Mixed AVC and SVC.

3 Select any of the other settings that is relevant for the conference.

4 Click OK.

3-37


3-38

4
SVC-Enabled Conference Calls
This chapter describes how to place an SVC-enable conference call using the RealPresence SVC-Based conferencing solution. It describes the conference call from the end-user perspective in addition to describing the SVC-enabled conference established in the RealPresence Collaboration Server and the RealPresence Distributed Media Application (DMA). Additionally, the chapter describes the various features that can be used in an SVC-enabled conference.

Using the Polycom RealPresence SVC-Enabled EndpointsThe Polycom RealPresence SVC-enabled endpoints provide full support for SVC-based conferences in addition to AVC-capable conferences.The RealPresence SVC-enabled endpoints include:• Polycom® RealPresence™ Desktop

— RealPresence Desktop supports Microsoft Windows and MAC (OSX).• Polycom® RealPresence™ Mobile

— The Polycom RealPresence Mobile application provides video conferencing for tablets and smartphones, extending video beyond conference rooms, enabling organizations to deliver video collaboration to more users in more environments.

• Polycom® RealPresence™ Group Series— The Polycom RealPresence Group Series systems are cutting-edge visual

collaboration tools that provide high quality video and sound. The systems use the most up-to-date video communications technology to deliver the most natural video conferencing experience.

Configuring the RealPresence Group SeriesYou can configure the RealPresence Group Series to make and receive SVC-enabled calls when the Group Series system is connected to an SVC-capable bridge. You can enable or disable SVC calls in the Group Series systems from the Dialing Preferences screen in the administrators web interface.

To enable or disable SVC calls:1 In the RealPresence Group Series administrators web interface, navigate to Admin

Settings > Network > Dialing Preference.

4-1


2 Under Dialing Options, select one of the following settings from the Scalable Video Coding Preference (H.264) list:

Making a Conference CallThere are several types of conferences:• "Point-to-Point Calls” • "Multipoint Conferences”

Point-to-Point Calls

Using the RealPresence Desktop or the RealPresence Mobile applications, the participant can initiate a point-to-point call by:• Selecting a participant from the Contacts list (LDAP access from the provisioning server

or a manually entered contact)• Selecting a participant from the Recent Calls list• Typing the IP address of the participant to be called.When the RealPresence Desktop is provisioned using the RealPresence Resource Manager, the Contacts list is comprised of the LDAP directory and contacts that have been manually added. When selecting a participant from the Contacts list, the call is started when the called participant answers the call. The RealPresence® Access Director™, the Polycom secure firewall solution, enables high-quality and secure unified communications with remote enterprise users and guest users in the enterprise. In this solution, the RealPresence Access Director system, acting as the Session Border Controller (SBC) for the enterprise IP network, secures the borders to the enterprise IP network, the private VPN, and the Internet. This allows for secure communication between the enterprise environment and enterprise remote users.The RealPresence Access Director enables external, remote users via designated video endpoints such as smartphones and tablets, to make an LDAP connection to the RealPresence Access Director system which are then proxied to the internal LDAP server.

Table 4-1 SVC Preference Options

SVC Setting Description

SVC then AVC This is the default setting. This setting allows the system to determine whether the Virtual Meeting Room (VMR) is defined as SVC or AVC and enters the calls accordingly. When the conference is an SVC-capable conference, the system defines the call as SVC. When the conference does not have SVC capabilities, the system defines the call as AVC.

AVC Only This option disables SVC and allows AVC only calls.

SVC point-to-point SIP calls are only supported by the RealPresence Desktop or RealPresence Mobile applications.

4-2

Chapter 4-SVC-Enabled Conference Calls

The RealPresence Distributed Media Application (DMA) establishes point-to-point conferences within the enterprise network and is used as the SIP proxy server between the conference participants. The RealPresence Distributed Media Application (DMA) provides call control for point-to-point calls. When the point-to-point video call is sent to an endpoint outside the enterprise firewall, SIP signaling and media are sent through the RealPresence Access Director.

Video Layouts for Point-to-Point CallsThe video layout for point-to-point calls contain both participants in the layout view. The smaller pane displays the local participant (self-view).The following table illustrates how participants are displayed in the video layout of a point-to-point call:

Multipoint Conferences

For SVC-based conferences, only SVC-enabled endpoints, such as the RealPresence Desktop, the RealPresence Mobile, and the RealPresence Group Series applications, can connect to a configured SVC Only conference on the RealPresence Collaboration Server and the RealPresence Distributed Media Application (DMA). Non-SVC endpoints are not able to connect to SVC Only conferences.SVC-based conferences are established on the RealPresence Distributed Media Application (DMA) through Virtual Meeting Rooms. Participants to SVC-based conferences can dial-in to the Virtual Meeting Room using a SIP URI, SIP IP address, or a Virtual Meeting Room number. Examples of these can be:• SIP URI — [email protected]• SIP IP Address — [email protected]• Meeting Room — 724999The RealPresence Collaboration Server 800s enables an SVC participant to directly dial-in to a Meeting Room or an ongoing conference or dial-in through an Entry Queue locally defined on the Collaboration Server 800s.VMRs can also be located in the Contacts list when the RealPresence Resource Manager is connected with the enterprise LDAP. The RealPresence Resource Manager controls the provisioning of the enterprise computers.The RealPresence Distributed Media Application (DMA) is used for call control, SIP proxy, and conference management. The RealPresence Distributed Media Application (DMA) allocates a RealPresence Collaboration Server for sending and receiving video streams to and from the SVC-enabled endpoints. When the RealPresence Collaboration Server is allocated, it detects the type of conference - SVC Only or Mixed CP and SVC. In an SVC

Table 4-2 Point-to-Point Video Layout


RealPresence Desktop RealPresence Mobile

1 - 2

4-3


Only conference, the RealPresence Collaboration Server verifies that all endpoints support SVC capabilities and allows SVC-enabled endpoints to connect. When an endpoint in the conference is not an SVC endpoint, the RealPresence Collaboration Server rejects the call and does not allow it to connect to the conference. In a mixed CP and SVC conference, both AVC-capable and SVC-enabled endpoints can connect to the conference. The conference uses the SVC protocol until an AVC-capable endpoint joins the conference. The conference then uses the AVC protocol.The RealPresence Collaboration Server provides the information on the SVC streams for each endpoint in the SVC-enabled conference and negotiates the required video streams to be sent to the endpoints.Using the RealPresence Desktop, the RealPresence Mobile, or the RealPresence Group Series applications, the user is able to dial to VMRs or other participants, view other participants in a continuous presence video layout, control video suspend and resume (not supported in the RealPresence Group Series), and audio mute, and share content.

Video LayoutsDepending on the number of participants in the multipoint conferencing, video layouts are automatically configured for displaying on the participant endpoint. The participant that is currently speaking is displayed in the larger video pane and the previous active speakers are displayed in the smaller video panes.Using the RealPresence Desktop and the RealPresence Mobile applications, conference participants can control the appearance of video layouts. The participant can select a video frame in the video layout to enlarge the frame for a full frame view with a higher resolution.Video layouts using the RealPresence Group Series systems are different than the RealPresence Desktop and RealPresence Mobile applications. The RealPresence Group Series systems can support a single monitor or dual monitors. Dual monitors provide more flexibility in the video layouts, enabling you to view the active speaker or content on the second monitor. For more information on the RealPresence Group Series video layouts, see "Video Layouts for the RealPresence Group Series” .The following video layouts are used in an SVC-enabled conference and a mixed CP and SVC conference using the RealPresence Desktop or RealPresence Mobile clients. The following table illustrates how participants are displayed in video layouts in an SVC-based conference:

Table 4-3 Video Layouts for Multipoint Conferences



2

4-4


3

4

5

6

7

8

9

Table 4-3 Video Layouts for Multipoint Conferences (Continued)



4-5


Video Layouts for the RealPresence Group SeriesThe RealPresence Group Series can be configured for SVC or AVC conferences. For more information on configuring the RealPresence Group Series, see "Configuring the RealPresence Group Series” .Video layouts in the RealPresence Group Series depends on whether you are using a single video display monitor or dual video display monitors. Self view can be displayed or hidden by using the RealPresence Group Series systems settings.The RealPresence Group Series can support up to 16 participants in an AVC Only conference.

Using a Single Video Display Monitor

The following table displays the video layouts without content using a single monitor:

10

11

Table 4-3 Video Layouts for Multipoint Conferences (Continued)



For the Group Series 300 and the Group Series 500 endpoints, when there are more than six participants in a conference, the video layouts will remain the same layout as specified for six participants.

Table 4-4 RealPresence Group Series Video Layouts - Single Monitor without Content


Self View On Self View Off

1 - 2

3

4-6


The following table displays the video layouts for a single video display monitor with content.

4

5

6

7

8 or more

Table 4-5 RealPresence Group Series Video Layouts - Single Monitor with Content



1 - 2

Table 4-4 RealPresence Group Series Video Layouts - Single Monitor without Content (Continued)



4-7


Using Multiple Video Display Monitors

Multiple video display monitors can be used with the RealPresence Group Series systems to display participants and content in a conference. When no content is displayed, the video display monitors display the current speaker on one monitor and the last speakers on the other monitor.

3

4

5

6

7

8 or more

Table 4-5 RealPresence Group Series Video Layouts - Single Monitor with Content (Continued)



4-8


The following table displays the video layouts for dual video display monitors with content.

Table 4-6 RealPresence Group Series Video Layouts - Dual Monitors with Content



1-2

3

4

5

6

7

8 or more

4-9


The following table displays the video layouts for dual video display monitors without content:

Table 4-7 RealPresence Group Series Video Layouts - Dual Monitors without Content



3

4

5

6

7

8 or more

4-10

A
SVC-Based Conferencing Solution Specifications
Solution SpecificationsThe following table describes the SVC-based conferencing solution supported capabilities:

Table A-1 Supported Solution Capabilities

Feature Description

Video Protocol H.264 SVC, Baseline Profile

Video ResolutionsFor details, see:• "MCU Supported Resolutions” on page A-4

Audio Protocols The following protocols are supported for SVC conferencing:

• SAC LPR (multipoint only)

Signaling • SIP over TCP (Recommended)

• SIP over UDP

• SIP over UDP/TLS

Media Quality Low Latency, VID & AUD error resiliency

Media Encryption Supported for SVC conferences and mixed AVC CP and SVC conferences:

• SRTP - AES 128

• SIP over TLS secured signaling

Additional Video RFC Support

• PLI (Picture Loss Indication, RFC 4585)

• FIR (Full Intra Request, RFC 5104)

A-1


Video Layout • RealPresence Desktop:

• 1+3

• 1+4

• 1+7

• 1+11

• RealPresence Mobile (iPad):

• 1+3

• 1+5

• RealPresence Mobile (iPhone):

• 1x1

• 1x2

• 1+2

• 2x2

Note: For asymmetric layouts such as 1+3 and 1+4, the first digit denotes the current speaker in the conference. The second digit denotes the number of participants including the local (self view).• RealPresence Group Series:

For a description of video layouts for the Group Series, see "Video Layouts for the RealPresence Group Series” .

Table A-1 Supported Solution Capabilities (Continued)

Feature Description

A-2

Appendix A -SVC-Based Conferencing Solution Specifications

Supported Conferencing Features• Multipoint Video H.264 SVC call between SVC endpoints and a single MCU• Content can be shared.

Video Resource Capacity:

* Collaboration Server 1800: For a maximum license of 75 ports.** Collaboration Server 2000/4000: For a maximum license of 65 ports.

• The Polycom RealPresence Distributed Media Application (DMA) provides the following SIP Proxy and Registrar services to registered clients:— SIP Registration— Point-to-point conferencing— Alias resolution— Dial Plan— Hunt Groups— Call Forwarding— External SIP Proxy and SBC support— Multipoint conferencing using up to 64 RealPresence Collaboration Servers— 5,000 concurrent calls— 15,000 registrations

When running an SVC-based conference in the RealPresence Collaboration Server (RMX), all SVC participants in the same conference must reside on the same MPMx media card.

Table A-2 Video Resources Capacity

Resource Type

Maximum Possible Resources per Collaboration Server Model

1500 1800* 2000** 4000**800s

MPMx 1 card 3 cards MPMx MPMRx-D MPMx MPMRx-D

HD720p30 30 25 75 60 130 120 260 20

SVC 90 75 225 180 390 360 780 60

A-3

Chapter A-Appendix - SVC-Based Conferencing Solution Specifications

MCU Supported ResolutionsThe MCU automatically selects the resolution and frame rate according to the conference line rate. Table A-3 details the maximum resolution and frame rates supported by the MCU for each conference line rate. The actual video rate, resolution and frame rates displayed on each endpoints is determined by the endpoint’s capabilities.:

Table A-3 SVC Conferencing - Maximum Supported Resolutions per Simulcast Stream

Conference Line Rate (kbps)

ProfileMaximum Resolution

Max. Frame Rate (fps)

Audio Rate (kbps)

1472 - 2048 High Profile 720p 30fps 48




256 - 512 Base Profile 180p 15fps 48



The maximum conference line rate for the RealPresence Collaboration Server 800s is 1920 kbps.

A-4

Documents

Version 8.3 | DOC2759A Polycom® RealPresence® SVC …support.polycom.com/.../products/network/RMX_SVC_Deployment_G… · Polycom® RealPresence® SVC-Based Conferencing Solutions