Cisco Cisco Unified MeetingPlace for IBM Lotus Notes Guía De Instalación Rápida
Administration Center Page References for Cisco Unified MeetingPlace
Meeting Configuration Page
64
Early meeting start (minutes)
Maximum time, in minutes, before the scheduled meeting start that participants may enter
the meeting. This field does not apply to reservationless meetings.
the meeting. This field does not apply to reservationless meetings.
Restriction: This number cannot exceed the value entered in the
Meeting ID start guard time
(minutes)
field.
Recommendation: 10. If you plan to permit consecutive meetings with the same meetingID,
make sure that you set the Early meeting start parameter so that it is less than orequal to the
meeting ID start guard time.
make sure that you set the Early meeting start parameter so that it is less than orequal to the
meeting ID start guard time.
Default: 10
Last warning time (minutes)
Number of minutes before the end of a meeting when the system issues a warning.
Default: 2
Minimum meeting password
length
length
Minimum number of characters required in meeting passwords.
A value of 0 means that meeting passwords are never required, even for meetings that are
scheduled by users whose user profile
scheduled by users whose user profile
Meeting password required
field is set to Yes.
Recommendation: Follow your company guidelines for similar telecommunications
systems.
systems.
Default: 0
Maximum advance days to
schedule
schedule
How many days in advance users can schedule meetings.
Default: 300
Days until meeting statistics
purged
purged
Minimum number of days that meeting data is stored on the Application Server and Web
Server. To determine the actual date when the meeting data will be purged:
Server. To determine the actual date when the meeting data will be purged:
•
If you enter a value less than 7, then the system purges the meeting data after the
specified number plus 7 days. For example, if you enter 5, then the meeting data is
purged after 5 + 7 = 12 days.
specified number plus 7 days. For example, if you enter 5, then the meeting data is
purged after 5 + 7 = 12 days.
•
If you enter a value equal to or greater than 7 days, then the system purges the meeting
data after the specified number of days. For example, if you enter 7, then the meeting
data is purged after 7 days.
data after the specified number of days. For example, if you enter 7, then the meeting
data is purged after 7 days.
Restriction: Seven days after a meeting was scheduled to occur, the system applies the value
that you configure in this field. For example, if you set this field to “7,” the system purges
meeting statistics immediately after it applies the field value to the meeting. If you set this
field to “3,” the system purges meeting statistics three days later.
that you configure in this field. For example, if you set this field to “7,” the system purges
meeting statistics immediately after it applies the field value to the meeting. If you set this
field to “3,” the system purges meeting statistics three days later.
This field also affects Cisco Unified MeetingPlace report data. When meetings are purged,
they are no longer available for reporting purposes.
they are no longer available for reporting purposes.
Default: 38
Allow vanity meeting IDs
Whether users may request a specific meeting ID when scheduling a meeting. If a user
requests a meeting ID that is already reserved for another meeting, the system prompts the
user to select another meeting ID.
requests a meeting ID that is already reserved for another meeting, the system prompts the
user to select another meeting ID.
If you select No, the system generates a unique, randomly generated ID for every scheduled
meeting. Users cannot change the assigned meeting IDs.
meeting. Users cannot change the assigned meeting IDs.
Default: Yes
Table 39
Field Reference: Meeting Configuration Page (continued)
Field
Description