Cisco Cisco Unified MeetingPlace Audio Server Release Notes
Release Note, Cisco MeetingServer 5.1.1
Page 2 of 13
78-16459-01
Cisco Systems
Revision Date: 3/11/05
1 Overview
This document describes Cisco MeetingServer 5.1.1 release, including fixes from MeetingPlace Server
5.1. Use this document when installing the Cisco MeetingPlace M3 server with Cisco
MeetingServer 5.1.1.
Important: For the most current version of this document, visit the MeetingPlace Customer Support
Reference Center.
5.1. Use this document when installing the Cisco MeetingPlace M3 server with Cisco
MeetingServer 5.1.1.
Important: For the most current version of this document, visit the MeetingPlace Customer Support
Reference Center.
2 Naming Conventions Used in This Document
Throughout the remainder of this document, we refer to Cisco MeetingServer as “MeetingServer” or
“MeetingPlace.”
“MeetingPlace.”
3 Requirements
3.1 Hardware
Requirement
s
s
Note: Release 5.1.1 does not support any EISA or PCI hardware platforms or optional cards from those
systems.
systems.
The minimum hardware requirements for Release 5.1.1 are:
•
MeetingPlace M3 Server with 1 Smart Blade (for PSTN) or 2 Smart Blades (for IP).
3.2 Software
Requirement
s
s
The minimum system requirements to run MeetingTime from an IBM-compatible computer are as
follows:
follows:
•
16 MB RAM (24 MB for Windows NT), Windows 98, Windows NT 4 or later, Windows 2000, or
Windows XP.
•
System Managers and Technicians are required to upgrade to MeetingTime Release 5.1.0.x to
monitor MeetingServer 5.1.
•
Attendants, Contacts, and End Users may use the following workstation clients with
MeetingServer 5.1: MeetingTime 5.0.0.x.
•
In MeetingTime 5.0.x, the “In Session” tab only shows meeting IDs and meeting names in the initial
list of in-session meetings. The scheduler’s name displays when a meeting is selected or when a new
meeting comes in session. This feature allows MeetingTime to display in-session meetings
significantly faster. To disable this feature, the registry setting
HKEY_CURRENT_USER\Software\Latitude\MeetingTime\settings\ShowInSessionSchedNames
must be changed from 0 to 1. If this registry setting does not exist, MeetingTime behaves as if
ShowInSessionSchedNames is set to 0.
meeting comes in session. This feature allows MeetingTime to display in-session meetings
significantly faster. To disable this feature, the registry setting
HKEY_CURRENT_USER\Software\Latitude\MeetingTime\settings\ShowInSessionSchedNames
must be changed from 0 to 1. If this registry setting does not exist, MeetingTime behaves as if
ShowInSessionSchedNames is set to 0.