Poly RealPresence Collaboration Server (RMX)1800 Deployment Guide

8.4 | July 2014 | DOC2781A

SVC-Based Conferencing Solutions Deployment Guide

Polycom

®

RealPresence

®

Collaboration Server (RMX)

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.

i

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.

Polycom® RealPresence® SVC-Based Conference Solutions Deployment Guide

Polycom, Inc. ii

Table of Contents

SVC Conferencing Solution Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

SVC Conferencing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Overview of SVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

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

Overview of the RealPresence SVC-Based Conferencing Solution . . . . . . . . . . . . . . . . . . 2

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

Video Layouts in the Mixed AVC CP and SVC Conference Mode . . . . . . . . . . . . . . . . 6

Allocating Available Bandwidth During Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

SVC Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Optimizing Video Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

B2B Support using the RealPresence SVC-Based Conferencing Solution . . . . . . . . . . . . 9

Detecting SVC/SIP Endpoint Disconnections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

SVC Conferencing System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

System Architecture for Enterprise Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

User Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Access Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Media Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Call Control Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Management and Provisioning Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Polycom System Environment Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

RealPresence Access Director . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

RealPresence DMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

RealPresence Collaboration Server (RMX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

RealPresence Collaboration Server (RMX) 800s/Virtual Edition . . . . . . . . . . . . . . . . . . . 17

Licensing for SVC-Based Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

RealPresence Resource Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Polycom RealPresence

®

CloudAXIS

™

Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

A Typical SVC-Based Conference Deployment Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

SVC Support for Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Deploying the RealPresence DMA in the Enterprise Environment . . . . . . . . . . . . . . . . . . 21

Deploying the RealPresence Resource Manager in the Enterprise Environment . . . . . . . 22

Supported Features in the RealPresence Collaboration Server (RMX) . . . . . . . . . . . . . . . . . 22

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Polycom® RealPresence® SVC-Based Conference Solutions Deployment Guide

Polycom, Inc. iii

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

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

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

39

Resource Capacities for Mixed CP and SVC Conferences . . . . . . . . . . . . . . . . . . . . . . . 55

Configuring the RealPresence Collaboration Server (RMX) 800s/Virtual Edition for Mixed AVC

CP and SVC Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Resource Capacities for Mixed CP and SVC Conferences . . . . . . . . . . . . . . . . . . . . . . . 59

Resource Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Configuring the RealPresence DMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Configuring the RealPresence DMA for SVC-Based Conferences . . . . . . . . . . . . . . . . . . 60

Configuring the RealPresence DMA for Mixed AVC and SVC Conferences . . . . . . . . . . 61

SVC-Enabled Conference Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Using the RealPresence SVC-Enabled Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Configuring the RealPresence Group Series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Making a Conference Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Point-to-Point Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Video Layouts for Point-to-Point Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Multipoint Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Video Layouts in Multipoint Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Video Layouts for RealPresence Desktop or RealPresence Mobile Conferences . . . 67

Video Layouts for RealPresence Group Series Conferences . . . . . . . . . . . . . . . . . . . 68

SVC-Based Conferencing Solution Specifications . . . . . . . . . . . . . . . . . . . . . . . 74

Solution Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Supported Conferencing Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Video Resource Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

MCU Supported Resolutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

MCU Supported Resolutions for SVC Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

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 Overview

This 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 the 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, which is 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 their

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.

The following diagram illustrates an example of the various devices and bandwidths that can be used in an

SVC-based video conferencing environment:

Polycom® RealPresence® SVC-Based Conferencing Solutions Deployment Guide

Polycom, Inc. 2

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

Polycom® RealPresence® SVC-Based Conferencing Solutions Deployment Guide

Polycom, Inc. 3

In the SVC-based conference, each SVC-enabled endpoint transmits multiple resolutions and temporal

layers to the Polycom® RealPresence® Collaboration Server (RMX) 1500/1800/2000/4000 or the

RealPresence Collaboration Server (RMX) 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 (RMX) 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 RMX.

The higher the display quality and size, the higher the requested resolution is 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 (RMX) is used as a media

relay server in an SVC-based conference:

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 (RMX).

Polycom® RealPresence® SVC-Based Conferencing Solutions Deployment Guide

Polycom, Inc. 4

As another example, the SVC stream sent from a RealPresence Desktop client (1) transmits 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 (RMX) 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 (RMX) functions as the multipoint media relay to the endpoints. For

voice activated selection of the video streams, the RealPresence Collaboration Server (RMX) determines

which of the incoming bit streams to send to each endpoint.

SVC video conferences provide a robust bandwidth-efficient technology that deliver 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. It also provides flexible in-stream selection to accommodate various endpoint

capabilities, such as bandwidth, CPU, screen resolution, and so on.

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

● The RealPresence Collaboration Server (RMX) functions as a media relay server providing low cost

production benefits. The RealPresence Collaboration Server (RMX) 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

Three types of conferences are defined in the RealPresence Collaboration Server (RMX):

● AVC CP Only

● SVC Only

● Mixed AVC CP and SVC

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

The RealPresence Collaboration Server (RMX) 1500/2000/4000, in addition to the RealPresence

Collaboration Server (RMX) 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 (RMX), 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.

Polycom® RealPresence® SVC-Based Conferencing Solutions Deployment Guide

Polycom, Inc. 5

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.

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.

Polycom® RealPresence® SVC-Based Conferencing Solutions Deployment Guide

Polycom, Inc. 6

Video Layouts in the Mixed AVC CP and SVC Conference Mode

Video layouts that are used in the mixed AVC CP and SVC conferencing mode depend 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 who 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:

Video Layouts for Mixed AVC CP and SVC Conferences

AVC endpoints can use the PiP (Picture in Picture) option, which displays the participant’s Self View.

This can change the video layouts view.

Number of Participants

SVC Endpoints (RPD) AVC Endpoints (Auto Layout)

2

3

4

5

Polycom® RealPresence® SVC-Based Conferencing Solutions Deployment Guide

Polycom, Inc. 7

6

7

8

9

10

11

Number of Participants

SVC Endpoints (RPD) AVC Endpoints (Auto Layout)

Polycom® RealPresence® SVC-Based Conferencing Solutions Deployment Guide

Polycom, Inc. 8

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 were displayed is no longer displayed in the video layout.

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). When required, the MCU reduces or increases the bandwidth 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.

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

12

Number of Participants

SVC Endpoints (RPD) AVC Endpoints (Auto Layout)

Polycom® RealPresence® SVC-Based Conferencing Solutions Deployment Guide

Polycom, Inc. 9

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. Mixed AVC CP

and SVC conferences are supported for B2B conferences.

The following diagram illustrates an example of Polycom B2B support:

Polycom® RealPresence® SVC-Based Conferencing Solutions Deployment Guide

Polycom, Inc. 10

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

Polycom® RealPresence® SVC-Based Conferencing Solutions Deployment Guide

Polycom, Inc. 11

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, refer to the Polycom RealPresence Collaboration Server (RMX)

1500/1800/2000/4000 Administrator’s Guide.

Polycom, Inc. 12

SVC Conferencing System Architecture

This chapter describes the Polycom RealPresence SVC Conferencing System Architecture, a general

description of SVC, and how to use 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 (RMX)

System Architecture for Enterprise Deployment

The following diagram illustrates the SVC-based conferencing system architecture; each plane is detailed

in the sections below the diagram:

Polycom® RealPresence® SVC-Based Conferencing Solutions Deployment Guide

Polycom, Inc. 13

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.

Polycom® RealPresence® SVC-Based Conferencing Solutions Deployment Guide

Polycom, Inc. 14

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.

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 (RMX) 1500/1800/2000/4000 (RMX) or the RealPresence Collaboration Server (RMX) 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 are optional for this level, such as the Polycom RSS

4000, used for video recording, archiving, and streaming.

Polycom® RealPresence® SVC-Based Conferencing Solutions Deployment Guide

Polycom, Inc. 15

In this SVC conferencing solution, the RealPresence Collaboration Server (RMX) communicates with the

Polycom

®

RealPresence

®

Distributed Media Application

™

(DMA

®

) as the SIP Server. The RealPresence

DMA manages conferences, and performs call control and signaling. For more information about the

RealPresence DMA in the SVC-based conferencing solution, see RealPresence DMA.

Call Control Plane

The Call Control Plane contains the RealPresence DMA that is responsible for call control, signaling, and

acts as the conference focus. The RealPresence DMA is the SIP Server for the SVC conferencing solution.

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

This level also contains the enterprise Active Directory (AD), which communicates with the RealPresence

Resource Manager, as well as the RealPresence DMA.

Polycom® RealPresence® SVC-Based Conferencing Solutions Deployment Guide

Polycom, Inc. 16

Polycom System Environment Components

This section describes the Polycom RealPresence components used in the SVC conferencing solution and

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 DMA

The RealPresence DMA is the primary server communicating between the SVC endpoints and the

RealPresence Collaboration Server (RMX). The RealPresence DMA is responsible for managing

conferences, call control, signaling, and acting as the conference focus. It communicates with the

RealPresence Collaboration Server (RMX) using the SIP protocol. The RealPresence DMA also provides a

REST API for creating Virtual Meeting Rooms (VMRs). To enable SVC-based conferences on VMRs, you

configure the Conference Template in the RealPresence DMA. For details on configuring the RealPresence

DMA for SVC-based conferences, see Configuring the RealPresence DMA.

For more information on using the RealPresence DMA, see the Polycom RealPresence DMA 7000 System

Operations Guide.

RealPresence Collaboration Server (RMX)

In the SVC conferencing environment, the 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.

Page is loading ...

Poly RealPresence Collaboration Server (RMX)1800 Deployment Guide

This manual is also suitable for

Poly RealPresence Collaboration Server (RMX)1800 Deployment Guide

Related papers

Other documents