Polycom RealPresence 1800 Administration Manual page 383

Collaboration server
Hide thumbs Also See for RealPresence 1800:
Table of Contents

Advertisement

Two use cases are supported for content sharing:
● RealConnect Mode - Collaboration Server calls the AS-MCU
● Direct Call Mode - Lync client calls a VMR
Both cases require RealPresence Collaboration Server configured to MMCU mode.
Polycom RealConnect Call Mode
RealConnect's capability to translate between RDP and H.264, and vice versa, is embedded in the MMCU
and is referred to as RealConnect Mode or Gateway Mode. This requires a single transcoding resource,
between the virtual meeting room (VMR) and the Microsoft Application Sharing MCU (ASMCU). This
resource resides on a soft blade MMCU.
For Polycom RealConnect calls to work, set 'AllowMultiView' to TRUE on the Skype for Business Front End
Server. This allows participants to connect and receive multiple video streams.
This option can be used in place of a separate Polycom® ContentConnect™ gateway solution.
● If the are insufficient resources for a RDP-content translator, content isn't shared between Polycom
endpoints and Skype for Business clients.
● In the event of soft blade failure the MCU recovers RealConnect content calls if another soft blade is
available.
● In the event of MCU fail-over, RealConnect content calls are recovered immediately after the MCU
recovers the A/V RealConnect call.
Direct Call Mode
RDP content can be shared in the Direct Call mode, in which Skype for Business clients share the content
directly and Polycom clients still share the RDP content through RDP translator in the Soft blade.
● A transcoding resource is allocated to each direct call from a Skype for Business client to the VMR.
● The MMCU allocates transcoding resources to RDP content for each Skype for Business client
connected to a VMR
● DMA routes Skype for Business content calls to the same MCU where the A/V call is being hosted.
● In cases of MCU fail-over, only non-encrypted Skype for Business A/V calls can be re-established.
Recovery requires a re-invite, including the exchange of keys for the encrypted call, which is not
supported by Skype for Business clients.
● If there are insufficient resources for a RDP-content translator, whether content is sent through the
people video channel depends on the setting of the Send Content to Legacy Endpoints check box in
the Profile - Video Quality dialog. In this case, Skype for Business clients will not be able to share
content.
● RDP Content calls are not supported on MMCUs that do not have an encryption license.
● In the event of soft blade failure the MCU will recover Direct Calls if another soft blade is available. If
the content was being shared by the Skype for Business client, the content will be shared again by
the Skype for Business client.
Note: Transcoded content call
The transcoded content call reaches the main MCU.
Polycom, Inc.
Appendix - Modular MCU
362

Advertisement

Table of Contents
loading

This manual is also suitable for:

Realpresence 2000Realpresence 4000

Table of Contents