Cisco Cisco Unified MeetingPlace Audio Server Maintenance Manual
Managing 4-7
February 27, 2004
Cisco MeetingPlace Audio Server System Manager’s Guide
Managing port scheduling with guard times
Guard times ensure that meetings do not overlap each other or that two
meetings are not scheduled back-to-back with the same meeting ID.
meetings are not scheduled back-to-back with the same meeting ID.
Guard times become part of the scheduled meeting record. For example, if
you schedule a meeting with the system start and end guard time parameters
set at 0 minutes, then change the system start and end guard times to
60 minutes, your meeting will not take on the new guard time settings. To
ensure the meeting in the example takes on the current system start and end
guard time minutes, you must reschedule your meeting. Back-to-back
reservationless meetings are permitted regardless of guard times. In effect, the
guard time for reservationless meetings is equal to zero.
you schedule a meeting with the system start and end guard time parameters
set at 0 minutes, then change the system start and end guard times to
60 minutes, your meeting will not take on the new guard time settings. To
ensure the meeting in the example takes on the current system start and end
guard time minutes, you must reschedule your meeting. Back-to-back
reservationless meetings are permitted regardless of guard times. In effect, the
guard time for reservationless meetings is equal to zero.
MeetingPlace uses guard times to manage three resources:
N
OTE
When using the Reservationless Meetings feature, profile numbers
cannot match existing meeting IDs, because reservationless meetings use
profile numbers as reservationless meeting IDs.
profile numbers as reservationless meeting IDs.
Resource
Description
Conference ports
Every MeetingPlace conference server has a finite number
of ports available for users, as described earlier. The
parameters discussed in this section determine how long
before, during, and after a scheduled meeting the ports are
reserved (and therefore when the ports become available to
other users).
of ports available for users, as described earlier. The
parameters discussed in this section determine how long
before, during, and after a scheduled meeting the ports are
reserved (and therefore when the ports become available to
other users).
Meeting IDs
Every meeting has an ID number, which is how users
identify the meeting they want to attend. During any given
time, a meeting ID must be unique, so that the system knows
which meeting to put a caller into. The meeting guard time
fields determine how long before and after a meeting the
meeting ID is protected. This protection prevents another
person from scheduling another meeting at the same time
with that particular meeting ID number. The meeting ID
guard time also defines the period before and after a meeting
that the caller hears that the meeting has not yet started or
has ended, rather than hearing that MeetingPlace does not
recognize the meeting.
identify the meeting they want to attend. During any given
time, a meeting ID must be unique, so that the system knows
which meeting to put a caller into. The meeting guard time
fields determine how long before and after a meeting the
meeting ID is protected. This protection prevents another
person from scheduling another meeting at the same time
with that particular meeting ID number. The meeting ID
guard time also defines the period before and after a meeting
that the caller hears that the meeting has not yet started or
has ended, rather than hearing that MeetingPlace does not
recognize the meeting.
Voice storage
Guard times reserve space for recording a meeting (if the
organizers elected to record the meetings at the time the
meeting was scheduled).
organizers elected to record the meetings at the time the
meeting was scheduled).