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 />

Additional Content Information<br />

Forcing Other Content Capabilities<br />

• The H239_FORCE_CAPABILITIES System Flag in system.cfg gives additional control<br />

over Content sharing:<br />

— When the flag is set to NO (default), the <strong>RMX</strong> only verifies that the endpoint<br />

supports the content protocols: H.263 or H.264.<br />

— When set to YES, the <strong>RMX</strong> checks frame rate, bit rate, resolution, annexes and all<br />

other parameters of the Content mode as declared by an endpoint during the<br />

capabilities negotiation phase. If the endpoint does not support the Content<br />

capabilities of the MCU, the participant will not be able to send or receive content<br />

over a dedicated content channel.<br />

BFCP Content Capabilities<br />

• Content management control, BFCP, is supported with TCP only. BFCP utilizes an<br />

unsecured channel even when SIP TLS is enabled. If security is of higher priority than<br />

SIP content sharing, SIP People+Content can be disabled. To do this manually add the<br />

ENABLE_SIP_PEOPLE_ PLUS_CONTENT System Flag to the System Configuration and<br />

set its value to NO.<br />

• SIP People+Content and BFCP capabilities are by default declared to all endpoints. If,<br />

however, the endpoint identity is hidden by a proxy server, these capabilities will not<br />

be declared by the <strong>RMX</strong>. Capabilities declaration is controlled by the<br />

ENABLE_SIP_PPC_FOR_ALL_USER_AGENT System Flag.<br />

The default value of the ENABLE_SIP_PPC_FOR_ALL_USER_AGENT System Flag is<br />

YES resulting in BFCP capability being declared with all vendors’ endpoints unless it is<br />

set to NO. When set to NO, the <strong>RMX</strong> will declare SIP People+Content and BFCP<br />

capabilities to <strong>Polycom</strong> and Avaya endpoints.<br />

• The CFG_KEY_ENABLE_FLOW_CONTROL_REINVITE System Flag should be set to<br />

NO when SIP BFCP is enabled.<br />

If these System Flags don’t exist in the system, they must be created using the <strong>RMX</strong><br />

Menu – Setup option. For more information see "Modifying System Flags” on page 21-1.<br />

• BFCP capabilities are not supported in Microsoft ICE environment.<br />

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

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

Saved successfully!

Ooh no, something went wrong!