Maintenance Manual

Redial limit Enables or disables the redial limit. The redial limit allows the MCU to stop trying to
reconnect a failed call. When the limit is enabled, the
MCU will attempt to reconnect up to ten times: once
immediately after the connection failure; four times at
one minute intervals thereafter, and once every five
minutes for a further five attempts.
When the redial limit is disabled, the MCU continues
retrying - once every five minutes - after those first ten
attempts. It will do this until the connection is made. If
the connection is never made, the MCU continues
retrying until either the conference or the participant is
destroyed.
The redial pattern has an initial delay when the redial
behavior is set to Redial on any disconnection. With
that setting, the MCU does not immediately redial after
a deliberate disconnection - it waits 30 seconds.
This setting enables or disables the redial limit for all
conferences when they are redialing preconfigured
participants. The setting may be overridden by the
corresponding setting on individual preconfigured or ad
hoc endpoints.
Conferences
remain locked
when empty
When enabled, conferences remain
locked when all participants leave the
conference.
Without this option selected, when the final participant
leaves a locked conference, the MCU unlocks that
conference.
Use
conference
name as caller
ID
If enabled, when the MCU is calling out
to an endpoint, the caller ID that the
endpoint will see is the conference
name.
Without this option selected, the caller ID is the name
of the MCU. This setting applies to both H.323 and SIP
endpoints.
Require H.323
gatekeeper
callers to
enter PIN
Instructs the MCU to request
conference participants dialing into
protected conferences using an E.164
number via an H.323 gatekeeper to
enter a PIN before they may join the
conference.
You may want participants joining a conference via a
gatekeeper not to need to enter a PIN, even for
protected conferences. If this is the case, do not set
this option. If you want conferences to be protected,
regardless of how participants connect, ensure you set
this option.
When this option is set, participants calling into a
protected conference will be presented with PIN-entry
screen instead of the normal conference view. The
option has no effect for conferences with no PIN set.
Require a PIN
for ad hoc
conferences
If this option is checked, a participant
creating an ad hoc conference must
enter a PIN for that conference. The
MCU will not create the conference
until the participant enters a PIN.
When a PIN is required for ad hoc conferences, the
auto attendant will wait forever for the participant to
enter a PIN.
This option is required in some highly secure
environments.
Minimum
required PIN
length for ad
hoc
conferences
The minimum number of digits required
for a PIN.
This field is only available if Require a PIN for ad hoc
conferences is selected. This forces a participant who
is creating an ad hoc conference to protect it with a
PIN with at least this number of digits.
163
Cisco TelePresence MCU Series Online Printable Help