Cisco Cisco Unified MeetingPlace Audio Server Manual De Manutenção
Cisco MeetingServer 5.1 System Manager’s Guide
79
Cisco Systems
March 2003
•
Mtg. ID start guard time (min)—The number of minutes before a
meeting that the associated meeting ID or DID/DDI number is reserved.
Both this parameter and Mtg. ID end guard time control when meeting
IDs become available to be re-used. This is to ensure that two meetings
do not have the same ID at the same time. Therefore, callers will not
inadvertently enter the wrong meeting.
meeting that the associated meeting ID or DID/DDI number is reserved.
Both this parameter and Mtg. ID end guard time control when meeting
IDs become available to be re-used. This is to ensure that two meetings
do not have the same ID at the same time. Therefore, callers will not
inadvertently enter the wrong meeting.
If users attempt to enter the meeting before the meeting ID start guard
time begins, they are informed, “This is not a recognized meeting ID
number”. Callers in the voice conference hear it as a voice prompt. Users
logging into a web conference see it on their screen.
time begins, they are informed, “This is not a recognized meeting ID
number”. Callers in the voice conference hear it as a voice prompt. Users
logging into a web conference see it on their screen.
After the Mtg. start guard time begins, callers attempting to enter the
voice conference hear the message “The meeting has not started.” The
recommended value for this parameter is 15 minutes.
voice conference hear the message “The meeting has not started.” The
recommended value for this parameter is 15 minutes.
Mtg. ID end guard time (min)—The number of minutes after a meeting
that the associated Meeting ID or DID/DDI number is reserved. If callers
call into a voice conference during this period, they hear “The meeting
has ended.” Users logging into a web conference see it on their screen.
After this period, users will be informed, “This is not a recognized
meeting ID number.” The recommended value for this parameter is 15
minutes.
that the associated Meeting ID or DID/DDI number is reserved. If callers
call into a voice conference during this period, they hear “The meeting
has ended.” Users logging into a web conference see it on their screen.
After this period, users will be informed, “This is not a recognized
meeting ID number.” The recommended value for this parameter is 15
minutes.
Note: If two people are on a zero-port meeting and forget to log
out, the meeting will continue extending itself for a maximum of
24 hours. The meeting will expire if it encounters a meeting ID
conflict.
out, the meeting will continue extending itself for a maximum of
24 hours. The meeting will expire if it encounters a meeting ID
conflict.
Managing Port Scheduling Using Run Times
Run times determine how early someone can call into a meeting before its
scheduled start time, how long a meeting can be extended, and when ports
should be released.
scheduled start time, how long a meeting can be extended, and when ports
should be released.
Run time parameters take affect at the start of each meeting. As each new
meeting begins, the system will look to the current run time settings to
determine how to manage the meeting.
meeting begins, the system will look to the current run time settings to
determine how to manage the meeting.
•
End of mtg. warning (min)—Determines when users are first warned that
their meeting will end. (Recommended time is 10 minutes.) Users
receive another warning two minutes before the meeting ends.
their meeting will end. (Recommended time is 10 minutes.) Users
receive another warning two minutes before the meeting ends.
•
Extend meeting (min)—The time that a meeting gets extended if the time
runs over and ports are available (0 to 60 minutes). Callers receive
warnings informing participants when the meeting will end. The system
can continue to extend the meeting time provided ports are not reserved
for other meetings. The recommended value for this parameter is 15
minutes.
runs over and ports are available (0 to 60 minutes). Callers receive
warnings informing participants when the meeting will end. The system
can continue to extend the meeting time provided ports are not reserved
for other meetings. The recommended value for this parameter is 15
minutes.