RMX 2000 Administrator's Guide - Polycom Support

Chapter 16-RMX Administration and Utilities
16-20
2 In the MCMS_PARAMETERS tab, the following flags can be modified:
Table 16-2 System Flags – MCMS_PARAMETERS
Flag Description
ALLOW_NON_
ENCRYPT_PARTY_IN_
ENCRYPT_CONF
APACHE_KEEP
_ALIVE
_TIMEOUT
If YES, allows non-encrypted participants to
connect to encrypted conferences.
Default: No
If the connection is idle for longer than the
number of seconds specified by this flag, the
connection to the RMX is terminated.
Value: 1 - 999
Default: 120
Default (JITC_MODE=YES): 15
AUTHENTICATE_USER If the external database application is to be
used to verify that operators are authorized to
log in to the MCU, set the value of this flag to
YES.
If the value of this flag is set to NO, the MCU
database is used to verify that operators are
authorized to log in to the MCU.
Note: If the flag is set to YES, the flow is first
to look in the internal DB and then go out to
the external one.
Flags for SE200 need to be added manually.
CHANGE_AD_HOC_CO
NF_DURATION
DISABLE_INACTIVE_
USER
The duration of an ad-hoc conference* can be
configured on a system level by setting the
flag to one of the following values (in minutes):
60 (default), 90, 180 and 270.
* An ad-hoc conference is automatically created
when the participant dials into an Ad-hoc Entry
Queue and enters a conference ID that is not being
used by any other conferencing entity. It is based on
the Conference Profile assigned to the EQ.
Users can be automatically disabled by the
system when they do not log into the RMX
application for a predefined period.
Possible Values: 0 - 90 days.
Default: 0 (disables this option).
Default (JITC_MODE=YES): 30