Content Protocol; Endpoint Capabilities - Polycom RMX 1500 Administrator's Manual

Multipoint control unit
Hide thumbs Also See for RMX 1500:
Table of Contents

Advertisement

Table 2-9 summarizes the Maximum Resolution of Content and Frames per Second (fps) for Bit
Rate Allocations to the Content Channel as set out in Table 2-9.
Table 2-9
Bit Rate Allocated to
Content Channel (kbps)
From 64 and less than 512
From 512 and less than 768
From 768 and up to 1536

Content Protocol

H.263 Annex T and H.264 protocols are supported for the Content transmission.
H.264 provides higher video quality at video resolutions of up to HD.

Endpoint Capabilities

H.263 Endpoints
Polycom, Inc.
Content - Maximum Resolution, Frames/Second per Bit Rate Allocation
The H239_FORCE_CAPABILITIES System Flag in system.cfg gives additional control
over Content sharing.
When the flag is set to NO, the RMX only verifies that the endpoint supports the
content protocols: Up to H.264 or H.263.
When set to YES, the RMX checks frame rate, bit rate, resolution, annexes and all other
parameters of the Content mode as declared by an endpoint during the capabilities
negotiation phase. If the endpoint does not support the Content capabilities of the MCU
the participant will not be able to send or receive content over a dedicated content
channel. The flag's default value is NO.
Content management control, BFCP, is supported with TCP only. BFCP utilizes an
unsecured channel even when SIP TLS is enabled. If security is of higher priority than
SIP content sharing, SIP People+Content can be disabled. To do this manually add the
ENABLE_SIP_PEOPLE_ PLUS_CONTENT System Flag to the System Configuration and
set its value to NO.
SIP People+Content and BFCP capabilities are by default declared to all endpoints. If,
however, the endpoint identity is hidden by a proxy server, these capabilities will not
be declared by the RMX. Capabilities declaration is controlled by the
ENABLE_SIP_PPC_FOR_ALL_USER_AGENT System Flag.
The default value of the ENABLE_SIP_PPC_FOR_ALL_USER_AGENT System Flag is
YES resulting in BFCP capability being declared with all vendors' endpoints unless it is
set to NO. When set to NO, the RMX will declare SIP People+Content and BFCP
capabilities to Polycom and Avaya endpoints .
The CFG_KEY_ENABLE_FLOW_CONTROL_REINVITE System Flag should be set to
NO when SIP BFCP is enabled.
If these System Flags don't exist in the system, they must be created using the RMX
Menu – Setup option. For more information see "Modifying System Flags" on page 19-4.
If an endpoint that supports only H.263 for Content Sharing connects to a conference
with an Up to H.264 Content sharing Profile:
Content
Maximum Resolution
H.264 HD720p
H.264 HD720p
H.264 HD1080p
Chapter 2-Additional Conferencing Information
Frames/Second
5
30
15
2-27

Advertisement

Table of Contents
loading

This manual is also suitable for:

Rmx 4000Rmx 2000

Table of Contents