The Hardware Media Server should be on the same local network segment as the Application Server. Cisco Unified MeetingPlace does not support Hardware Media Server blades that are remotely located.

The Hardware Media Server should be on the same local network segment as the Application Server. Cisco Unified MeetingPlace does not support Hardware Media Server blades that are remotely located.

+

Line 1,752:

Line 1,782:

* The time must be synchronized between the two Application Servers. This is required to resolve conflicts when the same piece of data is modified simultaneously in both Application Servers.

* The time must be synchronized between the two Application Servers. This is required to resolve conflicts when the same piece of data is modified simultaneously in both Application Servers.

* If the primary and failover Application Servers share a common set of Audio and Video Blades, you must add all the Audio Blades to both Applications Servers. Be sure to use the same passwords and SNMP community names on the two systems or the failover mechanism will not work.

* If the primary and failover Application Servers share a common set of Audio and Video Blades, you must add all the Audio Blades to both Applications Servers. Be sure to use the same passwords and SNMP community names on the two systems or the failover mechanism will not work.

+

* If the primary and failover Application servers are in different data centers (dual data center deployment), then the same VLAN must be extended between both data centers for the replication and failover to be supported.

'''Note: ''' Directory Service between two Application Servers is not supported in a failover deployment.

'''Note: ''' Directory Service between two Application Servers is not supported in a failover deployment.

-

-

== Hardware Requirements ==

== Hardware Requirements ==

Line 1,771:

Line 1,800:

-

'''NOTE:''' For information about different system capacity limits for several key configurations, see http://www.cisco.com/en/US/docs/voice_ip_comm/meetingplace/7x/english/technical_references/system_capacity_field_notice.html.

'''Note:''' The number of supported audio-only calls drops to a maximum of 300 SRUs at a maximum call rate of 3cps when you are using the G.711 codec.

+

|

|

1000

1000

+

+

'''Note:''' The number of supported audio-only calls drops to a maximum of 600 SRUs at a maximum call rate of 6cps when you are using the G.711 codec.

+

|

|

-

1300

+

1500

|-

|-

|

|

Line 1,982:

Line 2,017:

'''Notes: '''

'''Notes: '''

+

+

* IMPORTANT: The DL380-G6 Server (AX690A, AX693A) is shipped with an internal USB Drive. The drive conflicts with the custom Linux OS and causes an illegal opcode error. The workaround is to remove the USB Drive from the system.

+

*:There is a video clip at the following URL that illustrates how to remove the USB drive.

*:If the URL does not work, visit https://videosharing.cisco.com:8443/ and search for MeetingPlace.

+

*:You can also use these steps to remove the USB Drive:

+

*:1. Remove the top cover of the server.

+

*:2. Look on the left-side of the server toward the middle for a USB flash drive. It is located near the edge of the secondary (internal) cover next to the connectors for two cables coming from the HDDs.

+

*:3. Pull the drive out and close the cover.

+

+

+

* The Cisco MCS 7845-I3-RC2 does not support the Web Server for Cisco Unified MeetingPlace Release 8.0.

* The Cisco MCS 7845-I3-RC2 does not support the Web Server for Cisco Unified MeetingPlace Release 8.0.

* Cisco MCS 7845-H2/I2-RC1 and MCS 7835-I2-RC1 servers are supported for upgrades only. However, they are not recommended for use with Cisco Unified MeetingPlace Release 8.0 due to their smaller hard drives.

* Cisco MCS 7845-H2/I2-RC1 and MCS 7835-I2-RC1 servers are supported for upgrades only. However, they are not recommended for use with Cisco Unified MeetingPlace Release 8.0 due to their smaller hard drives.

* For information about Cisco Security Agent, see http://www.cisco.com/en/US/products/sw/secursw/ps5057/tsd_products_support_series_home.html.

* For information about Cisco Security Agent, see http://www.cisco.com/en/US/products/sw/secursw/ps5057/tsd_products_support_series_home.html.

+

=== Setting the Write Cache on a RAID Controller ===

+

+

For optimal system performance you should check the Default Write setting on your RAID controller. You can set Default Write to three settings: Write Back with BBU, Write Through and Always Write Back.

+

+

* Set Default Write to '''Write Back with BBU''' if you have installed a battery backup unit on your RAID controller. In the event of a system power loss, the battery backup unit preserves the content of the controller cache memory.

+

+

* In the event that the battery backup unit fails or goes offline to a re-learn cycle, the '''Write Back with BBU''' setting automatically fails back to '''Write Through''' mode. Without a working battery backup unit, the '''Write Through''' setting is safer, but it also brings a performance penalty on the I/O subsystem of the host device.

+

+

* If you need to remove the battery backup unit for repairs, you should explicitly set Default Write to '''Write Through''' mode and enable the cache explicitly (Disk Cache option). This should give you better but not optimal performance. When the faulty battery is replaced, you can safely return the Default Write setting to '''Write Back with BBU''' mode.

+

+

* If the host that houses your RAID controller is connected to an uninterruptible power supply unit, you can set Default Write to '''Always Write Back''' mode.

=== Express Media Server Requirements ===

=== Express Media Server Requirements ===

Line 2,267:

Line 2,326:

|

|

-

300

+

320

|

|

Line 2,276:

Line 2,335:

-

'''Note: ''' In practice, some users may be restricted to scheduling Standard Rate video ports while others are able to schedule High Rate video ports. The total maximum system video capacity, therefore, is between 160 and 300 based on the maximum allowable hardware of eight Video Blades.

+

'''Note: ''' In practice, some users may be restricted to scheduling Standard Rate video ports while others are able to schedule High Rate video ports. The total maximum system video capacity, therefore, is between 160 and 320 based on the maximum allowable hardware of eight Video Blades.

Cisco Unified MeetingPlace supports the following languages for Audio conferencing and Cisco WebEx web conferencing. This includes all voice prompts, WebEx user interfaces, scheduling tools, except System Administration inferfaces. A maximum of four languages per system is supported, where end users choose their default language and guest users are prompted to pick from a list through a voice menu option.

+

+

* US English (Default)

+

* UK English

+

* French & French Canadian

+

* German

+

* Spanish (Latin America)

+

* Portuguese (Brazil)

+

* Japanese

+

* Russian (audio/video)-English for WebEx

+

* Chinese (Traditional & Simplified)

+

+

+

=== Directory Service ===

-

Cisco Unified MeetingPlace Directory Service enables you to populate and synchronize the Cisco Unified MeetingPlace user database with the contents of the Cisco Unified Communications Manager user database. The Cisco Unified Communications Manager user database is typically integrated with an LDAP directory. The following LDAP directories are supported by Cisco Unified MeetingPlace Directory Service:

+

Cisco Unified MeetingPlace Directory Service enables you to populate and synchronize the Cisco Unified MeetingPlace user database with the contents of the Cisco Unified Communications Manager user database, as well as provide encrypted End User Authentication. The Cisco Unified Communications Manager user database is typically integrated with an LDAP directory. UC Manager End User Authentication also supports secure LDAP (sLDAP) configuration. The following LDAP directories are supported by Cisco Unified Communications Manager to MeetingPlace Directory Service:

Cisco Unified MeetingPlace Directory Service (via UC Manager LDAP integration) may also be optionally configured to work with Webex to provide on premises End User Authentication and automatic profile propegation to Webex for "host" accounts. This must be requested upon provisioning of the Webex Site at installation. The MeetingPlace to Webex LDAP integration is called Directory Service "SSO" Single Sign On which is optional based on customer requirements for LDAP use. No passwords are stored on Webex nor passed to the Webex cloud for authentication.

+

+

All "Host" users must be able to resolve to the MeetingPlace Application Server fully qualified domain name (FQDN) which is deployed behind the company firewall, for instance they must be on the corporate network and VPN connection before "hosting" any meetings. If your profiled users cannot access the corporate network, then a non-Directory Service implementation is advised. MeetingPlace profiles can be exported and imported into Webex Site via Administration interface using Excel CSV formated files.

For MeetingPlace 8 Systems deployed with MeetingPlace Scheduling model the End User Authentications may also be done via the MeetingPlace Internal Web Server with the following 5 options (choose 1 method for End User Authentication) or you may still choose the UC Manager LDAP End USer Authentication method.

-

License requirements are based on the features you use. For a list of all licenses, see the ''Planning Guide for Cisco Unified MeetingPlace Release 8.0 ''at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment.

+

* MeetingPlace Local UserID/Password

+

* LDAP - this supports mutlidomain environments

+

* LDAP, then MeetingPlace - this support single domain environments only

+

* Windows Integrated Authentication (WIA) - all MeetingPlace PRofiled users must use Windows OS and the MeetingPlace Web server must be join the domain.

+

* Third Party Authentication Servers - supports Siteminder and others

+

* Web HTTP

-

=== Reservationless Single Number Access (RSNA) Requirements ===

+

=== License Requirements ===

-

To use Cisco Unified MeetingPlace with RSNA, you must use Cisco Unified Communications Manager. There are no other system requirements specific to RSNA.

+

License requirements are based on the features you use. For a list of all licenses, see the ''Planning Guide for Cisco Unified MeetingPlace Release 8.0 ''at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment.

+

=== Reservationless Single Number Access (RSNA) Requirements ===

+

Reservationless Single Number Access is used in an Audio only deployment model and is not support with Webex web conferening integration. To use Cisco Unified MeetingPlace with RSNA, you must use Cisco Unified Communications Manager using all SIP Trunking. There are no other system requirements specific to RSNA.

* MeetingPlace Application Server Webex TSP only support SOCKS Web Proxy servers (Not HTTP Proxy) so please allow direct firewall access to Webex Site IPs directly. Often there are delay issues when proxy servers are used and the integration to Webex must be able to be maintained continuously via internet without delays, otherwise it will affect user response times.

* Cisco Webex Node for MCS is currently not supported with the Webex Global Site Backup system. If you want a fully redundant option with GSB, submit a new Webex Node for MCS request to Webex Provisioning to deploy a redundant Node which is ‘homed’ to the GSB data center instead of the primary. You must deploy an MCS server with the Webex Node for MCS software for this function only in your network.

+

+

* A Cisco WebEx integration supports a maximum of 1000 Webex sessions on either multiple Webex Node for MCS's or connected to Webex Collaboration Cloud per system in multiple meetings.

+

* A single Meeting Center meeting with MeetingPlace Audio supports a maximum of audio and web 125 attendees.

+

* A Cisco Webex Scheduling model also supports Webex Event Center which supports a maximum of 500 MeetingPlace Audio attendees in a single meeting. However, Event Center can also provide "Audio Broadcast function which only the "Speakers" for a large conference would connect to the MEetingPlace Audio system and all attendees would receive the entire Web sharing, video and MP Audio all bridged into a single web HTTPS stream via end user's PC which reduces the need for everyone to dial into the MeetingPlace Audio system for meetings.

* Cisco Webex Enterprise Edition that supports Meeting Center, Event Center and Training Center (Support Center is also available but does not require MeetingPlace Audio unless Support personnel escalate to a full Meeting Center meeting with multiple attendees.)

For platform-specific requirements, see http://support.webex.com/support/system-requirements.html

+

===== Webex Scheduling Option with Mobile Device Integrations=====

+

* Cisco WebEx supports iPhone, Blackberry mobile devices ability to easily join a Webex meeting with automatic callback to a mobile device. When integrating to MeetingPlace Audio with Webex, the iPhone or Blackberry Webex client must be programmed without any Plus "+" dialing in the phone number field. Please enter the mobile phone number without a "+".

+

+

+

+

+

For platform-specific requirements, see http://support.webex.com/support/system-requirements.html

=== Cisco Unified MeetingPlace for IBM Lotus Notes Release 8.0 ===

=== Cisco Unified MeetingPlace for IBM Lotus Notes Release 8.0 ===

-

'''Note: ''' This integration is only supported when using a Cisco Unified MeetingPlace Scheduling deployment option.

+

'''Notes: '''

+

* This integration is only supported when using a Cisco Unified MeetingPlace Scheduling deployment option.

+

* Multiple clusters are not supported for the IBM Lotus Notes for Cisco Unified MeetingPlace integration.

* Also see the server requirements at http://publib.boulder.ibm.com/infocenter/sametime/v7r5m1/index.jsp?topic=/com.ibm.help.sametime.install.doc/st_inst_inst_softwarerequirements.html.

+

*: Also see the server requirements at http://publib.boulder.ibm.com/infocenter/sametime/v7r5m1/index.jsp?topic=/com.ibm.help.sametime.install.doc/st_inst_inst_softwarerequirements.html.

-

IBM Lotus Sametime Server Release 8.0.1

+

* IBM Lotus Sametime Standard Server Release 8.0.1

-

* Also see the server requirements at http://www-01.ibm.com/support/docview.wss?rs=477&uid=swg27010738.

+

*: Also see the server requirements at http://www-01.ibm.com/support/docview.wss?rs=477&uid=swg27010738.

'''Note: ''' If you also deploy the Cisco Phone Control and Presence with IBM Lotus Sametime integration, then you must use IBM Lotus Sametime Server 8.0.1 and install the following IBM patches to disable the IBM phone icon: 3AAAFEAB, 49D5219C, 643A31, 662A775A, 77D5E39D.

'''Note: ''' If you also deploy the Cisco Phone Control and Presence with IBM Lotus Sametime integration, then you must use IBM Lotus Sametime Server 8.0.1 and install the following IBM patches to disable the IBM phone icon: 3AAAFEAB, 49D5219C, 643A31, 662A775A, 77D5E39D.

* Currently this integration does not support any level of SSO or LDAP integration capability.

+

* The CallBack feature via mobile devices requires the Webex client on the mobile device be configured with the full dialable mobile phone number without the use of the "+" symbol in the front of the number. Please remove "+" when use a MeetingPlace Audio integrated Webex site.

+

* iPAD is currently not supported with MeetingPlace Audio systems because iPAD is VoIP enabled only via internet.

== Upgrading and Migration Requirements ==

== Upgrading and Migration Requirements ==

Line 3,737:

Line 3,850:

-

Due to differences in architecture, you can only migrate a Cisco Unified MeetingPlace Release 6.0 system to Cisco Unified MeetingPlace Release 8.0. When you migrate, you export data from the Cisco Unified MeetingPlace Release 6.0 system, save it to a remote location, perform a fresh installation of Cisco Unified MeetingPlace Release 8.0 from the DVD, transfer the backup file to the newly-installed system, and import data from backup file.

+

Due to differences in architecture, you can only migrate a Cisco Unified MeetingPlace Release 6.0 system to Cisco Unified MeetingPlace Release 8.0.

-

+

# If you are at an earlier release, first upgrade to Release 6.0 Maintenance Release 5.

-

You can only migrate from Cisco Unified MeetingPlace Release 6.0 Maintenance Release 5. If you are on an earlier release of Cisco Unified MeetingPlace, you must upgrade to Release 6.0 Maintenance Release 5.

To migrate your system from Cisco Unified MeetingPlace Release 6.0 to Release 8.0, first migrate to Release 7.0 and then upgrade from Release 7.0 to Release 8.0.

+

# Upgrade from Release 7.0 to Release 8.0.

-

* For information about migrating from Cisco Unified MeetingPlace Release 6.0 to Release 7.0, see the ''Installation and Upgrade Guide for Cisco Unified MeetingPlace Release 7.0'' on the DocWiki at http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_7.0_--_Migrating_to_Cisco_Unified_MeetingPlace_Release_7.0_from_Release_6.0.

Note: The SOCKS configuration is an optional configuration and is not used unless you specifically configure it. Other types of proxies (such as HTTP) are not supported by Cisco Unified MeetingPlace for Cisco WebEx connectivity

The Hardware Media Server supports escalation of audio calls to video if the endpoint is video-enabled.

This section lists the incoming and outgoing ports that are used by the various components of the Cisco Unified MeetingPlace Release 8.0 system. The information refers to Cisco Unified MeetingPlace Scheduling deployment options.

Use these tables to make sure that your firewalls do not block access to Cisco Unified MeetingPlace from users or integrated systems, and to make sure that you do not block communication among the Cisco Unified MeetingPlace components and servers.

Note: The ports that you do not need to expose to system administrators or end users are used for local communication between the Cisco Unified MeetingPlace elements or between Cisco Unified MeetingPlace and local services such as Cisco Unified Communications Manager or Microsoft Exchange. Such ports should be blocked in the DMZ or external firewall, but should not be blocked between internal components of the Cisco Unified MeetingPlace solution.

Network Time Protocol communication from the Web Servers and Hardware Media Servers

Expose to Web Server in the DMZ

SNMP

UDP

161

SNMP configuration

Expose to system administrators

-

TCP

1270-1279

For Cisco WebEx

-

MP_REPL

TCP

2008

Database replication between the active and standby servers for Application Server failover

-

-

TCP

2000-2009

For Cisco WebEx

-

GWSIM

TCP

5003, 5005

Receive attachments from the external Web Server to Application Servers (active server and standby server, if one exists) in segmented meeting access configurations.

Expose to Web Server in the DMZ.

Used in segmented meeting access configurations.

If you configured your network for reverse connection, where your Web Servers are configured with a Cisco Unified MeetingPlace hostname instead of an IP address, the Application Server can initiate a reverse connection to the Web Server in the DMZ when port 5003 inbound is blocked.

SIP

TCP UDP

5060

SIP B2BUA

-

-

TCP

7676

Accept the connection from the Cisco WebEx Node

-

HTTP

TCP

8080

HTTP services

-

HTTP

TCP

9090

Media Server Administration

Expose to system administrators

SIP

TCP UDP

61002

Recording signaling

-

Recording control

TCP

61003

Recording control

For remote RSS servers only

HTTP

TCP

61004

Communication from the external Web Server to the Application Server for prompts, recordings, attachment access, and login service for remote users

For external users to participate in web meetings, access must be granted from the Internet to the Web Server in the DMZ. However, access to port 80 may be closed if the Web Server is configured for HTTPS and you open TCP port 443.

HTTPS

TCP

443

Secure user web access

Cisco Unified MeetingPlace for Microsoft Outlook client

(Optional) Expose to system administrators and end users. If you have external users, then grant access from the Internet to the Web Server in the DMZ.

SQL

TCP

1433

Communication between the Web Server and the SQL Server database

-

RTMP

TCP

1627

Web meeting room

Note: This port is only used for systems that were upgraded to Release 8.0 from Release 7.0.

(Optional but recommended for best performance) Expose to system administrators and end users. If you have external users, then grant access from the Internet to the Web Server in the DMZ.

This is an optional configuration that is not used unless you specifically configure it. The standard SOCKS port is 1080 but is configurable. Other types of proxies (such as HTTP) are not supported by Cisco Unified MeetingPlace for Cisco WebEx connectivity.

Control connection between the external Web Server and Application Servers (active server and standby server, if one exists) in segmented meeting access configurations

Open bidirectional

If you configured your network for reverse connection, where your Web Servers are configured with a Cisco Unified MeetingPlace hostname instead of an IP address, the Application Server can initiate a reverse connection to the Web Server in the DMZ when port 5003 inbound is blocked.

Cisco WebEx Node for MCS (including Cisco WebEx Cloud)

HTTPS

TCP

443

Tunnel meeting information from the Cisco WebEx Node to the Cisco WebEx cloud

MCS-7835: two connections max with SSLv3

MCS-7845: four connections max with SSLv3

Only outbound firewall to Internet

-

TCP

7676

Control connection with the Application Server

Internal network use

Web Server

NTP

UDP

123

Time synchronization between Web Servers and Application Server

-

Control connection

TCP

5003

Control connection between Web Servers and the Application Server

-

-

TCP

5003, 5005

Control connection between the external Web Server and Application Servers (active server and standby server, if one exists) in segmented meeting access configurations

Open bidirectional

If you configured your network for reverse connection, where your Web Servers are configured with a Cisco Unified MeetingPlace hostname instead of an IP address, the Application Server can initiate a reverse connection to the Web Server in the DMZ when port 5003 inbound is blocked.

HTTP

TCP

61004

Recording control

-

TCP/UDP Ports Used in Cisco WebEx Scheduling Deployment Options

This section lists the incoming and outgoing ports that are used by the various components of the Cisco Unified MeetingPlace Release 8.0 system. The information refers to Cisco WebEx Scheduling deployment options.

Use these tables to make sure that your firewalls do not block access from Cisco Unified MeetingPlace to users or integrated systems, and to make sure that you do not block communication among the Cisco Unified MeetingPlace components and servers.

This is an optional configuration that is not used unless you specifically configure it. The standard SOCKS port is 1080 but is configurable. Other types of proxies (such as HTTP) are not supported by Cisco Unified MeetingPlace for Cisco WebEx connectivity.

-

TCP

5003, 5005

Control connection between the external Web Server and Application Servers (active server and standby server, if one exists) in segmented meeting access configurations

Open bidirectional

If you configured your network for reverse connection, where your Web Servers are configured with a Cisco Unified MeetingPlace hostname instead of an IP address, the Application Server can initiate a reverse connection to the Web Server in the DMZ when port 5003 inbound is blocked.

Cisco WebEx Node for MCS (including Cisco WebEx Cloud)

HTTPS

TCP

443

Tunnel meeting information from the Cisco WebEx Node to the Cisco WebEx cloud

MCS-7835: two connections max with SSLv3

MCS-7845: four connections max with SSLv3

Only outbound firewall to Internet

-

TCP

7676

Control connection with the Application Server

Internal network use

Application Server to Hardware Media Server Connectivity

The Hardware Media Server should be on the same local network segment as the Application Server. Cisco Unified MeetingPlace does not support Hardware Media Server blades that are remotely located.

Application Server to Web Server Connectivity

Confirm that the system meets the following requirements so that the Web Server can communicate with the Application Server:

The Web Server must be able to communicate with the Application Server on TCP port 5003. This can be achieved by opening port 5003 inbound from the Web Server to the Application Server, in which case the normal registration mechanism will operate. Alternately, the Application Server can initiate a reverse (outbound) connection to the Web Server. For the reverse connection to be initiated, you must enter the MeetingPlace Server name as a hostname instead of an IP address during the Web Server installation. You will also have to manually configure this Web Server unit on the Application Server.

Connectivity between the Web Server and the Application Server is of high quality and not subject to interruptions because of traffic congestion. Any time the round-trip latency exceeds 100 ms or there is more than 1 percent packet loss, you should expect a noticeable reduction in service quality.

TCP port 61004 must be open inbound from the Web Server to the Application Server. There is no "reverse" connection mechanism for this port.

Cisco recommends opening UDP port 123 (NTP) bidirectionally between the Web Server and the Application Server. This is used for time synchronization. Alternate time synchronization mechanisms may be used, but any significant clock drift will result in failures.

Cisco WebEx Node for MCS must be installed on either a MCS 7835 or MCS 7845. The 7835 provides two TCP 443 dedicated socket connections to the Cisco Webex cloud outbound via the firewall. The 7845 provides four TCP 443 dedicated socked connections to the Cisco Webex cloud.

Be aware of the following when configuring the Cisco WebEx Node for MCS:

Cisco WebEx Node for MCS does not support any HTTPS/TCP 443 proxy configured in a network.

All Cisco WebEx Node for MCS outbound TCP Port 443 must be able to traverse firewalls directly without HTTPS proxy servers in between.

Cisco Unified MeetingPlace Release 8.0 supports a maximum of three Cisco WebEx Nodes for MCS with a maximum of 1000 sessions load-shared amongst the deployed nodes.

For meetings scheduled to allow external attendees, internal ports are consumed by internal users. Once the nodes are full, client connections overflow to the Cisco WebEx cloud. If all nodes fail, all clients failover to the cloud.

For meetings scheduled for internal attendees only, internal ports are consumed by internal users. External users are not able to access the meeting. Once the Cisco WebEx Nodes for MCS are full, clients are blocked. If a node fails, client connections go to another node. Failover to the cloud is not possible for internal meetings.

Failover Requirements

To configure failover, you need two Application Servers with a high-speed network connection (preferably 100Mpbs or better) between them. Failover configuration requires the following:

When you configure the Application Server for the Express Media Server, both the primary and secondary failover Express Media Servers must have the same licenses and port distribution for scheduled and ad-hoc meetings.

The time must be synchronized between the two Application Servers. This is required to resolve conflicts when the same piece of data is modified simultaneously in both Application Servers.

If the primary and failover Application Servers share a common set of Audio and Video Blades, you must add all the Audio Blades to both Applications Servers. Be sure to use the same passwords and SNMP community names on the two systems or the failover mechanism will not work.

If the primary and failover Application servers are in different data centers (dual data center deployment), then the same VLAN must be extended between both data centers for the replication and failover to be supported.

Note: Directory Service between two Application Servers is not supported in a failover deployment.

Table: Hardware Capacity

The system supports a maximum of two Application Servers: one primary and one standby.

500

1500

2000

Application Server with Express Media Server

The system supports a maximum of two Application Servers: one primary and one standby.

500

Note: The number of supported audio-only calls drops to a maximum of 300 SRUs at a maximum call rate of 3cps when you are using the G.711 codec.

1000

Note: The number of supported audio-only calls drops to a maximum of 600 SRUs at a maximum call rate of 6cps when you are using the G.711 codec.

1500

Cisco WebEx Node for MCS (web conferencing sessions)

The system supports a maximum of three servers with Cisco WebEx Node installed running a total of 1000 sessions.

100

250

500

Application Server Requirements

The Application Server is Cisco Unified MeetingPlace Application Server software that is installed on a Cisco Media Convergence Server (MCS). The Express Media Server (EMS) is co-resident with the Application Server.

Hardware

Cisco MCS 7835 or 7845 or third-party equivalent as described in the following table.

IMPORTANT: The DL380-G6 Server (AX690A, AX693A) is shipped with an internal USB Drive. The drive conflicts with the custom Linux OS and causes an illegal opcode error. The workaround is to remove the USB Drive from the system.

There is a video clip at the following URL that illustrates how to remove the USB drive.

2. Look on the left-side of the server toward the middle for a USB flash drive. It is located near the edge of the secondary (internal) cover next to the connectors for two cables coming from the HDDs.

3. Pull the drive out and close the cover.

The Cisco MCS 7845-I3-RC2 does not support the Web Server for Cisco Unified MeetingPlace Release 8.0.

Cisco MCS 7845-H2/I2-RC1 and MCS 7835-I2-RC1 servers are supported for upgrades only. However, they are not recommended for use with Cisco Unified MeetingPlace Release 8.0 due to their smaller hard drives.

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

Setting the Write Cache on a RAID Controller

For optimal system performance you should check the Default Write setting on your RAID controller. You can set Default Write to three settings: Write Back with BBU, Write Through and Always Write Back.

Set Default Write to Write Back with BBU if you have installed a battery backup unit on your RAID controller. In the event of a system power loss, the battery backup unit preserves the content of the controller cache memory.

In the event that the battery backup unit fails or goes offline to a re-learn cycle, the Write Back with BBU setting automatically fails back to Write Through mode. Without a working battery backup unit, the Write Through setting is safer, but it also brings a performance penalty on the I/O subsystem of the host device.

If you need to remove the battery backup unit for repairs, you should explicitly set Default Write to Write Through mode and enable the cache explicitly (Disk Cache option). This should give you better but not optimal performance. When the faulty battery is replaced, you can safely return the Default Write setting to Write Back with BBU mode.

If the host that houses your RAID controller is connected to an uninterruptible power supply unit, you can set Default Write to Always Write Back mode.

Express Media Server Requirements

The Express Media Server is a set of software modules that reside on the Application Server.

Note: During installation, you will have the option to choose between the Hardware Media Server and Express Media Server for Cisco Unified MeetingPlace scheduled meeting mode. Ad-hoc meetings are only available in Express Media Server mode.

Audio Codecs

Scheduled/Reservationless mode:

G.711 u/a, G.729a/G.722 (reduced capacity)

Ad-hoc mode:

G.711 u/a, G.729a/G.722 (reduced capacity)

Video Codecs

Scheduled/Reservationless mode:

H.263, H.264/AVC

Video-mode setting: per user profile configuration

Levels available: Mobile, Compatibility, High Quality, High Definition at 720p

Ad-hoc mode:

H.263, H.264/AVC

Video-mode setting: system-wide

Levels available: Mobile, Compatibility, High Quality, High Definition at 720p

Note: Customers deploying the Express Media Server are responsible for providing adequate echo cancellation in their voice gateways. For calls within a single continent, we recommend a minimum of 64ms of echo cancellation in all voice gateways that are connected to the PSTN. For calls between North America, Europe, and Japan, we recommend 128ms. Customers unable to provide this protection in voice gateways, or who are taking intercontinental calls across satellite links or from outside North America, Europe, and Japan should consider deploying the hardware media server instead, which has a built-in echo cancellation capability.

Hardware Media Server Requirements

The Cisco Unified Hardware Media Server is comprised of a set of Audio Blades and/or Video Blades. Each Hardware Media Server supports a maximum of four Blades. You can mix and match Hardware Media Servers. For example, if you deployed a Cisco Unified MeetingPlace solution using a Cisco Unified MeetingPlace 3515 Media Server, you could add more video ports to the solution by adding a Cisco Unified MeetingPlace 3545 Media Server chassis plus a Cisco Unified MeetingPlace 3545 Media Server Video Blade.

Hardware

Cisco Unified MeetingPlace 3515 or 3545 Media Server

The 3515 Media Server is delivered with a predetermined number of ports.

The 3545 Media Server can be configured to support a wide range of audio and/or video ports.

Audio Blade

Cisco Unified MeetingPlace Release 8.0 supports a maximum of eight Audio Blades. Each Audio Blade must be configured with at least one Video Blade. In other words, if your system is configured with eight Audio Blades, you must also purchase eight Video Blades so that each Audio Blade has an associated Video Blade.

Note: In practice, some users may be restricted to scheduling Standard Rate video ports while others are able to schedule High Rate video ports. The total maximum system video capacity, therefore, is between 160 and 320 based on the maximum allowable hardware of eight Video Blades.

Media Server Administration Pages

The following browsers are supported for configuring the Media Server Administration pages:

Cisco WebEx Node for MCS Requirements

Cisco Unified MeetingPlace Release 8.0 supports a maximum of three nodes per system with a total maximum of 1000 Cisco WebEx sessions. Cisco WebEx Nodes for MCS are used by internal network connections for Cisco WebEx web meetings only. They do not provide any audio/video mixing.

Hardware

Cisco Media Convergence Server (MCS) 7835 or 7845 or third-party equivalent per node as described in the following table.

Note: We recommend that you dedicate a Cisco MCS or exact equivalent on which to install the Cisco WebEx Node for MCS.

The Cisco MCS 7845-I3-RC2 does not support the Web Server for Cisco Unified MeetingPlace Release 8.0.

Cisco MCS 7845-H2/I2-RC1 and MCS 7835-I2-RC1 servers are supported for upgrades only. However, they are not recommended for use with Cisco Unified MeetingPlace Release 8.0 due to their smaller hard drives.

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

The Cisco MCS 7845-I3-RC1 does not support the Application Server or Cisco WebEx Node for Cisco Unified MeetingPlace Release 8.0.

Cisco MCS 7845-H2/I2-RC1 and MCS 7835-H2/I2-RC1 servers are supported for upgrades only. However, they are not recommended for use with Cisco Unified MeetingPlace Release 8.0 due to their smaller hard drives.

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

MEM-7835-H2-1GB=

MEM-7835-I2-2GB=

Operating System

Cisco MCS OS 2003.1.3 or later for Windows (Recommended versions are 2003.1.4 and 2003.1.5)

DNS Configuration

For segmented DNS, the same hostname must resolve to the internal Web Server on the internal DNS and resolve to the external Web Server on the external DNS.

The internal hostname and IP address is accessible only from the internal network.

The external hostname or IP address is accessible from both the internal network and the Internet.

Port Access

The following ports must be open between the DMZ and the internal network:

TCP ports 5003 and 5005 are open bidirectional between the Web Server and the Cisco Unified MeetingPlace Application Servers (active server and standby server, if one exists).

If you configured your network for reverse connection, where your Web Servers are configured with a Cisco Unified MeetingPlace hostname instead of an IP address, the Application Server can initiate a reverse connection to the Web Server in the DMZ when port 5003 inbound is blocked.

Software Requirements

Language Support

Cisco Unified MeetingPlace supports the following languages for Audio conferencing and Cisco WebEx web conferencing. This includes all voice prompts, WebEx user interfaces, scheduling tools, except System Administration inferfaces. A maximum of four languages per system is supported, where end users choose their default language and guest users are prompted to pick from a list through a voice menu option.

US English (Default)

UK English

French & French Canadian

German

Spanish (Latin America)

Portuguese (Brazil)

Japanese

Russian (audio/video)-English for WebEx

Chinese (Traditional & Simplified)

Directory Service

Cisco Unified MeetingPlace Directory Service enables you to populate and synchronize the Cisco Unified MeetingPlace user database with the contents of the Cisco Unified Communications Manager user database, as well as provide encrypted End User Authentication. The Cisco Unified Communications Manager user database is typically integrated with an LDAP directory. UC Manager End User Authentication also supports secure LDAP (sLDAP) configuration. The following LDAP directories are supported by Cisco Unified Communications Manager to MeetingPlace Directory Service:

Cisco Unified MeetingPlace Directory Service (via UC Manager LDAP integration) may also be optionally configured to work with Webex to provide on premises End User Authentication and automatic profile propegation to Webex for "host" accounts. This must be requested upon provisioning of the Webex Site at installation. The MeetingPlace to Webex LDAP integration is called Directory Service "SSO" Single Sign On which is optional based on customer requirements for LDAP use. No passwords are stored on Webex nor passed to the Webex cloud for authentication.

All "Host" users must be able to resolve to the MeetingPlace Application Server fully qualified domain name (FQDN) which is deployed behind the company firewall, for instance they must be on the corporate network and VPN connection before "hosting" any meetings. If your profiled users cannot access the corporate network, then a non-Directory Service implementation is advised. MeetingPlace profiles can be exported and imported into Webex Site via Administration interface using Excel CSV formated files.

For MeetingPlace 8 Systems deployed with MeetingPlace Scheduling model the End User Authentications may also be done via the MeetingPlace Internal Web Server with the following 5 options (choose 1 method for End User Authentication) or you may still choose the UC Manager LDAP End USer Authentication method.

MeetingPlace Local UserID/Password

LDAP - this supports mutlidomain environments

LDAP, then MeetingPlace - this support single domain environments only

Windows Integrated Authentication (WIA) - all MeetingPlace PRofiled users must use Windows OS and the MeetingPlace Web server must be join the domain.

Reservationless Single Number Access (RSNA) Requirements

Reservationless Single Number Access is used in an Audio only deployment model and is not support with Webex web conferening integration. To use Cisco Unified MeetingPlace with RSNA, you must use Cisco Unified Communications Manager using all SIP Trunking. There are no other system requirements specific to RSNA.

Make sure that user workstations meet the client requirements in this section, or provide these requirements to your users. All client machines must have separate Internet and telephony access for attending voice and web meetings. The recommended minimum bandwidth for web conferencing is a 56K modem connection. A lesser connection can slow down web-conferencing performance.

Operating System and Browser Support

Platform

Operating System

Browser

Microsoft Windows

Windows Vista Business and Ultimate SP1

Windows Vista Business and Ultimate RTM

Microsoft Internet Explorer Release 7.0 and later

Mozilla Firefox 2.0 and later

Windows XP (with SP2 or SP3)

Microsoft Internet Explorer Release 6.0 and later

Mozilla Firefox 2.0 and later

Apple Mac

Mac OS X 10.4.11 and later (Tiger)

Mozilla Firefox Release 2.0 and later

Mac Safari Release 3.0 and later

Mac OS X 10.5.5 and later (Leopard)

Mozilla Firefox Release 2.0 and later

Mac Safari Release 3.0 and later

Mac OS X 10.6 (Snow Leopard)

Mozilla Firefox Release 3.0 and later

Mac Safari Release 3.0 and later

Sun Solaris

Sun Solaris Release 9 or 10

Mozilla Firefox Release 2.0 and later

Linux

Red Hat Enterprise Linux 5 Desktop

SUSE Linux Enterprise Desktop 10

Ubunti Release 8.04 LTS Desktop

Mozilla Firefox Release 2.0 and later

Adobe Flash

Note: Adobe Flash is not required for new installations of Cisco Unified MeetingPlace Release 8.0.

Platform

Operating System

Requirement

Microsoft Windows

Windows Vista Business and Ultimate

Windows XP

Adobe Flash Player Release 9.0 and later

Apple Mac

Mac OS X Release 10.4 and 10.5

Adobe Flash Player Release 9 and later

Mac OS X Release 10.6

Adobe Flash Player Release 10 and later

Sun Solaris

Sun Solaris Release 9

Adobe Flash Player Release 7.0 and later

Sun Solaris Release 10

Adobe Flash Player Release 9.0 and later

Linux

Red Hat Enterprise Linux 5 Desktop

SUSE Linux Enterprise Desktop 10

Ubunti Release 8.04 LTS Desktop

Adobe Flash Player Release 9.0 and later

(Optional) Audio Player

Audio player that plays WAV, WMA, or MP3 files.

Port Access

(Optional, but strongly recommended) TCP port 1627 open from client-to-server on your firewall for direct inbound access. If this port is not open, the meeting console establishes a slightly slower connection by tunneling through port 80.

Cisco WebEx Integration with Cisco Unified MeetingPlace

The Cisco WebEx integration requires the following:

Cisco Unified MeetingPlace Application Server

(Optional) Cisco Unified MeetingPlace Web Server

(Optional) Cisco WebEx Node for MCS

MeetingPlace Application Server Webex TSP only support SOCKS Web Proxy servers (Not HTTP Proxy) so please allow direct firewall access to Webex Site IPs directly. Often there are delay issues when proxy servers are used and the integration to Webex must be able to be maintained continuously via internet without delays, otherwise it will affect user response times.

MeetingPlace Webex Node for MCS does not support any HTTP or SOCKS proxy servers. Please allow direct accesss to Webex Site IPs directly through Firewall settings.

Cisco Webex Node for MCS is currently not supported with the Webex Global Site Backup system. If you want a fully redundant option with GSB, submit a new Webex Node for MCS request to Webex Provisioning to deploy a redundant Node which is ‘homed’ to the GSB data center instead of the primary. You must deploy an MCS server with the Webex Node for MCS software for this function only in your network.

A Cisco WebEx integration supports a maximum of 1000 Webex sessions on either multiple Webex Node for MCS's or connected to Webex Collaboration Cloud per system in multiple meetings.

A single Meeting Center meeting with MeetingPlace Audio supports a maximum of audio and web 125 attendees.

A Cisco Webex Scheduling model also supports Webex Event Center which supports a maximum of 500 MeetingPlace Audio attendees in a single meeting. However, Event Center can also provide "Audio Broadcast function which only the "Speakers" for a large conference would connect to the MEetingPlace Audio system and all attendees would receive the entire Web sharing, video and MP Audio all bridged into a single web HTTPS stream via end user's PC which reduces the need for everyone to dial into the MeetingPlace Audio system for meetings.

Linux OS on client desktops are not suppported on Meeting Center/Event Center/Training Center.

Cisco WebEx Node for MCS

Software

Cisco WebEx MeetingCenter or Cisco WebEx MeetingCenter Pro

Cisco Webex Enterprise Edition that supports Meeting Center, Event Center and Training Center (Support Center is also available but does not require MeetingPlace Audio unless Support personnel escalate to a full Meeting Center meeting with multiple attendees.)

WebEx Business Suite 27 (WBS27 SP14 or later) on the Cisco WebEx site.

Webex Scheduling Option with Mobile Device Integrations

Cisco WebEx supports iPhone, Blackberry mobile devices ability to easily join a Webex meeting with automatic callback to a mobile device. When integrating to MeetingPlace Audio with Webex, the iPhone or Blackberry Webex client must be programmed without any Plus "+" dialing in the phone number field. Please enter the mobile phone number without a "+".

Because the IBM Lotus Sametime Server cannot support multiple Telephony Conferencing Service Provider Interface (TCSPI) server-side integrations, you cannot use both of the following integrations at the same time:

Note: If you also deploy the Cisco Phone Control and Presence with IBM Lotus Sametime integration, then you must use IBM Lotus Sametime Server 8.0.1 and install the following IBM patches to disable the IBM phone icon: 3AAAFEAB, 49D5219C, 643A31, 662A775A, 77D5E39D.

Cisco WebEx Mobile Integration with Cisco Unified MeetingPlace

Currently this integration does not support any level of SSO or LDAP integration capability.

The CallBack feature via mobile devices requires the Webex client on the mobile device be configured with the full dialable mobile phone number without the use of the "+" symbol in the front of the number. Please remove "+" when use a MeetingPlace Audio integrated Webex site.

iPAD is currently not supported with MeetingPlace Audio systems because iPAD is VoIP enabled only via internet.

Upgrading and Migration Requirements

Anytime that you upgrade or migrate to Cisco Unified MeetingPlace Release 8.0, you must get new licenses for your system. For details about licenses, see the Planning Guide for Cisco Unified MeetingPlace Release 8.0.

Make sure that the specific Cisco MCS model supports the number of SIP sessions that are required by your Cisco Unified MeetingPlace system.

Migrating from Cisco Unified MeetingPlace Express

We currently only support migrations from Cisco Unified MeetingPlace Express Release 2.1.1 to Cisco Unified MeetingPlace Release 8.0; therefore, if you are using an earlier version of Cisco Unified MeetingPlace Express, you must first upgrade to Cisco Unified MeetingPlace Express Release 2.1.1.

There are no specific requirements for migrating from Release 7.0 to Release 8.0.

For complete information about migrating to Cisco Unified MeetingPlace Release 8.0, see the Installation and Upgrade Guide for Cisco Unified MeetingPlace Release 8.0.

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: