Polycom RealPresence Capture Serverdownloads.polycom.com/.../RealPresence_capture_server_rn_1_6.pdfThe RealPresence Capture Server version 1.6 is typically deployed as part of a Polycom

Software 1.6.0 | Date March 2014 | 3725-69910-002 Rev C

Polycom® RealPresence

® Capture Server

RELEASE NOTES

RealPresence Capture Server Release Notes

Polycom, Inc. - 2 -

Introducing Polycom RealPresence

Capture Server

The Polycom® RealPresence

® Capture Server is a network appliance that participates in standards-based

video and telepresence calls. It converts the video and content in those calls into live streams (for live

viewing on devices with compatible web browsers) as well a video-on-demand archives for playback on

video conferencing systems and devices with compatible web browsers, including tablets, smart phones,

PCs, and MAC desktops.

The RealPresence Capture Server version 1.6 is typically deployed as part of a Polycom RealPresence

Platform, but it can be used as a standalone solution. The RealPresence Capture Server’s full potential

can best be realized when integrated with the Polycom RealPresence Media Manager.

Note: Capture Server 1.6 requires RealPresence Media Manager v6.6

RealPresence Capture Server 1.6 requires that RealPresence Media Manager v6.6 be installed on your system. There is no interoperability with earlier versions of RealPresence Media Manager.

This document provides the latest information for the RealPresence Capture Server and covers the

following topics:

● Software Version History

● Feature Overview

● Known Issues

● Interoperability

● Port Usage

● Multi-user Login Capacity

● Supported Media Player Plug-ins

● Supported External Media Servers

● Supported Web Browsers

For more information about configuring and using the RealPresence Capture Server, see the product

documentation available at RealPresence Capture Server User Manuals.

Software Version History The following table lists the RealPresence Capture Server version history.

http://support.polycom.com/PolycomService/support/us/support/network/index.html


Polycom, Inc. - 3 -

Software Version History

Version Release Date Description

1.6 March 2014 This release provides both Appliance Edition and Virtual Edition.

This is the first release of the RealPresence Capture Server Virtual

Edition.

1.0 July 2013 This is the first release of RealPresence Capture Server.

Before You Start

The following table shows the hardware requirements for the RealPresence Capture Server - Virtual

Edition.

Hardware Requirements

Component Description

Virtual Cores Each instance must have no less

than 8 virtual cores.

Minimal RAM 16 GB

Minimal Accessible Storage 120 GB

Feature Overview RealPresence Capture Server 1.6 includes the following new features:

● Support for streaming without recording, in which only live streaming is available and no archives

are created.

● Ability for users to watermark the video recording with timecode.

● Support for streaming meetings to an AKAMAI server using the Real Time Messaging Protocol

(RTMP).

● Ability to redirect visitors from the Capture Server’s user portal to the Media Manager v6.6 or

greater (or third-party portal) home page. Note – this is a best practice when using RealPresence

Media Manager v6.6 or another external portal to provide audience users to access live and on-

demand streams.


Polycom, Inc. - 4 -

Note: RealPresence Media Manager is not customer or partner upgradeable

RealPresence Media Manager is not customer or partner upgradeable. Contact your Polycom representative for a quote to upgrade RealPresence Media Manager before upgrading to RealPresence Capture Server 1.6.

Migrate Data for Appliance Edition Only

Archives and MP4 transcode files can be backed up and restored, but most other configuration data, such

as Virtual Recording Room (VRR) and external media servers, cannot (and must be reconfigured). In

addition to backing up the media, you can use a third-party tool to take screen captures of all

configuration screens to help speed reconfiguration. Note that you need to know the user/password

combination for any service that requires a user/password (FTP, SIP Registrar), as these will not be

backed up in migration.

Caution: Hotfix Patch 37317 is needed for 1.0 backup

Appliances running Capture Server v1.0 must first be Hot-Fixed with HF 37317 to ensure proper backup. Failure to apply HF 37317 before attempting to migrate to Capture Server v1.6, data will likey be lost.

Once HF 37317 is applied and Capture Server is restarted, data migration is enabled and you can back up your MP4

and RAW media files to a target FTP server you have configured in the Capture Server admin pages. After you have

upgraded to Capture Server v1.6, you will need to restore these files via FTP. Note that backup and restore via FTP

can be time-consuming for heavily used Capture Server systems.

Note: New license key is required for version 1.6

Retrieve the license key from the Polycom portal (support.polycom.com). If you have any issues, contact Polycom support.

To migrate media files:

1 Go to Admin > Data Backup/Restore > Migration.

2 Configure the following settings:

Server Address Enter the IP address of the FTP server.

Port Enter the port of the FTP server.

User Name and Password Enter the account and password for login to the FTP server. If the

FTP server has anonymous logins enabled, click Use Anonymous to log in using the

anonymous account. Note that the registered FTP user should possess read-write permissions

to the user root directory.

Enable SSL Set whether to enable SSL encryption for the communication between the

RealPresence Capture Server system and FTP server. The system can support only implicit

SSL FTP.

Media Path Specify where the backup data of 1.0 is saved.

Test Test whether the FTP server is accessible.


Polycom, Inc. - 5 -

Make sure that the media storage settings are the same as those set in version 1.0; otherwise, data

loss may occur during migration process.

3 Click Start Migration. Note that if migration is stopped and started again, files that have been

migrated are not migrated again.

Configure NFS for Virtual Edition

Capture server virtual edition requires a NFS share as its media storage. For Appliance Edition, NFS

storage is optional. The procedure below demonstrates how a NFS share is configured on a typical Linux

distribution.

It’s recommended to use Linux NFS.

Note: Capture Server v1.6 and NAS subsystems

Capture Server v1.6 supports network-attached storage (NAS); however, a fast (100G minimum) and very responsive network connection is required for stable I/O between Capture Server and NAS. To minimize any latency or delay in the writing or reading stream, archive data traveling to and from the Capture Server. Capture Server v1.6 supports only NAS subsystems that are located on the same physical Ethernet switch/segment as the Capture Server.

To export a shared storage location via NFS on a typical Linux system:

1 Make sure the NFS service has been installed and is running.

Examples:

[root@centos-nfs ~]# service nfs status

rpc.svcgssd is stopped

rpc.mountd (pid 20129) is running...

nfsd (pid 20194 20193 20192 20191 20190 20189 20188 20187) is running...

rpc.rquotad (pid 20125) is running...

2 Edit the NFS configuration file /etc/exports to set the file system paths for export.

Examples:

[root@centos-nfs ~]# cat /etc/exports

/home/nfs *(rw,no_root_squash)

/home/nfs_zip_1 192.168.9.78(rw,no_root_squash)

3 Restart the NFS service.

Examples:

[root@centos-nfs ~]# service nfs restart

Shutting down NFS daemon: [ OK ]

Shutting down NFS mountd: [ OK ]

Shutting down NFS quotas: [ OK ]

Shutting down NFS services: [ OK ]


Polycom, Inc. - 6 -

Starting NFS services: [ OK ]

Starting NFS quotas: [ OK ]

Starting NFS mountd: [ OK ]

Stopping RPC idmapd: [ OK ]

Starting RPC idmapd: [ OK ]

Starting NFS daemon: [ OK ]

4 Go to Configuration > Media Storage Settings and configure the settings.

Note: Limit each recording to less than 8 hours

To ensure good quality video recording limit each recording to less than 8 hours.

Known Issues This section lists the known issues for this RealPresence Capture Server release. If a workaround is

available, it is noted. Known issues are organized by type.

Admin UI

4950 After you power on the newly installed Capture Server system, you need to wait for 2 minutes to

log in to the Admin Portal with correct credential.

Workaround: None.

5139 If you go to Configuration > Signaling Settings, you cannot save both H.323 and SIP signalling

settings at one time.

Workaround: Save H.323 and SIP signalling settings separately by clicking OK.

5140 If you change the media storage settings and restart the system, the Data Backup/Restore button

is unavailable on Admin Portal for your first login.

Workaround: Log out and log in again.

5154 You cannot find a button on Admin Portal to delete log files manually.

Workaround: The Capture Server system deletes old log files automatically when file size

exceeds the threshold value.

5185 Go to Configuration > Diagnostics, enter a host name and click Ping, and a warning message

displays: “Please enter valid IP address.”

Workaround: Ignore the warning.

5212 If you place many calls to the Capture Server system, the media storage disk becomes full and

system hangs up all calls automatically. It takes over 10 minutes for archive files to be displayed

on Admin Portal.

Workaround: Wait for more than 10 minutes.


Polycom, Inc. - 7 -

EP Recording

4596 If you dial into an endpoint located in external network of RPAD environment from Capture

Server via H.323, the content sent from external endpoint cannot display.

Workaround: None.

4892 On Capture Server system’s recording template, if you set When Available as Media Encryption

Type, audio only recording cannot be set up.

Workaround: None.

Interoperability

2891 If a Polycom RMX system uses a recording link to live stream in a SIP VSW conference with a

Polycom HDX system RealPresence Capture Server, the conference always records at the

secondary rate when the conference line rate is set as 128 kbps, 256 kbps, or 384 kbps.

Workaround: None.

4598 FECC functionality doesn’t work if you dial into an endpoint located in external network of RPAD

environment from Capture Server via H.323 or SIP.

Workaround: None.

4994 Video playback displays no video in H.323 calls with the Polycom VVX 500 and VVX 600

endpoints.

Workaround: None.

LPR

2690 If you configure RealPresence Capture Server in connection with a Polycom RMX 2000 system

using a recording link that uses a LPR-enabled VRR during a multipoint call hosted by the RMX

system, you find that the LPR are not activated on the Tx side of the recorder.

Workaround: None.

MCU Recording

5177 Encrypted H.323 recording link with MGC cannot be set up.

Workaround: None.

RAID 10 Hardware Storage Array

3545 If you replace a failed hard disk with an used hard disk with RAID information, RealPresence

Capture Server cannot recover the used hard disk.

Workaround: Polycom provides a spare hard disk in the case of a failure. Use this spare hard

disk to replace a failed drive.

3548 When RealPresence Capture Server is running and one or more hard disks malfunction or stop

working, the RAID status on the Admin UI does not change. It is still normal.


Polycom, Inc. - 8 -

Workaround: When a hard disk does not work, a notification e-mail will be sent to the specified

address. You will also see a pop-up message indicating failed hard disks in the Admin UI.

Replace failed hard disks and reboot RealPresence Capture Server. The RAID status will change

to Degraded or the system will go into recovery mode in case of RAID failure.

Recording

5340 You cannot hear IVR when using DTMF to control the recording from conferences if recording link

is SIP with encryption.

Workaround: None.

SIP

2805 RealPresence Capture Server supports BFCP over TCP only and the far end systems that

support BFCP work only on BFCP over UDP if dual stream in SIP failed.

Workaround: Use third-party devices that support BFCP over TCP.

2894 If a Polycom RMX system uses a recording link to live stream a SIP call (call rate: 128–384 kpbs)

with a Polycom HDX system, the video out frame rate shown on the RMX side is significantly

lower than the call rate.

Workaround: None.

5011 You cannot unregister the Capture Server system from SIP server over TLS.

Workaround: None.

S_Network Separation

5270 When network separation is enabled, you cannot play live streaming and VoD on Android 4.1.2

devices using the RTSP protocol.

Workaround: None.

SNMP

3498 RealPresence Capture Server does not support SNMP trap.

Workaround: None.

S_PKI

2635 If you select the option System Config > Client Certificate > Enable web client certificate

validation, you cannot log in to the system after the system’s self-signed certificate expires.

Workaround: Disable the option Enable web client certificate validation before the self-signed

certificate expires.

5325 After you install a certificate chain, if you select Enable OCSP under Configuration > Certificate

Management and deselect Enable web client certificate validation and reboot the system, you

cannot enter either Admin or Viewer Portal login page.


Polycom, Inc. - 9 -

Workaround: Select both Enable OCSP and Enable web client certificate validation.

5284 Go to Configuration > Certificate Management and click Install Certificate, the Password text box

is always noneditable.

Workaround: None.

System Configuration

5335 Go to Admin > Log Settings and change the Logger Warning Capacity from 0 to 70 for which no

e-mail notification will be sent. You can still receive system alert and e-mail notification for low

disk usage alarm.

Workaround: Restart the system.

5341 Certificate configuration cannot restore to default settings after issuing reset config command

from the console to restore system configurations to the default value.

Workaround: None.

Video

5150 Watermark on video recording is illegible for archives with resolution 128x96.

Workaround: Use higher resolution.

Viewer Portal

2832 If an archive is not uploaded to an external server that you configured, the Viewer Portal shows

that you can play this archive. However, you cannot play this archive because RealPresence

Capture Server cannot find this archive on the external server.

Workaround: None.

4476 If you play live streaming or VoD from Viewer Portal on Android 4.2 tablets, the Full Screen

button doesn’t work.

Workaround: None.

4491 You cannot play back IIS media server live streaming and VoD on Android 4.1.2 devices.

Workaround: None.

4475 If you play back live streaming or VoD from Viewer Portal on Android 4.2 mobile phones, the Full

Screen button is unavailable.

Workaround: None.

5129 You cannot change signaling settings if there are ongoing calls on the Capture Server system.

Workaround: None.

5358 A valid user ID to log in to the Capture Server System’s Admin and Viewer Portal contains only

the following characters: lowercase characters (a–z), uppercase characters (A–Z), numbers (0–

9), and underscore.

Workaround: None.


Polycom, Inc. - 10 -

5359 When a player requests a chunk of media from the Capture Server System, if the chunk of media

is unready (the Capture Server System is constructing the media chunk), the Capture Server

System will not respond to the player request. As a result, the player stops to play and shows a

black screen. This exception often happens on players that play low bandwidth streaming, such

as 128 kbps, because players in this situation seem much easier to issue the requests before the

Capture Server System media chunks are ready.

Workaround: Run a live streaming at a higher bandwidth.

Others

2731 When an endpoint is connected to RealPresence Capture Server, the system name doesn’t work if

it contains Chinese.

Workaround: Call a Polycom HDX IPV4 address.

4974 You cannot dial in to specified VRRs via H.323 ID that contains characters.

Workaround: Set H.323 ID with only numbers.

5041 When the Capture Server system runs for a long time, upgrade progress becomes very slow.

Workaround: Cancel update and restart the system.

Playback

3316 You cannot play an archive whose duration is longer than 7 hours at one time.

Workaround: Play this archive again after a while.

Interoperability Limitations 2827 On Wowza server, the latency time for live streaming is about 30 seconds.

Workaround: None.

2884 During a SIP call with live streaming between the RadVision Scopia XT1000 system and

RealPresence Capture Server, when the RadVision Scopia XT1000 system sends DualVideo

(BFCP based People+Content) to RealPresence Capture Server, RealPresence Capture Server

shows the content only.

Workaround: None.

3291 Polycom does not support sending contents from a Lifesize Team 220 endpoint to RealPresence

Capture Server.

Workaround: None.

3523 You cannot fast forward or fast reverse VoD via Chrome and Firefox.

Workaround: Use Internet Explorer.

4925 FECC doesn’t work in H.323 VRR calls with Cisco C and E Series.

Workaround: None.

5032 FECC recording control doesn’t work in H.323 calls with Tandberg 880MXP endpoints.



Workaround: None.

5196 If you dial into the RealPresence Capture Server from Cisco Telepresence Systems, the TV UI

menu looks bad.

Workaround: None.

Interoperability Your Polycom RealPresence Capture Server systems are tested extensively with a wide range of

products. The tables in this section do not list a complete inventory of compatible equipment, but list the

products that have been tested for compatibility.

Video conferencing systems use a variety of algorithms to compress audio and video. In a call between

two systems, each end transmits audio and video using algorithms supported by the other end. In some

cases, a system may transmit an algorithm that differs from the algorithm it receives. This process occurs

because each system independently selects the optimum algorithms for a particular call, and different

products may make different selections. This process does not affect the quality of the call.

Interoperate with Polycom Products (H.323)

The following table shows the interoperability between RealPresence Capture Server and other Polycom

products when you record H.323 calls.

Interoperate with Polycom Products (H.323)

Type Product Version

Gatekeepers,

Gateways, and MCUs

Polycom CMA4000/5000 6.2.4, 6.2.5

Polycom DMA 7000 6.0.3, 6.0.4

Polycom RMX 1000/500 2.5.1

Polycom RMX 1000C/500C 2.5.1

Polycom RMX 1500/2000/4000 8.2, 8.3.0

Polycom RMX 1800 8.3.0

Polycom RMX 800VE 8.3.0

Polycom RMX 800S 8.3.0

Polycom MGC 9.0.4

Endpoints Polycom RealPresence Group Series 4.1.1, 4.1.3

Polycom HDX Series 3.1.2, 3.1.3

Polycom VSX Series 9.0.6.1, 9.0.6.2

Polycom QDX Series 4.0.3




Polycom PVX 8.0.16

Polycom VVX 5.0.1

CMA Desktop PC/Mac 5.2.4, 5.2.5

Polycom m100 1.0.6

Polycom RealPresence Desktop 3.0, 3.1

Polycom RealPresence Mobile (iPad, iPhone4s) 3.0, 3.1

Polycom RealPresence Mobile (Android) 3.0, 3.1

V500 9.0.6.2

Content Management

System

Polycom RealPresence Media Manager 6.6

Polycom RealPresence Media Editor 6.6

Interoperate with Third-party Products (H.323)

The following table shows the interoperability between RealPresence Capture Server and third-party

products when you record H.323 calls.

Interoperate with Third-party Products (H.323)


Gatekeepers, Gateways,

and MCUs

Codian MCU 4505 4.4 (3.57)

Cisco VCS X7.2.2

Endpoints RadVision Scopia XT1000 02.05.0416

Tandberg Edge95 MXP F9.3.1

SONY PCS-G50 2.72

SONY PCS-XG80 2.41

Cisco EX90 7.0.1

Sony PCS –1 3.42

Tandberg MXP 770 FC7.3.1

Tandberg C20 Tc2.1.2

External Media server Wowza 3.5.2




IIS Media Service 4.1

AKAMAI latest



Interoperate with Polycom Products (SIP)

The following table shows the interoperability between RealPresence Capture Server and other Polycom

products when you record SIP calls.

Interoperate with Polycom Products (SIP)


Gatekeepers, Gateways,

and MCUs

Polycom DMA 6.0.3, 6.0.4

Polycom RMX 1000/500 2.5.1

Polycom RMX 1000C/500C 2.5.1

Polycom RMX1500/2000/4000 8.2, 8.3

Polycom RMX 1800 8.3.0

Polycom RMX 800VE 8.3.0

Polycom RMX 800S 8.3.0

Endpoints Polycom HDX Series 3.1.2, 3.1.3

Polycom VVX 5.0.1

Polycom PVX 8.0.16

Polycom RealPresence Group Series 4.1.1, 4.1.3

Polycom RealPresence Desktop 3.0, 3.1

Polycom RealPresence Mobile (iPad, iPhone4s) 3.0, 3.1

Polycom RealPresence Mobile (Android) 3.0, 3.1

Interoperate with Third-party Products (SIP)

The following table shows the interoperability between RealPresence Capture Server and third-party

products when you record SIP calls.

Interoperate with Third-party Products (SIP)


SIP Server, Gateways,

and MCUs

Codian MCU 4505 4.4 (3.57)

Cisco VCS X7.2.2

Endpoints SONY PCS-G50 2.72




SONY PCS-XG80 2.41

Cisco EX90 7.0.1

Tandberg Edge95 MXP F9.3.1

LifeSize Team 220 4.12.0 (30)

RadVision Scopia XT1000 2.5.416

Port Usage The following table lists the port usage of your RealPresence Capture Server.

Port Usage

Usage Type Port Range

http TCP 80 (for IPV4 Only), 8080

https TCP 443 (for IPV4 Only), 8443

Trace (for technical support usage) UDP 60001 (configurable)

SMTP TCP 25

MS RTSP Streaming TCP 554

UDP (optional) Random (for source port)

Streaming (RTSP, HTTP, SSTR,

Adaptive streaming, and so on)

TCP 1640

UDP 6970 - 6971

Endpoint RAS UDP 1719

Q.931 Socket TCP 1720

H.245 Socket TCP 10000 – 10199 (configurable)

audio / video /

data

UDP 20000 – 20999 (configurable)

SIP BFCP TCP 20000 – 20049 (configurable)

UDP 10000 – 10049 (configurable)

External media

server

Wowza 1935

IIS Media Service 80



Usage Type Port Range

AKAMAI 1935

Multi-user Login Capacity Following are maximum numbers of admin UI login and Viewer Portal login, including anonymous login:

● Admin UI Login: maximum 200.

● Viewer Portal Login: maximum 3000.

Supported Media Player Plug-ins The following table lists the supported media player plug-ins.

Supported Media Player Plug-ins

Operating System Media Player Plug-in Name Media Player Version MP4

Windows Microsoft SilverLight 5.0.61118.0 Supported

5.1.20125.0 Supported

MAC Microsoft SilverLight 5.0.10411.0 Supported

5.1.20125.0 Supported

Supported External Media Servers The following table lists the supported external media servers.

Supported External Media Servers

Server Name Version Default Port Live Streaming VoD Supported

Media Type

IIS Media Server 4.1 80 Yes, supported

Windows, Mac OS,

and IOS

Yes, supported Windows

and Mac OS

MP4

Wowza Media

Server

3.5.2 1935 Yes, supported

Windows, Mac OS,

IOS, and Android

OS

Yes, supported Windows,

Mac OS, IOS, and

Android OS

MP4



Server Name Version Default Port Live Streaming VoD Supported

Media Type

AKAMAI Media

Server

latest 1935 Yes, supported IOS,

and Android OS 4.3

or above

No. MP4

Supported Web Browsers The following table lists the supported web browsers.

Supported Browsers

Operating System Browser Name Version MP4 (Live stream &VoD)

PC (Windows 7 and Windows 8) Internet Explorer 9, 10, 11 Yes

Firefox 26, 27 Yes

Chrome 32, 33 Yes

MAC OS-X

(Intel-based Leopard, Snow, and Lion)

Safari 7.0.1 Yes

Firefox 26, 27 Yes

Chrome 32, 33 Yes

iOS (iPad 2/air/mini, iPhone 4S/5) Safari 6.1.3,

7.0.3

Yes

Android Tablet (Samsung GT-P5210

and GT-N5100)

Android browser 4.1.2,

4.2.2, 4.3

Yes

Android Phone (Samsung Galaxy S4

and Galaxy Note3)

Android browser 4.1.2,

4.2.2, 4.3

Yes



Copyright ©2014, Polycom, Inc. All rights reserved. No part of this document may be reproduced, translated into another language or format, or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc.

6001 America Center Drive San Jose, CA 95002 USA

Trademarks

Polycom®, the Polycom logo and the names and marks associated with Polycom 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 property of their respective owners. No portion hereof may be reproduced or transmitted in any form or by any means, for any purpose other than the recipient's personal use, without the express written permission of Polycom.

End User License Agreement

Use of this software constitutes acceptance of the terms and conditions of the Polycom RealPresence Capture Server end-use license agreement (EULA).

The EULA for your version is available on the Polycom Support page for the Polycom RealPresence Capture Server.

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.

Open Source Software Used in this Product

This product may contain open source software. You may receive the open source software from Polycom up to three (3) years after the distribution date of the applicable product or software at a charge not greater than the cost to Polycom of shipping or distributing the software to you. To receive software information, as well as the open source software code used in this product, contact Polycom by email at [email protected].

Disclaimer

While Polycom uses reasonable efforts to include accurate and up-to-date information in this document, Polycom makes no warranties or representations as to its accuracy. Polycom assumes no liability or responsibility for any typographical or other errors or omissions in the content of this document.

Limitation of Liability

Polycom and/or its respective suppliers make no representations about the suitability of the information contained in this document for any purpose. Information is provided “as is” without warranty of any kind and is subject to change without notice. The entire risk arising out of its use remains with the recipient. In no event shall Polycom and/or its respective suppliers be liable for any direct, consequential, incidental, special, punitive or other damages whatsoever (including without limitation, damages for loss of business profits, business interruption, or loss of business information), even if Polycom has been advised of the possibility of such damages.

Customer Feedback

We are striving to improve our documentation quality and we appreciate your feedback. Email your opinions and comments to [email protected].

mailto:[email protected]

mailto:[email protected]



Visit the Polycom Support Center for End User License Agreements, software downloads, product documents, product licenses, troubleshooting tips, service requests, and more.

http://support.polycom.com/PolycomService/home/home.htm

Documents

Polycom RealPresence Capture Serverdownloads.polycom.com/.../RealPresence_capture_server_rn_1_6.pdfThe RealPresence Capture Server version 1.6 is typically deployed as part of a Polycom