Recommendation: 30. To ensure that meeting IDs are available for reuse, decrease this value if the number of simultaneous meetings to be held on your system is about the same as the number of available meeting IDs.

+

Recommendation: 30. To ensure that meeting IDs are available for reuse, decrease this value if the number of simultaneous meetings to be held on your system is about the same as the number of available meeting IDs. If you also plan to permit consecutive meetings with the same meeting ID, make sure that you set the Early Meeting start parameter so that it is less than or equal to the configured Start Guard time.

+

Line 369:

Line 370:

If you select No, or if ports are not available at the end of the meeting, callers receive a warning that the meeting will end. The warning time is determined by the [[Cisco Unified MeetingPlace, Release 7.0 -- Meeting Configuration Page#Last warning time (minutes)|Last warning time (minutes)]] field.

If you select No, or if ports are not available at the end of the meeting, callers receive a warning that the meeting will end. The warning time is determined by the [[Cisco Unified MeetingPlace, Release 7.0 -- Meeting Configuration Page#Last warning time (minutes)|Last warning time (minutes)]] field.

+

+

'''Note:''' If you have two consecutive meetings with the same meeting ID, the first occurrence of the meeting (Meeting1) will be extended if the second occurrence (Meeting2) complies with the following condition:

+

+

Extend Meeting time is less than (Meeting2StartTime - StartGuardTime) - (Meeting1EndTime + EndGuardtime)

+

Line 384:

Line 390:

-

Recommendation: 10

+

Recommendation: 10. If you plan to permit consecutive meetings with the same meeting ID, make sure that you set the Early meeting start parameter so that it is less than or equal to the meeting ID start guard time.

Number of voice ports that are reserved as floater ports. Floater ports can be used by any meeting to accommodate unanticipated additional attendees. Configuring voice floater ports reduces the number of ports that are available for scheduling meetings.

Number of voice ports to allow for scheduling meetings that exceed the number of available voice ports on the system. Configuring voice overbook ports increases the risk of users being unable to attend scheduled meetings.

If you use this feature, you assume that users who are scheduled to attend meetings do not always attend, leaving their reserved voice ports unused. Once all voice ports are in use, other users who try to attend a voice meeting will not be able to get through.

Number of video ports to allow for scheduling meetings that exceed the number of available video ports on the system.

If you use this feature, you assume that users who are scheduled to attend meetings do not always attend or use video, leaving their reserved video ports unused. Once all video ports are in use, any other video users who try to attend a meeting will join audio-only; if no voice ports are available at that time, then those users will not be able to attend.

Display only. Number of web ports for scheduled and reservationless meetings on the system, determined by the installed webconf and maxweb licenses. To view installed and enabled licenses, see Displaying Licenses.

The value determines the maximum number of possible simultaneous connections to Cisco Unified MeetingPlace using the full web meeting room.

Web ports are allocated on an ad-hoc basis and are never reserved for meetings.

Before the meeting ID start guard time, users who try to attend the meeting hear or see on the screen: "This is not a recognized meeting ID number." During the meeting ID start guard time period, users hear: "The meeting has not started."

Meeting ID start guard times are not applied to reservationless meetings or meetings that begin immediately.

Recommendation: 30. To ensure that meeting IDs are available for reuse, decrease this value if the number of simultaneous meetings to be held on your system is about the same as the number of available meeting IDs. If you also plan to permit consecutive meetings with the same meeting ID, make sure that you set the Early Meeting start parameter so that it is less than or equal to the configured Start Guard time.

During the meeting ID end guard time, users who try to attend the meeting hear or see on the screen: "The meeting has ended." After the meeting ID end guard time period, users hear: "This is not a recognized meeting ID number."

Meeting ID end guard times are not applied to reservationless meetings or meetings that are user-terminated before the scheduled end time.

Recommendation: 15. To ensure that meeting IDs are available for reuse, decrease this value if the number of simultaneous meetings to be held on your system is about the same as the number of available meeting IDs.

Default: 30

Extend meeting (minutes)

Whether to extend meetings if they run over the requested duration and if ports are available. Meetings may continue to be extended as long as ports are available, up to the Maximum meeting length (minutes) field value. Specifically for web meeting rooms:

For meetings scheduled with zero locations, the web meeting is extended as long as there is at least one participant in the web meeting room.

For meetings scheduled with at least one location, the web meeting is extended only if there are at least two voice meeting participants.

If you select Yes, also enter the number of minutes to extend meetings.

If you select No, or if ports are not available at the end of the meeting, callers receive a warning that the meeting will end. The warning time is determined by the Last warning time (minutes) field.

Note: If you have two consecutive meetings with the same meeting ID, the first occurrence of the meeting (Meeting1) will be extended if the second occurrence (Meeting2) complies with the following condition:

Extend Meeting time is less than (Meeting2StartTime - StartGuardTime) - (Meeting1EndTime + EndGuardtime)

Default: Yes, 15

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.

Recommendation: 10. If you plan to permit consecutive meetings with the same meeting ID, make sure that you set the Early meeting start parameter so that it is less than or equal 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

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 Meeting password required field is set to Yes.

Recommendation: Follow your company guidelines for similar telecommunications systems.

Default: 0

Maximum advance days to schedule

How many days in advance users can schedule meetings.

Default: 300

Days until meeting statistics 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:

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.

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.

Restriction: Changes to this field apply only to meetings that are scheduled after the field is changed. For each meeting, the system applies the field value that was configured at the time the meeting was scheduled.

This field also affects Cisco Unified MeetingPlace report data. When meetings are purged, they are no longer available for reporting purposes.

Default: 120

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.

If you select No, the system generates a unique, randomly generated ID for every scheduled meeting. Users cannot change the assigned meeting IDs.

Default: Yes

Minimum scheduled meeting ID length

Minimum number of characters in meeting IDs.

Note that longer meeting IDs are more secure, because they are more difficult to guess.

Restriction: If this value is set to 3 and the scheduler does not enter a vanity meeting ID, the system assigns a four-digit meeting ID to all new meetings.

This field was called "Minimum meeting ID length" in Release 7.0.1.

Default: 4

Enable rescheduled recurring meetings

Whether to enable users to reschedule recurring meetings.

Default: Yes

Disconnect empty port (minutes)

Number of minutes after the scheduled start time that ports are held after all participants leave, even when the scheduled meeting time is not over. This time accounts for longer meetings when people break and return to the meeting. This time also applies if no one comes to the meeting.

For meetings that were scheduled with the "Number of Participants" set to 0, this field applies only when one person remains in the web meeting.

This parameter does not apply to reservationless meetings.

Default: 30

Early meeting port release (minutes)

Number of minutes before the scheduled end of a meeting that ports are released if no ports are in use for that meeting.

For meetings that were scheduled with the "Number of Participants" set to 0, this field applies only when one person remains on the web conference.

Default: 5

Auto-Answer Devices

Meeting controls device

Determines whether the meeting owner or the meeting itself controls when auto-answer devices are disconnected from each meeting:

No-When the meeting owner leaves the meeting, all auto-answer devices are disconnected from the meeting.