Filter
Top Products
Polycom® RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide
4-2 Polycom, Inc.
Content Sharing
Content such as graphics, presentations, documents or live video can be shared with
conference participants using the H.239 (H.323) or BFCP (SIP) protocol, which is the
standard protocols for content sharing or Polycom’s proprietary protocol People+Content.
H.239 Protocol
The H.239 protocol allows compliant endpoints to transmit and receive two simultaneous
video streams:
• People video stream – video is displayed in Continuous Presence conferences or Video
Switching conferencing mode or in Media Relay (SVC) conferencing Mode
• Content video stream – Video Switching mode for content sharing
By default, all conferences, Entry Queues, and Meeting Rooms launched on the Collaboration
Server have H.239 capabilities.
To view Content, endpoints must use the same Bit Rate, Protocol, and Resolution. Endpoints
may not send Content while connecting to an Entry Queue.
Endpoints without H.239 capability can connect to the video conference without Content.
Cascade links declare H.239 capabilities and they are supported in Star and MIH cascading
topologies. For more details, see "Cascading Conferences - H.239-enabled MIH Topology” on
page 5-28.
People+Content
People+Content utilizes a different signaling protocol and is Polycom’s proprietary equivalent
of H.239.
Guidelines
• All network environments are supported.
• Conferences can include a mix of endpoints that support H.239 or People+Content.
• All endpoints will receive Content at the highest resolution common to all connected
endpoints.
• SIP People+Content is supported with MPM+ and MPMx cards.
• H.239 is supported in MIH, Star and Basic Cascading topologies.
• People+Content is supported in cascaded conferences but cannot be used as the protocol
for a cascade link.
• If an endpoint supports both H.239 and People+Content protocols, H.239 is selected as
the preferred communications protocol.
• H.263 Annex T and H.264 protocols are supported for Content transmission.
• People+Content is enabled by default. It can be disabled for all conferences and
endpoints by manually adding the ENABLE_EPC System Flag to the System
Configuration and setting its value to NO (default setting is YES).
• Endpoints that support People+Content (for example, FX endpoints) may require a
different signaling protocol. For these endpoints, manually add the System Flag
CS_ENABLE_EPC to the System Configuration and set its value to YES (default value is
NO).