19.08.2013 Views

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Polycom</strong> <strong>RMX</strong> 1500/<strong>2000</strong>/4000 Administrator’s <strong>Guide</strong><br />

H.239 / People+Content<br />

H.239<br />

People+Content<br />

The H.239 protocol allows compliant endpoints to transmit and receive two simultaneous<br />

video streams:<br />

• People Conference – Continuous Presence or Video Switched conference<br />

• Content Conference – Video Switching conference for content sharing<br />

By default, all conferences, Entry Queues, and Meeting Rooms launched on the <strong>RMX</strong> have<br />

H.239 capabilities.<br />

To view Content, endpoints must use the same Bit Rate, Protocol, and Resolution. An<br />

endpoint may not send Content while connecting to an Entry Queue.<br />

Endpoints without H.239 capability can connect to the video conference without Content.<br />

Cascade links declare H.239 capabilities and they are supported in Star and MIH cascading<br />

topologies. For more details, see "Cascading Conferences - H.239-enabled MIH Topology” on<br />

page 4-27.<br />

People+Content utilizes a different signaling protocol and is <strong>Polycom</strong>’s proprietary equivalent<br />

of H.239.<br />

<strong>Guide</strong>lines<br />

• All network environments are supported.<br />

• Conferences can include a mix of endpoints that support H.239 or People+Content.<br />

• All endpoints will receive Content at the highest resolution common to all connected<br />

endpoints.<br />

• SIP People+Content is supported with MPM+ and MPMx cards.<br />

• H.239 is supported in MIH, Star and Basic Cascading topologies.<br />

• People+Content is supported in cascaded conferences but cannot be used as the protocol<br />

for a cascade link.<br />

• If an endpoint supports both H.239 and People+Content protocols, H.239 is selected as<br />

the preferred communications protocol.<br />

• H.263 Annex T and H.264 protocols are supported for Content transmission.<br />

• People+Content is enabled by default. It can be disabled for all conferences and<br />

endpoints by manually adding the ENABLE_EPC System Flag to the System<br />

Configuration and setting its value to NO (default setting is YES).<br />

• Endpoints that support People+Content (for example, FX endpoints) may require a<br />

different signaling protocol. For these endpoints, manually add the System Flag<br />

CS_ENABLE_EPC to the System Configuration and set its value YES (default value is<br />

NO).<br />

• Content sharing is not supported in Microsoft ICE environment (BFCP protocol).<br />

• Video endpoints that do not support SIP Content (such as PVX), can receive Content on<br />

the People channel if the conference is set to Send Content to Legacy Endpoints. For more<br />

details see, "Sending Content to Legacy Endpoints” on page 3-12.<br />

3-2 <strong>Polycom</strong>, Inc.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!