Cisco Cisco Unified MeetingPlace Audio Server Maintenance Manual

Cisco MeetingServer 5.1 System Manager’s Guide   

 

                  78 

 

Cisco Systems 

 

March 2003 

Figure 0-4 shows how guard time settings affect users. 

When the system "knows" about a particular meeting ID.

Meeting ID is reserved for this length of time and cannot be used for another meeting.

If there are

conference ports

available, users will be

allowed to join the
voice conference.

Since conference

ports have been

guaranteed for early

arrivals, users will be

admitted to both voice

and web components

of the meeting.

Conference ports are

guaranteed to be available

for meeting extensions

because they have been
reserved by the system.

If a meeting is over,

someone who calls or

logs in will be

informed that  "The

meeting has ended".

Users attempting to join

the meeting will be

informed that "This is not a

recognized meeting ID

number" assuming that the

meeting has ended.

 Mtg ID Start

 Guard Time

(min)

 Mtg Start

 Guard Time

(min)

 Mtg End

 Guard Time

(min)

 Mtg ID End

 Guard Time

(min)

Early Mtg

Start

(min)

Users attempting

to join the

meeting will be

informed that

"The meeting has

not started".

Users attempting to
join the meeting will

be informed that

"This is not a

recognized meeting

ID number".

 

You specify the parameters for each of these “consumable” resources by 
choosing the Scheduling Parameters topic of the Configure tab. 

•

 

Mtg. start guard time (min)—The number of minutes in advance of the 
requested meeting start time that ports are reserved for the meeting. 
MeetingPlace automatically adds this advance time to the requested start 
time. This time guarantees ports for early arrivals to the voice 
component of a meeting. Set this parameter to 0 minutes and use Mtg. ID 
start guard time to ensure that MeetingPlace acknowledges the meeting 
and that users hear “The meeting has not started” when they attempt to 
enter the meeting. 

•

 

Mtg. end guard time (min)—The number of minutes after the scheduled 
meeting end time that ports, or a “zero-port” meeting, will remain 
reserved. MeetingPlace adds this extra time to the reserved end time of 
the meeting. This time guarantees ports when a voice meeting overruns 
its scheduled end time. Set this parameter to 0 minutes if you want to be 
able to schedule back-to-back meetings. Set this parameter for a longer 
period if your users tend to have longer meetings and/or your system is 
relatively less busy. When your guard time expires and no ports are 
available, you will not be able to extend the voice component of your 
meeting. 

Although non-zero guard times guarantee ports before and after a 
meeting, most users simply schedule some “padding” into their 
meetings. For example, if a user wants an hour-long meeting and wants 
to pad it to allow callers time to enter the meeting, listen to the roll call 
and agenda, and greet one another, the user would simply schedule the 
meeting for 70 minutes. In this case, managing guard times can be an 
unnecessary complication.