September 2013 | Level 2
Breaking News
RealPresence Video Collaboration Server (RMX) 8.1.7
Software Release Date: July 19, 2013 (RMX 1500/2000/4000)
July 30, 2013 (RP Collaboration Server 800s)
Breaking News: RMX 8.1
V1 Page 2 of 16
Disclaimer © 2013 Polycom, Inc. All rights reserved.
Polycom, Inc. 6001 America Center Dr 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.
Breaking News: RMX 8.1
V1 Page 3 of 16
Contents
Module Overview ................................................................................................................... 4
Polycom RealPresence Collaboration Server (RMX) Version 8.1.7 .................................... 5
TIP Support with Polycom Endpoints .................................................................................... 5
Encryption Support with TIP ................................................................................................. 6
Port Number Change for RealPresence Collaboration Server 800s ...................................... 6
Additional Conferencing Features ......................................................................................... 7
Mixed AVC / SVC Support ..................................................................................................... 7
Examples of AVC and SVC Streams .................................................................................... 9
Conference Profile Settings for Mixed CP and SVC Conferencing ...................................... 10
Translation Pools and Resource Capacities for Mixed Conferences ................................... 11
New SVC Features ............................................................................................................. 13
Lab Exercise / Demonstration: Mixed SVC / AVC Conference ......................................... 14
Breaking News: RMX 8.1
V1 Page 4 of 16
Module Overview
This module provides an overview of the Polycom RMX 8.1 software release, which was
made available in July, 2013 for all models of the Polycom RMX along with the RealPresence
Collaboration Server 800s.
Intended Audience
This course is intended for students that are familiar with existing Polycom solutions and now
want to learn about the RMX 8.1 release.
Prerequisites
Students should have attended RealPresence Implementation, Configuration and
Troubleshooting (Level 2) RPIIT202 training or have equivalent experience with Polycom
video and infrastructure products.
Product Release Date
RMX Version 8.1.7.35 was made generally available on July 19, 2013 for the RMX product
line (1500 / 2000 / 4000) and on July 30, 2013 for the RealPresence Collaboration Server
800s.
Lab Exercise / Demonstration Scenario
A lab exercise has been provided with this training. Detailed instructions are provided for
students that have access to the necessary Polycom equipment and a recorded
demonstration can be viewed as well.
Breaking News: RMX 8.1
V1 Page 5 of 16
Polycom RealPresence Collaboration Server (RMX) Version 8.1.7
RMX version 8.1.7 introduced a wide range of new features, including support for both CP
(AVC) and SVC participants in the same conference. Another major change is the way
system resources are reported in the RMX Manager. RMX Ports are now counted as
HD720p30. This is a change from the previous unit of measurement: CIF ports.
TIP Support with Polycom Endpoints
Polycom endpoints can now connect to Entry Queues, Meetings Rooms and conferences
using the TIP protocol. TIP Compatibility is a setting on the Advanced tab of a CP
Conference Profile as shown below:
Breaking News: RMX 8.1
V1 Page 6 of 16
Encryption Support with TIP
Encryption between the Polycom RealPresence Collaboration Server (RMX) and a CISCO
environment is now supported.
Media and control can be encrypted using SRTP/SRTCP
TIP is encrypted using SRTCP
SIP is encrypted using DTLS
When upgrading, the RMX automatically creates a self-signed certificate to support encrypted
communications with CISCO endpoints.
Port Number Change for RealPresence Collaboration Server 800s
When connecting to the Polycom RealPresence Collaboration Server 800s using the RMX
Manager application, version 8.1.7 requires the use of port 8080. Currently, the default ports
are 80 and 443 so the user must manually enter 8080 in the MCU Properties window, as
shown below:
Breaking News: RMX 8.1
V1 Page 7 of 16
Additional Conferencing Features
This release includes numerous new conferencing features, including:
CCS Support: The Polycom Content Collaboration Solutions (CCS) Plug-in for Lync
clients is now supported, allowing Lync clients to receive and send Content on a
separate channel, without having to use the video channel. Content is transmitted
using SIP BFCP
Automatic Suppression of Noisy Endpoints: The RMX can detect AVC endpoints with
a noisy audio channel and automatically mute them. This setting can be found in the
Audio Settings tab of the Conference Profile, as shown below:
Multiple Content Resolutions: Content can be shared in multiple streams to support
H.263 and H.264 video protocols in the same conference to allow endpoints with
different protocols to receive content without having to restart Content sharing in the
middle of a conference
AS SIP Support: The RMX can accept incoming Assured Services SIP (AS SIP) calls,
place outbound AS SIP calls at varying precedence levels and accept AS SIP content
Mixed AVC / SVC Support
This feature enables participants with SVC-enabled endpoints and AVC endpoints to
participate in the same conference. The RealPresence Collaboration Server 1500/2000/4000
in addition to the RealPresence Collaboration Server 800s - Virtual Edition, can manage a
mixed CP and SVC conference.
Breaking News: RMX 8.1
V1 Page 8 of 16
In a mixed CP (AVC) 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
CP and SVC conferencing, both SVC and AVC endpoints in the conference receive the same
CP layout.
The diagram below illustrates an example of a mixed CP and SVC conferencing mode:
Breaking News: RMX 8.1
V1 Page 9 of 16
Examples of AVC and SVC Streams
The RealPresence Desktop application will be used to highlight the differences between a CP
conference (AVC only) and a CP and SVC mixed mode conference on the RMX. Shown
below are screen captures from the RealPresence Desktop while it is dialed into the two
different conferences with the same five additional endpoints.
Here are the call statistics for a RealPresence Desktop endpoint dialed into an RMX AVC
Meeting Room (ID 1004) with five additional endpoints. Notice there are two participants
shown in the listing: “Local” is the RealPresence Desktop endpoint and 1004 represents the
RMX Meeting Room 1004.
Shown below is the RealPresence Desktop endpoint dialed into a CP and SVC conference on
the RMX with the same five additional endpoints. There are now multiple call streams, as the
RMX is passing multiple SVC-decoded video streams to the RealPresence Desktop SVC
endpoint. Notice that the RealPresence Desktop device is not currently receiving audio
streams for all of the endpoints in the list, as they are currently muted.
Breaking News: RMX 8.1
V1 Page 10 of 16
Conference Profile Settings for Mixed CP and SVC Conferencing
To support this new capability a new Conferencing Mode is now available: CP and SVC.
The RMX now ships with a default Conference Profile to support mixed CP and SVC
conferences. These default settings (shown below) are also the default settings used by the
RMX Manager when creating a new Conference Profile.
Profile Name: Factory_Mix_SVC_CP_Video_Profile
Line Rate: 1920 kbps
Video Switching: Disabled
Operator Conference: Disabled
Encryption: Enabled
Packet Loss Compensation (LPR and DBA): Enabled for AVC participants only
Auto Terminate: After last participant quits Enabled
Auto Redialing: Disabled
Font for text over video: Enabled for AVC participants only
Exclusive Content Mode: Disabled
TIP Compatibility: Disabled
Enabled FECC: Enabled
Gathering Phase: Enabled
Display Language: English
Video Quality: Sharpness
Maximum Resolution: Auto
This profile has been assigned to the following default conference entities:
Maple_Room: ID 1001
Oak_Room: ID 1002
Juniper_Room: ID 1003
Fig_Room: ID 1004
Default EQ: ID 1000
Breaking News: RMX 8.1
V1 Page 11 of 16
Translation Pools and Resource Capacities for Mixed 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.
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 RMX
2000 and 4000 models:
Resource Type
Number of Available Ports
RMX 2000 2x MPMx
RMX 4000 4x MPMx
Mixed CP and SVC HD 20 AVC 90 SVC
40 AVC 180 SVC
HD720p 60 120
SD @ 30 fps 120 240
SVC Only 180 360
CIF @ 30 fps 180 360
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.
Breaking News: RMX 8.1
V1 Page 12 of 16
In this resource capacity allocation 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 is 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:
The following table shows the actual resource capacity utilization for both CP only and mixed
CP and SVC conferences:
Port Type Non-Mixed Conferences Mixed 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
Breaking News: RMX 8.1
V1 Page 13 of 16
The resource capacity utilization table below indicates the total amount of ports used for each
port type for one MPMx media board:
Port Type Maximum Ports in Non-
Mixed Conferences Maximum Ports in Mixed CP and SVC Conferences
AVC HD 30 20
AVC SD 60 40
AVC CIF 90 40
SVC 90 90
New SVC Features
The following features have been added to SVC support in this release:
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 CP and SVC
conferences
IVR Services for SVC: IVR Services are now supported in SVC Conferencing Modes
PSTN (Audio Only) in Mixed Conferences: PSTN audio calls are supported in mixed
CP and SVC conferences
SVC Licensing: A purchasable license is now required for SVC-enabled conferencing
Breaking News: RMX 8.1
V1 Page 14 of 16
Lab Exercise / Demonstration: Mixed SVC / AVC Conference
View the accompanying video from the course registration page to see a
demonstration of the following lab exercise or use your own equipment to
complete the lab exercise. When finished with lab exercise / demonstration return
to this point in the courseware.
Summary Exercise (10 Minutes)
Objective
During this lab you will use the RMX Manager 8.1 to create an appropriate conference profile
and meeting room and then use the RMX Manager Participant properties to show the SVC
and AVC participants in the conference. The steps will include:
Login to the RMX version 8.1 and verify that the SVC license has been applied
Create a new Conference Profile to support the CP and SVC Conferencing Mode
Create a new Meeting Room using the newly created conference profile
Dial into the CP and SVC Meeting Room using the RealPresence Desktop for
Windows application and an HDX endpoint
Verify the SVC and AVC connectivity using the RMX Manager application
What You Will Learn
After completing the exercises you will be able to:
Verify SVC support on an RMX running version 8.1
Create an RMX Conference Profile with the CP and SVC Conferencing Mode
Create an RMX Meeting Room using the CP and SVC Conference Profile
Place a SIP call into a CP and SVC Meeting Room using the Polycom RealPresence
Desktop application and an H.323 call using an HDX or Group Series endpoint
Use the RMX Manager application to verify SVC and AVC connectivity of the
endpoints
Breaking News: RMX 8.1
V1 Page 15 of 16
Lab Diagram
Detailed Lab Steps
Login to the RMX 8.1 and Verify SVC Licensing
1. Open the RMX Manager 8.1 application an connect to the RMX using an
Administrator login
2. Navigate to Administration > System Information and ensure the value for SVC
is set to True
Note: If the value for SVC is False, you will need to obtain and load a new
Activation Key for the RMX that includes the SVC license before proceeding with
this lab exercise
Creating CP and SVC Conference Profile and New Meeting Room
3. Navigate to Rarely Used > Conference Profiles and select the icon for New
Profile
4. Name the new profile CP and SVC Profile, select an appropriate line rate and select the Conferencing Mode of CP and SVC from the drop-down list Note: The Gathering Phase and Message Overlay options are not available in a CP and SVC conference
5. Change the Routing Name to CPandSVC
6. Select the Video Quality option and change Content Settings to HiResGraphics. Notice the new option for selecting a Customized Content Rate and that the Content Protocol of H.264 Cascade and SVC Optimized is the only available choice
RMX Version 8.1
RealPresence Desktop
SVC / AVC
Meeting Room
HDX
SVC
CP
(AVC)
SIP
H.323
HDX
Breaking News: RMX 8.1
V1 Page 16 of 16
7. Click OK to create the new Conference Profile
8. Navigate to Frequently used > Meeting Rooms and select the icon for New Meeting Room
9. Name the new meeting room Mixed Mode Meeting Room, select an appropriate duration and be sure to select the Profile: CP and SVC Profile
10. Set the ID of the conference to 1234 and click OK to create the new Meeting Room
Place SVC Call and Use RMX Manager to Monitor
11. From a Group Series or HDX endpoint, place a H.323 call into the Mixed Mode
Meeting Room, conference ID 1234
12. Open RealPresence Desktop for Windows and place a SIP call into the Mixed
Mode Meeting Room, in this example dialing [email protected] where
10.233.10.41 is the Signaling IP address of the RMX version 8.1
13. Once the call connects, click the Connection Status icon in the lower left corner of
the screen to view the call statistics and then click Close
14. Open RMX Manager 8.1 to monitor the conference
15. Select the Mixed Mode Meeting Room in the Conferences window and then
select the RealPresence Desktop endpoint in the Participant window
16. Right-click and select Participant Properties to view the General tab to
determine the Endpoint Type of SVC and then select OK
17. Select the second endpoint in the conference and right-click to view the General
tab to determine the Endpoint Type of AVC and then select OK
18. When finished viewing details of the participants, highlight the conference name
from the Conferences pane and click the icon to terminate the conference
End of practical exercise
