TANDBERG CODIAN MCU 4500 사용자 설명서
33
Sets the conference start time to the current time
on the MCU.
on the MCU.
The current time on the MCU is determined by
the settings in the
the settings in the
page, which
can only be modified by the administrator. See
information.
Allows you to retain a conference and its settings
for an infinite period of time.
for an infinite period of time.
Limits the duration of the conference for one
instance of the conference.
instance of the conference.
These fields are not available or necessary for
conferences set to permanent.
conferences set to permanent.
Which days and / or weeks the conference
repetitions will occur.
repetitions will occur.
The repetitions will always start at the same time
of day: the conference's configured Start time (see
above), and will last for the same amount of time:
the configured Maximum duration.
of day: the conference's configured Start time (see
above), and will last for the same amount of time:
the configured Maximum duration.
The start date is taken into account when
determining when the first repetition should
occur. For instance, if the start date is a
Wednesday and the conference is scheduled to
repeat every Monday, Tuesday and Wednesday
then it will occur only on Wednesday in the first
week and on all three specified days in subsequent
weeks.
determining when the first repetition should
occur. For instance, if the start date is a
Wednesday and the conference is scheduled to
repeat every Monday, Tuesday and Wednesday
then it will occur only on Wednesday in the first
week and on all three specified days in subsequent
weeks.
If a conference is set to repeat, its repetitions can
be configured to go on forever, stop after a
certain date, or to occur only a certain number of
times.
be configured to go on forever, stop after a
certain date, or to occur only a certain number of
times.
The first activation of a conference counts as a
"repetition", so configuring a conference to
repeat but terminate after 1 repetition is
equivalent to it not repeating at all.
"repetition", so configuring a conference to
repeat but terminate after 1 repetition is
equivalent to it not repeating at all.
You can choose to pre-configure endpoints to be part of a conference. These endpoints will be automatically invited
into the conference by the MCU. This is useful if you regularly invite the same participants into a conference. To
select which previously configured endpoints will be pre-configured for this conference, press
into the conference by the MCU. This is useful if you regularly invite the same participants into a conference. To
select which previously configured endpoints will be pre-configured for this conference, press
. (This button may also show a number in parentheses to indicate the number of participants that are
currently pre-configured). Refer to
There are two types of conference participant: chairperson and guest. IDs and PINs allow participants to connect to
conferences as the correct participant type.
conferences as the correct participant type.
Chairperson participants use Numeric ID and optionally, PIN; guest participants use Guest numeric ID and optionally,
Guest PIN.
Guest PIN.
A conference will not begin until the first chairperson joins. This means that guests will see a black screen/hear
silence with on screen text 'Waiting for conference chairperson' and an audio prompt after five seconds and then every
minute thereafter. Streaming viewers will see a black screen/hear silence although mark-up and text chat will work.
silence with on screen text 'Waiting for conference chairperson' and an audio prompt after five seconds and then every
minute thereafter. Streaming viewers will see a black screen/hear silence although mark-up and text chat will work.
You can control the behavior when the last chairperson leaves the conference (that is the When only guests remain
setting). The two options are:
setting). The two options are: