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

Table 21-1 System Flags – MCMS_PARAMETERS (Continued)<br />

Flag Description<br />

ALLOW_NON_ENCRYPT_R<br />

ECORDING_LINK_IN_ENCR<br />

YPT_CONF<br />

When set to NO (default), the Recording Link inherits the<br />

encryption settings of the conference. If the conference is<br />

encrypted, the recording link will be encrypted.<br />

When set to YES, it disables the encryption of the recording<br />

link, regardless of the Encryption settings of the conference<br />

and RSS recorder.<br />

AUTHENTICATE_USER If the external database application is to be used to verify that<br />

operators are authorized to log in to the MCU, set the value of<br />

this flag to YES.<br />

If the value of this flag is set to NO, the MCU database is<br />

used to verify that operators are authorized to log in to the<br />

MCU.<br />

Note: If the flag is set to YES, the flow is first to look in the<br />

internal DB and then go out to the external one.<br />

Flags for SE200 need to be added manually.<br />

BONDING_CHANNEL_DELA<br />

Y<br />

(ISDN)<br />

CHANGE_AD_HOC_CONF_<br />

DURATION<br />

CONTENT_SPEAKER_INTR<br />

A_SUPPRESSION_IN_SEC<br />

ONDS<br />

CPU_TCP_KEEP_ALIVE_TI<br />

ME_SECONDS<br />

When connecting a bonding group, this is the delay (number<br />

of 1/100 seconds) between dialing attempts to connect<br />

sequential channels.<br />

The channel per second connection performance of ISDN<br />

switches can vary and can cause timing issues that result in<br />

bonding channel disconnection.<br />

Default: 6<br />

The duration of an ad-hoc conference* can be configured on<br />

a system level by setting the flag to one of the following<br />

values (in minutes): 60 (default), 90, 180 and 270.<br />

* An ad-hoc conference is automatically created when the participant<br />

dials into an Ad-hoc Entry Queue and enters a conference ID that is<br />

not being used by any other conferencing entity. It is based on the<br />

Conference Profile assigned to the EQ.<br />

This flag controls the requests to refresh (intra) the content<br />

sent from the <strong>RMX</strong> system to the content sender as a result of<br />

refresh requests initiated by other conference participants.<br />

Enter the interval in seconds between the Intra requests sent<br />

from the <strong>RMX</strong> to the endpoint sending the content to refresh<br />

the content display. Refresh requests that will be received<br />

from endpoints within the defined interval will be postponed to<br />

the next interval.<br />

Default setting: 5<br />

This flag indicates when to send the first KeepAlive indication<br />

to check the TCP connection.<br />

Default value: 7200 second (120 minutes)<br />

Range: 600-18000 seconds<br />

When there are NAT problems, this default may be too long<br />

and the TCP connection is lost. In such a case, the default<br />

value should be changed to 3600 seconds (60 minutes) or<br />

less.<br />

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

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

Saved successfully!

Ooh no, something went wrong!