The Cisco Unified MeetingPlace 3515 Media Server includes one Audio Blade (250 ports) and one Video Blade that can support either 24 or 48 video user licenses based on video bandwidth settings.

The Cisco Unified MeetingPlace 3515 Media Server cannot be modified in the field to change any hardware configuration, only upgrade software can be applied to the Audio Blades and Video Blades in this fixed one RU chassis.

Audio Blades and Video Blades require one static IP address each and one Ethernet switch cable and connection for control by the Application Server.

Cisco Unified MeetingPlace 3545 Media Server

A four slot chassis that provides redundant power supplies and redundant power plugs to separate power sources.

Each Cisco Unified MeetingPlace 3545 Media Server can have any mixture of modular Audio Blades and Video Blades installed in any order.

Each Cisco Unified MeetingPlace 3545 Media Server is comprised of at least one Audio Blade and optionally, one to four Video Blades.

A mimimum of one Audio Blade is required for a Cisco Unified MeetingPlace system.

Video Blades (and video user licenses) are optional.

Each Audio Blade and each Video Blade requires one Ethernet IP address to be statically assigned and one switch port assigned.

The Application Server controls the audio and video SIP connections to each blade independently.

You can purchase Audio Blades and Video Blades for "active" redundancy, without licenses. For example: Audio user licenses are sold to support 250 ports and there are two Audio Blades installed, for a total of 500 ports available and active. The system capacity will be governed by the licenses for the total number of audio callers into one or many meetings. If a blade fails, the system will simply stop using it and place callers onto the "redundant" Audio Blade. A minor alarm will be registered if a blade drops off unexpectedly.

There is no limit on the number of Audio Blades you can have, but there is a limit of four Video Blades per Audio Blade.

Web Server Requirements

Web Server Models

The Cisco Unified MeetingPlace Web Server is installed on a Cisco Media Convergence Server (MCS). The Web Server must be one of the following Cisco MCS models:

Cisco MCS 7835

Note: Cisco Unified MeetingPlace supports the Cisco MCS 7835 models only for systems that are upgrading a Web Server from Release 6.0 to Release 7.0. For Cisco Unified MeetingPlace systems that use new hardware for the Web Server, we require a Cisco MCS 7845 H2/I2 model.

Cisco MCS 7835-H1-RC1

Cisco MCS 7835-H1-RC2

Cisco MCS 7835-I1-RC1

Cisco MCS 7835-I1-RC2

Cisco MCS 7835-H2-RC1

Cisco MCS 7835-H2-RC2

Cisco MCS 7835-I2-RC1

Cisco MCS 7835-I2-RC2

The Cisco MCS 7835 supports a maximum of 250 web sessions (non-SSL). If IBM Lotus Notes is co-resident on the system, then a 20% reduction in web sessions is supported.

Note: The Cisco MCS 7835 models must have at least 4 GB of memory using these memory modules:

MEM-7835-H2-1GB=

MEM-7835-I2-2GB=

Cisco MCS 7845

Cisco MCS 7845-H1-RC1

Cisco MCS 7845-H1-RC2

Cisco MCS 7845-I1-RC1

Cisco MCS 7845-I1-RC2

Cisco MCS 7845-H2-RC1

Cisco MCS 7845-H2-RC2

Cisco MCS 7845-I2-RC1

Cisco MCS 7845-I2-RC2

The Cisco MCS 7845 supports a maximum of 500 web sessions (non-SSL). If IBM Lotus Notes is co-resident on the system, then a 20% reduction in web sessions is supported. A cluster of web servers supports maximum of 1000 web sessions total.

SQL Server Requirements

If you choose the local SQL Server option, the system automatically installs SQL Server 2000 (Service Pack 4) during the Web Conferencing software installation. Microsoft SQL Server 2000 (Service Pack 4) is included in the Web Conferencing Release 7.0 installer.

If you choose the remote SQL Server option, you must install SQL Server 2000 (Service Pack 4) before you install Web Conferencing. You must also install and configure your SQL Server to be case insensitive because Web Conferencing supports only SQL Server case-insensitive configurations. If you configure your SQL Server to be case sensitive, Web Conferencing will not function properly.

You may choose to deploy more complex, remote SQL Server topologies, such as a server farm. To properly operate in a remote SQL Server configuration, Cisco Unified MeetingPlace Web Conferencing requires an Open DataBase Connectivity (ODBC) Data Source Name (DSN) that points to an installation of Microsoft SQL Server 2000 with Service Pack 4 or Microsoft SQL Server 2005 with Service Pack 2 (in backward compatibility mode) with correct permissions to the MPWEB database, and on the Cisco Unified MeetingPlace Web Server the Microsoft SQL Server 2005 backward compatibility software – DMO (Distributed Management Objects) component.

In such a topology, customers are responsible for supporting and ensuring the stability and performance of the remote SQL Server deployment. Any decrease in SQL Server transaction performance or network latency between the Cisco Unified MeetingPlace Web Conferencing server and the remote SQL Server can have a negative impact on Web Conferencing performance up to and including a complete system outage depending on the scale of the slow down. Cisco assumes that the SQL environment is appropriately sized and properly installed by the customer prior to installing Cisco Unified MeetingPlace Web Conferencing, and is monitored and maintained properly after installing Web Conferencing.

NOTE: You must install and configure a remote SQL Server to be case insensitive because Web Conferencing supports only SQL Server case-insensitive configurations. If you configure your SQL Server to be case sensitive, Web Conferencing will not function properly.

Networking Requirements

The Web Server must be configured with two static IP addresses on the same subnet.

Cisco Unified MeetingPlace Web Servers must be connected to network switch ports that are configured for 100/1000 Mb full duplex.

Cisco Unified MeetingPlace Web Conferencing requires additional disk space for recording. See the "Recording Size" section in the Configuration Guide for Cisco Unified MeetingPlace Release 7.0 or the online help in the administrator interface for more information about recording.

You must set the network port configuration on your Web Server to "Enable NetBIOS over TCP/IP" and not "Default."