Bfcp Support In Dial-In Connections; Video Transmission Methods For Sharing Content - Polycom RealPresence 800s Administrator's Manual

RealPresence Collaboration Server (RMX) 800s/Virtual Edition Administrator's Guide
System Flag - SIP_BFCP_DIAL_OUT_MODE
Flag Value
AUTO
(Default)
UDP
TCP
For more information see

BFCP support in dial-in Connections

● The Collaboration Server will share content with dial-in SIP clients according to their preferred BFCP
protocol.
● SIP clients connected as audio only cannot share content.

Video Transmission Methods for Sharing Content

Content can be shared using the following video transmission methods:
● Content Highest common parameters (also known as Content Video Switching)
● Multiple Content Resolutions (CP Conferencing Mode only)
In Content Video Switching mode, the content is negotiated to highest common capabilities supported by
the endpoints connected to the conference. If the conference includes participants that support lower
content capabilities (such as H.263) and higher content capabilities (H.264), content will be sent at the lower
capabilities supported by all endpoints, resulting in lower content quality seen by all endpoints.
In this mode, the content is set according to the capabilities of all the participants currently connected to the
conference. If the all the connected participant support the H.264 protocol, the Content will be started with
H.264 capabilities. If then an endpoint supporting only H.263 protocol connects, the content is stopped in
order to switch to H.263 and has to be resent. If the H.263 participant leaves the conference and only H.264
capable endpoints remain connected, content is stopped in order to switch back to H.264 and has to be
resent.
In Multiple Content Resolutions mode, content is shared in multiple streams, one for each video protocol:
H.263 and H.264. A separate video resource is used to process the Content shared with H.264-capable
endpoints and another for content shared with H.263-capable endpoints, with each endpoint receiving its
highest possible quality. This allows endpoints with different protocols to connect and disconnect without
having to restart Content sharing in the middle of a conference.
In this mode, endpoints that do not support the content capabilities set for the conference will receive the
content over the video (people) channel ("Legacy" content).
Polycom®, Inc.
UDP
BFCP/UDP selected as
Content sharing protocol.
Cannot share Content.
Manually Adding and Deleting System Flags
SIP Client: BFCP Support
TCP
BFCP/TCP selected as
Content sharing protocol.
Cannot share Content.
BFCP/TCP selected as
Content sharing protocol.
UDP and TCP
BFCP/UDP selected as
Content sharing protocol.
.
139