Endpoint Capabilities - Polycom RMX 1500 Administrator's Manual

Polycom RMX 1500/2000/4000 Getting Started Guide
2-32

Endpoint Capabilities

• 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) 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 only declared
to Polycom and Avaya 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 this System Flag is NO. When set to YES, the flag
ensures that the RMX declares SIP People+ Content and BFCP
capabilities in all environments.
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-5.
H.263 Endpoints
• If an endpoint that supports only H.263 for Content Sharing connects
to a conference with an Up to H.264 Content sharing Profile:
• H.263 is used for Content if that participant is the first to connect to
the conference
• Content sharing is stopped for all participants if the connection
occurs after Content sharing has started. When Content sharing is
restarted by the user, Content is shared using H.263.
H.264 Endpoints
• During a H.264 Content session, changes to resolution or frame rate
do not interrupt Content transmission.