Cisco Unified MeetingPlace Release 8.0 -- System Requirements for Cisco Unified MeetingPlace Release 8.0

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (Cisco Unified MeetingPlace for IBM Lotus Notes Release 8.0: multiple clusters are not supported for lotus notes)
(Video Blade)
(11 intermediate revisions not shown)
Line 59: Line 59:
US production IP Exceptions:
US production IP Exceptions:
-
64.68.96.0/19 (CIDR) or 64.68.96.0 - 64.68.127.255 (net range)  
+
* 64.68.96.0/19 (CIDR) or 64.68.96.0 - 64.68.127.255 (net range)  
-
66.114.160.0/20 (CIDR) or 66.114.160.0 - 66.114.175.255 (net range)  
+
* 66.114.160.0/20 (CIDR) or 66.114.160.0 - 66.114.175.255 (net range)  
-
66.163.32.0/20 (CIDR) or 66.163.32.0 - 66.163.47.255 (net range)  
+
* 66.163.32.0/20 (CIDR) or 66.163.32.0 - 66.163.47.255 (net range)  
-
209.197.192.0/19 (CIDR) or 209.197.192.0 - 209.197.223.255 (net range)  
+
* 209.197.192.0/19 (CIDR) or 209.197.192.0 - 209.197.223.255 (net range)
 +
* 173.243.0.0/20 (CIDR) or 173.243.0.0 - 173.243.15.255 (net range)
Outside of the US:
Outside of the US:
-
210.4.192.0/20 (CIDR) or 210.4.192.0 - 210.4.207.255 (net range)  
+
* 210.4.192.0/20 (CIDR) or 210.4.192.0 - 210.4.207.255 (net range)  
-
62.109.192.0/20 (CIDR) or 62.109.192.0 - 62.109.207.255 (net range)  
+
* 62.109.192.0/20 (CIDR) or 62.109.192.0 - 62.109.207.255 (net range)  
-
114.29.192.0/19 (CIDR) or 114.29.192.0 - 114.29.223.255 (net range) *India
+
* 114.29.192.0/19 (CIDR) or 114.29.192.0 - 114.29.223.255 (net range) *India
=== TCP/UDP Ports Used in Cisco Unified MeetingPlace Scheduling Deployment Options ===
=== TCP/UDP Ports Used in Cisco Unified MeetingPlace Scheduling Deployment Options ===
Line 1,781: 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.
Line 1,798: 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:'''  For information about different system capacity limits for several key configurations, see [[Cisco Unified MeetingPlace Release 8.0 -- System Capacity Quick Reference Tables|System Capacity Quick Reference Tables]].
Line 1,836: Line 1,838:
500
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
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 2,010: Line 2,018:
'''Notes: '''
'''Notes: '''
-
* IMPORTANT: The DL380-G6 Server (AX690A, AX693A) is shipped with an internal USB Drive. The drive conflicts with our custom Linux OS and causes an illegal opcode error. The workaround is to remove the USB Drive from the system.  
+
* 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.  
*:There is a video clip at the following URL that illustrates how to remove the USB drive.  
*:https://videosharing.cisco.com:8443/vportal/VideoPlayer.jsp?ccsid=C-2fbbdacb-65d5-4101-a070-ada46c84ecb7:1#  
*:https://videosharing.cisco.com:8443/vportal/VideoPlayer.jsp?ccsid=C-2fbbdacb-65d5-4101-a070-ada46c84ecb7:1#  
*:If the URL does not work, visit https://videosharing.cisco.com:8443/  and search for MeetingPlace.
*:If the URL does not work, visit https://videosharing.cisco.com:8443/  and search for MeetingPlace.
-
*:You can also use these steps to describe the process to the customer:
+
*:You can also use these steps to remove the USB Drive:
-
*:1. Remove the top cover of the server
+
*:1. Remove the top cover of the server.
-
*:2. Look on the left side of the server all the way toward the middle, near the edge of the secondary (internal) cover, next to the connectors for two cables coming from the HDDs,you should see a USB flash drive plugged in
+
*: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.
*:3. Pull the drive out and close the cover.
Line 2,307: Line 2,315:
|
|
-
300
+
320
|
|
Line 2,316: Line 2,324:
-
'''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.
-
 
+
===== Media Server Administration Pages =====
===== Media Server Administration Pages =====
Line 3,210: Line 3,217:
* A single Meeting Center meeting with MeetingPlace Audio supports a maximum of audio and web 125 attendees.  
* 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.
* 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.
 +
* Apple MAC OS on client de4sktops are supported on Meeting Center only, not Event or Training Center.
Line 3,259: Line 3,268:
'''Notes: '''
'''Notes: '''
* This integration is only supported when using a Cisco Unified MeetingPlace Scheduling deployment option.
* This integration is only supported when using a Cisco Unified MeetingPlace Scheduling deployment option.
-
* Multiple clusters are not supported for Lotus Notes.
+
* Multiple clusters are not supported for the IBM Lotus Notes for Cisco Unified MeetingPlace integration.
Line 3,835: Line 3,844:
#: See [[Cisco Unified MeetingPlace, Release 6.x -- Upgrading_to_Cisco_Unified_MeetingPlace_Release_6.0|Upgrading to Cisco Unified MeetingPlace Release 6.0]].
#: See [[Cisco Unified MeetingPlace, Release 6.x -- Upgrading_to_Cisco_Unified_MeetingPlace_Release_6.0|Upgrading to Cisco Unified MeetingPlace Release 6.0]].
# Migrate from Release 6.0 Maintenance Release 5 to Cisco Unified MeetingPlace Release 7.0.  
# Migrate from Release 6.0 Maintenance Release 5 to Cisco Unified MeetingPlace Release 7.0.  
-
#: See [[Cisco Unified MeetingPlace Release 7.0 -- Migrating to Cisco Unified MeetingPlace Release 7.0.3 from Release 6.0| How to Migrate to Cisco Unified MeetingPlace Release 7.0.3]]
+
#: See [[Cisco Unified MeetingPlace, Release 7.0 -- Migrating to Cisco Unified MeetingPlace Release 7.0 from Release 6.0|Migrating to Cisco Unified MeetingPlace Release 7.0 from Release 6.0]]
# Upgrade from Release 7.0 to Release 8.0.
# Upgrade from Release 7.0 to Release 8.0.
#: See [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0|Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0]] module.
#: See [[Cisco Unified MeetingPlace Release 8.0 -- Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0#Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0|Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0]] module.

Revision as of 18:49, 22 November 2012

Main page: Cisco Unified MeetingPlace, Release 8.0

Print PDF: Cisco Unified MeetingPlace Release 8.0 -- Print System Requirements


This document lists the system requirements for Cisco Unified MeetingPlace Release 8.0.


Contents

Network Requirements


Standards and Protocols

Cisco Unified MeetingPlace Release 8.0 uses the following standards and protocols:

  • SIP signaling as per RFC-3261
  • SDP protocol RFC-2327
  • Offer answer based on RFC-3264 (an Offer/Answer Model with the Session Description Protocol (SDP))
  • RTP as RFC-3550
  • Session Initiation Protocol (SIP) REFER Method RFC-3515
  • Out of band DTMF digits as per either RFC-2833 or KPML-RFC4730 (indirectly RFC-3265)
  • H.264 Video as per RFC-3984
  • H.263 video as per RFC-2190
  • MIME Type Registration of RTP Payload Formats RFC-3555
  • isFocus flag as per RFC-4579
  • SOCKS protocol for connecting to Cisco WebEx via a proxy configuration


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.

WebEx Port Ranges for Firewalls Used in Cisco Unified MeetingPlace Deployment Options

To ensure traffic to and from the WebEx domain is routed appropriately through your firewall or proxy servers, review the settings below:

Web browser exceptions Add an exception for the entire webex.com domain = *.webex.com. We ask that WebEx sites are not cached (content, IP-path) on proxy servers. Cisco WebEx Production IP Exceptions

US production IP Exceptions:

  • 64.68.96.0/19 (CIDR) or 64.68.96.0 - 64.68.127.255 (net range)
  • 66.114.160.0/20 (CIDR) or 66.114.160.0 - 66.114.175.255 (net range)
  • 66.163.32.0/20 (CIDR) or 66.163.32.0 - 66.163.47.255 (net range)
  • 209.197.192.0/19 (CIDR) or 209.197.192.0 - 209.197.223.255 (net range)
  • 173.243.0.0/20 (CIDR) or 173.243.0.0 - 173.243.15.255 (net range)

Outside of the US:

  • 210.4.192.0/20 (CIDR) or 210.4.192.0 - 210.4.207.255 (net range)
  • 62.109.192.0/20 (CIDR) or 62.109.192.0 - 62.109.207.255 (net range)
  • 114.29.192.0/19 (CIDR) or 114.29.192.0 - 114.29.223.255 (net range) *India

TCP/UDP Ports Used in Cisco Unified MeetingPlace 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 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.


Table: Incoming Ports Used in Cisco Unified MeetingPlace Scheduling Deployment Options
Protocol Port Type Ports Port Usage Special Requirements
Application Server/Express Media Server

SSH

TCP

22

Secure access

Expose to system administrators

HTTP, HTTPS

TCP

80, 443

Administrator web access for Cisco WebEx

Expose to system administrators

NTP

UDP

123

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

Expose to Web Server in the DMZ


Used in segmented meeting access configurations

RTP, RTCP

UDP

16384-32767

Recording media for both Hardware Media Server and Express Media Server

-

Hardware Media Server

FTP

TCP

21

Retrieving log files

Expose to system administrators

Telnet

TCP

23

Telnet

Expose to system administrators

HTTP

TCP

80

Web user interface

Expose to system administrators

NTP

UDP

123

Network Time Protocol

-

SNMP

UDP

161

SNMP configuration

Expose to system administrators

MPI

TCP

2010

MPI (Pompa control protocol)

-

MPI

TCP

2010

MPI (Pompa control protocol)

-

DCI

TCP

3333

DCI (DCS control protocol)

-

XML control

TCP

3336

XML control

-

XML cascading

TCP

3337

XML cascading

-

File server

TCP

3340

File server

-

SIP

TCP UDP

5060

SIP

-

RTP/RTCP

UDP

16384-16683

Audio Blades

Expose to system administrators and end users

RTP/RTCP

UDP

20000-21799

Video Blades

Expose to system administrators and end users

Video Blade control

TCP

2944-2945

Video Blade control (H.248)

-

Web Server

HTTP

TCP

80

User web access


Cisco Unified MeetingPlace for Microsoft Outlook client

Expose to system administrators and end 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.

DCOM

TCP

Dynamically open 1024 to 65535

Cisco Unified MeetingPlace for Microsoft Outlook to Microsoft Exchange uses the CDO API

Required only for Release 7.0.1 systems using the back-end Microsoft Outlook integration.

Control connection

TCP

5003

Control connection between Web Servers and the Application Server

Expose to Application Server

Cisco WebEx Node for MCS (including WebEx Cloud)

HTTP

TCP

80

User web access from Cisco WebEx client

Internal network use only

-

TCP

1270-1279

User web access from Cisco WebEx client

Internal network use only

-

TCP

2000-2009

User web access from Cisco WebEx client

Internal network use only

HTTPS

TCP

443

Meeting entry from the Cisco WebEx client


Checking time from the NTP server

The Cisco WebEx Site will redirect to the Cisco WebEx Node if configured.

IBM Lotus Sametime

TCP/UDP

TCP UDP

8083

Java RMI lookup service for IBM Lotus Sametime (1)

-

TCP

TCP

8086

RMI calls (JRMP) for IBM Lotus Sametime web conferencing (2)

-



(1) RMI = Remote Method Invocation


(2) RMP = Java Remote Method Protocol


Note: Table: Outgoing Ports Used in Cisco Unified MeetingPlace Scheduling Deployment Options contains a partial list of outgoing ports.


Table: Outgoing Ports Used in Cisco Unified MeetingPlace Scheduling Deployment Options
Protocol Port Type Port Usage Special Requirements
Application Server

SMTP

TCP

25

Send information to the SMTP or Microsoft Exchange Server for email notification

-

HTTP

TCP

80

Send information to the Microsoft Exchange Server for Microsoft Exchange integration

-

SOCKS

TCP

1080

Optional configuration for connecting to Cisco WebEx via a proxy configuration

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.

HTTPS

TCP

443

Send information to the Microsoft Exchange Server when SSL is enabled


Two permanent Telephony Service Provider (TSP) TLS Socket connections to send information to the Cisco WebEx cloud

-

-

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

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.


Table: Incoming Ports Used in Cisco WebEx Scheduling Deployment Options
Protocol Port Type Ports Port Usage Special Requirements
Application Server

SSH

TCP

22

Secure access

Expose to system administrators

HTTP, HTTPS

TCP

80, 443

Administrator web access for Cisco WebEx

Expose to system administrators

NTP

UDP

123

Network Time Protocol communication from the Hardware Media Server

-

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

-

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

RTP, RTCP

UDP

16384-32767

Recording media for both Hardware Media Server and Express Media Server

-

Hardware Media Server

FTP

TCP

21

Retrieving log files

Expose to system administrators

Telnet

TCP

23

Telnet

Expose to system administrators

HTTP

TCP

80

Web user interface

Expose to system administrators

NTP

UDP

123

Network Time Protocol

-

SNMP

UDP

161

SNMP configuration

Expose to system administrators

MPI

TCP

2010

MPI (Pompa control protocol)

-

DCI

TCP

3333

DCI (DCS control protocol)

-

XML control

TCP

3336

XML control

-

XML cascading

TCP

3337

XML cascading

-

File server

TCP

3340

File server

-

SIP

TCP UDP

5060

SIP

-

RTP/RTCP

UDP

16384-16683

Audio Blades

Expose to system administrators and end users

RTP/RTCP

UDP

20000-21799

Video Blades

Expose to system administrators and end users

Video Blade control

TCP

2944-2945

Video Blade control (H.248)

-

Cisco WebEx Node for MCS (including WebEx Cloud)

HTTP

TCP

80

User web access from Cisco WebEx client

Internal network use only

-

TCP

1270-1279

User web access from Cisco WebEx client

Internal network use only

-

TCP

2000-2009

User web access from Cisco WebEx client

Internal network use only

HTTPS

TCP

443

Meeting entry from the Cisco WebEx client.


Checking time from the NTP server.

The Cisco WebEx Site will redirect to the Cisco WebEx Node if configured.



Note: Table: Outgoing Ports Used in Cisco WebEx Scheduling Deployment Options contains a partial list of outgoing ports.


Table: Outgoing Ports Used in Cisco WebEx Scheduling Deployment Options
Protocol Port Type Port Usage Special Requirements
Application Server/ Express Media Server

SMTP

TCP

25

Send information to the SMTP or Microsoft Exchange Server for email notification

-

HTTP

TCP

80

Send information to the Microsoft Exchange Server for Microsoft Exchange integration

-

HTTPS

TCP

443

Send information to the Microsoft Exchange Server when SSL is enabled


Two permanent Telephony Service Provider (TSP) TLS Socket connections to send information to the Cisco WebEx cloud

-

SOCKS

TCP

1080

Optional configuration for connecting to Cisco WebEx via a proxy configuration

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

Note: Cisco Unified MeetingPlace Web Servers are only required in Cisco Unified MeetingPlace Scheduling deployments.


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 Connectivity

Note: Cisco Webex Node for MCS is an optional component. Cisco Unified MeetingPlace Release 8.0 also supports Webex Software as a Server (SaaS).


Cisco WebEx Node for MCS is deployed internally behind your corporate firewall. There are two separate connections:

  • Cisco WebEx Node for MCS to the Cisco WebEx Cloud
  • Cisco WebEx Node for MCS to the Cisco Unified MeetingPlace Application Server


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.

Hardware Requirements


Hardware Capacity

NOTE: For information about different system capacity limits for several key configurations, see System Capacity Quick Reference Tables.


Table: Hardware Capacity
Server Type Cisco MCS 7835-I2/I3/H2 with 4GIG RAM Cisco MCS 7845-I2/H2 Cisco MCS 7845-I3 (DL380-G6)

Application Server with Hardware Media Server


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.


Table: Supported Cisco MCS and Third-Party Equivalent Servers for the Application Server
Cisco MCS Version Description IBM Part Number HP Equivalent

Cisco MCS 7845-I3-RC2

Dual Intel E5540 2.53 GHz; 4x300 HDD, 8 GB RAM


HP equivalent: 2 Quad-Core Intel 2.53 GHz E5540 Processor, 8GB RAM, 4x 300GB HDD

7947-62Y (worldwide reseller), 7947-AC1 (IBM direct US/CAN/LA), 7947-CTO (IBM direct EMEA/AP)

DL380-G6 Server, part number: AX693A

Cisco MCS 7835-I3-RC1

Single Intel 5504 Quad-core 2.00 GHz; 2x146 HDD, 4 GB RAM


HP equivalent: 1 Quad-Core Intel 2.00 GHz Intel Nehalem E5504 Processor, 4GB RAM, 2x 146GB Hard Drives

7947-22Y (worldwide reseller), 7947-AC1 (IBM direct US/CAN/LA), 7947-CTO (IBM direct EMEA/AP)

DL380-G6 Server, part number: AX690A

Cisco MCS 7845-I2-RC2 (end-of-sale 12/09)

IBM x3650 2x Xeon 5140 2.33GHz Dual-Core Processor, 4G RAM, 4x 146GB HDD

7979-AC1 (IBM direct US/CAN/LA), 7979-CTO (IBM direct EMEA/AP)

-

Cisco MCS 7835-I2-RC2 (end-of-sale 12/09)

IBM x3650, Single Xeon 5140 2.33GHz Dual-Core Processor, 2G RAM, 2x 146GB HDD, Requires +2GIG RAM

7979-AC1 (IBM direct US/CAN/LA), 7979-CTO (IBM direct EMEA/AP)

-

Cisco MCS 7845-H2-RC2 (end-of-sale 7/09)

HP equivalent: Dual Intel 5140 2.33GHz; 4x146GB HDD

-

DL380-G5 Server, part number: 470064-887

Cisco MCS 7835-H2-RC2 (end-of-sale 7/09)

HP equivalent: Single Xeon 5140 2.33GHz Processor, 2G RAM, 2x 146GB HDD

-

DL380-G5 Server, part number: 470064-880

Cisco MCS 7845-H2-RC1 (end-of-sale 7/09)

Dual Intel 5140 2.33GHz; 4X72GB HDD

Supported for upgrades only

Supported for upgrades only

Cisco MCS 7845-I2-RC1 (end-of-sale 7/09)

Dual Intel 5140 2.33GHz; 4GB

Supported for upgrades only

Supported for upgrades only

Cisco MCS 7835-I2-RC1 (end-of-sale 7/09)

HP equivalent: Single Xeon 5140 2.33GHz Processor, 2G RAM, 2x 72GB HDD

Supported for upgrades only

Supported for upgrades only



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.
    https://videosharing.cisco.com:8443/vportal/VideoPlayer.jsp?ccsid=C-2fbbdacb-65d5-4101-a070-ada46c84ecb7:1#
    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.
  • 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:
    • MEM-7835-H2-1GB=
    • MEM-7835-I2-2GB=


For additional information about supported third-party servers, go to: http://www.cisco.com/go/swonly.

Operating System

Cisco MCS OS for Linux (installed with the Application Server software)


Cisco Unified Communications Manager

Cisco Unified Communications Manager Release 6.1(2), 7.0, 7.1, or 8.0 release.


For audio-only installations, you may connect Cisco Unified MeetingPlace to Cisco Unified Communications Manager Release 6.0(3) or later release:


Note: Cisco Unified Communications Manager Release 6.1(2) is automatically included with all shipments of Cisco Unified MeetingPlace Release 8.0.

Note: Cisco Unified Communications Manager Release 8.5 has a known issue with Cisco Unified MeetingPlace Release 8.0 Ad hoc conferencing. A fix will be available in Cisco Unified Communications Manager Release 8.6.


Software
  • Cisco Unified MeetingPlace Application Server Release 8.0
  • Cisco Security Agent Release 6.0.1.112


Related Information


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.


Maximum system audio capacity is dependent on the global audio mode of your Cisco Unified MeetingPlace system.


Number of Audio Blades Number of Supported Audio Ports in "High Capacity" Mode (250 Ports/Blade) Number of Supported Audio Ports in "High Quality" Mode (166 Ports/Blade)

1

250

166

2

500

332

3

750

498

4

1000

664

5

1250

830

6

1500

996

7

1750

1162

8

2000

1328



In other words, if the global audio mode is set to G.711, G.729 without LEC, the system supports 250 ports per Blade for a maximum of 2000 "high capacity" audio ports.


If the global audio mode is set to G.711, G.722, G.729, iLBC, the system supports 166 ports per Blade for a maximum of 1328 "high quality" audio ports.


Note: Configuration of G.729 with or without LEC occurs on the Call Configuration > Media Parameters page of the Cisco Unified MeetingPlace Administration Center.


Video Blade

Cisco Unified MeetingPlace Release 8.0 supports a maximum of eight Video Blades. Maximum system video capacity is dependent on whether hardware video resources are scheduled as High Rate video ports or Standard Rate video ports. High Rate/Standard Rate is configured in the user profile.


Number of Video Blades Number of Supported Standard Rate Video Ports Number of Supported High Rate Video Ports

1

40

20

2

80

40

3

120

60

4

160

80

5

200

100

6

240

120

7

280

140

8

320

160



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:

  • Microsoft Windows
    • Internet Explorer 6, 7, or 8 (recommended)
    • Mozilla Firefox 3.5.7
  • Apple Mac
    • Internet Explorer 6, 7, or 8 (recommended)
    • Mozilla Firefox 3.5.7


Related Information

For information about physically installing and configuring the Hardware Media Server, see the Installation and Upgrade Guide for Cisco Unified MeetingPlace Release 8.0 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html


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.


Table: Supported Cisco MCS and Third-Party Equivalent Servers for Cisco WebEx Node for MCS
Cisco MCS Version Description IBM Part Number HP Equivalent

Cisco MCS 7845-I3-RC2

Dual Intel E5540 2.53 GHz; 4x300 HDD, 8 GB RAM


HP equivalent: HP equivalent: 2 Quad-Core Intel 2.53 GHz E5540 Processor, 8GB RAM, 4x 300GB HDD

7947-62Y (worldwide reseller), 7947-AC1 (IBM direct US/CAN/LA), 7947-CTO (IBM direct EMEA/AP)

DL380-G6 Server, part number: AX693A

Cisco MCS 7835-I3-RC1

Single Intel 5504 Quad-core 2.00 GHz; 2x146 HDD, 4 GB RAM


HP equivalent: 1 Quad-Core Intel 2.00 GHz Intel Nehalem E5504 Processor, 4GB RAM, 2x 146GB Hard Drives

7947-22Y (worldwide reseller), 7947-AC1 (IBM direct US/CAN/LA), 7947-CTO (IBM direct EMEA/AP)

DL380-G6 Server, part number: AX690A

Cisco MCS 7845-I2-RC2 (end-of-sale 12/09)

IBM x3650 2x Xeon 5140 2.33GHz Dual-Core Processor, 4G RAM,4x 146GB HDD

Note: Supports a maximum of 250 sessions per server.

7979-AC1 (IBM direct US/CAN/LA), 7979-CTO (IBM direct EMEA/AP)

-

Cisco MCS 7835-I2-RC2 (end-of-sale 12/09)

IBM x3650, Single Xeon 5140 2.33GHz Dual-Core Processor, 2G RAM, 2x 146GB HDD, Requires +2GIG RAM

Note: Supports a maximum of 100 sessions per server.

7979-AC1 (IBM direct US/CAN/LA), 7979-CTO (IBM direct EMEA/AP)

-

Cisco MCS 7845-H2-RC2 (end-of-sale 7/09)

HP equivalent: Dual Intel 5140 2.33GHz; 4x146GB HDD

Note: Supports a maximum of 250 sessions per server.

-

DL380-G5 Server, part number: 470064-887

Cisco MCS 7835-H2-RC2 (end-of-sale 7/09)

HP equivalent: Single Xeon 5140 2.33GHz Processor, 2G RAM, 2x 146GB HDD

Note: Supports a maximum of 100 sessions per server.

-

DL380-G5 Server, part number: 470064-880

Cisco MCS 7845-H2-RC1 (end-of-sale 7/09)

Dual Intel 5140 2.33GHz; 4X72GB HDD

Supported for upgrades only

Supported for upgrades only

Cisco MCS 7845-I2-RC1 (end-of-sale 7/09)

Dual Intel 5140 2.33GHz; 4GB

Supported for upgrades only

Supported for upgrades only

Cisco MCS 7835-I2-RC1 (end-of-sale 7/09)

HP equivalent: Single Xeon 5140 2.33GHz Processor, 2G RAM, 2x 72GB HDD

Supported for upgrades only

Supported for upgrades only



Notes:

  • 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:
    • MEM-7835-H2-1GB=
    • MEM-7835-I2-2GB=


Operating System

Cisco MCS OS for Linux (installed with the Cisco WebEx Node for MCS software)


Software

Cisco WebEx Node for MCS software Release 8.0


Web Server Requirements

A Web Server is Cisco Unified MeetingPlace Web Server software that is installed on a Cisco Media Convergence Server (MCS).


Note: A Cisco Unified MeetingPlace Web Server is only required when using a Cisco Unified MeetingPlace Scheduling deployment option. Cisco WebEx Scheduling deployment options do not require a Web Server. For more information about deployment options, see the Planning Guide for Cisco Unified MeetingPlace Release 8.0 in the following location: http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment


Hardware

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


Table: Supported Cisco MCS and Third-Party Equivalent Servers for the Web Server
Cisco MCS Version Description IBM Part Number HP Equivalent


Cisco MCS 7835-I3-RC1 (recommended)

Single Intel 5504 Quad-core 2.00 GHz; 2x146 HDD, 4 GB RAM


HP equivalent: 1 Quad-Core Intel 2.00 GHz Intel Nehalem E5504 Processor, 4GB RAM, 2x 146GB Hard Drives

7947-22Y (worldwide reseller), 7947-AC1 (IBM direct US/CAN/LA), 7947-CTO (IBM direct EMEA/AP)

DL380-G6 Server, part number: AX690A


Cisco MCS 7845-I3-RC1

Single Intel 5540 Quad-core 2.53 GHz, 4x146HDD, 6GB RAM


HP equivalent: 2 Quad-Core Intel 2.53 Ghz Intel Nehalem E5540 Processor, 8GB RAM, 4x 300GB HDD

7947-62Y (worldwide reseller), 7947-AC1 (IBM direct US/CAN/LA), 7947-CTO (IBM direct EMEA/AP)

-

Cisco MCS 7845-H2-RC2 (end-of-sale 7/09)

2x Xeon 5140 2.33GHz Processor, 4G RAM,4x146GB HDD


HP equivalent: Dual Intel 5140 2.33GHz; 4x146GB HDD

7979-AC1 (IBM direct US/CAN/LA), 7979-CTO (IBM direct EMEA/AP)

DL380-G5 Server, part number: 470064-887

Cisco MCS 7835-H2-RC2 (end-of-sale 7/09)

Single Xeon 5140 2.33GHz Processor, 2G RAM, 2x146GB HDD. Requires +2GIG RAM added (4 total)


HP equivalent: Single Xeon 5140 2.33GHz Processor 2G RAM, 2x 146GB Hard Drives

7979-AC1 (IBM direct US/CAN/LA), 7979-CTO (IBM direct EMEA/AP)

DL380-G5 Server, part number: 470064-880

Cisco MCS 7845-I2-RC2 (end-of-sale 12/09)

IBM x3650 2x Xeon 5140 2.33GHz Dual-Core Processor, 4G RAM, 4x146GB HDD

7979-AC1 (IBM direct US/CAN/LA), 7979-CTO (IBM direct EMEA/AP)

-

Cisco MCS 7835-I2-RC2 (end-of-sale 12/09)

IBM x3650, Single Xeon 5140 2.33GHz Dual-Core Processor, 2G RAM, 2x146GB HDD, Requires +2GIG RAM (4 total)

7979-AC1 (IBM direct US/CAN/LA), 7979-CTO (IBM direct EMEA/AP)

-

Cisco MCS 7845-H2-RC1 (end-of-sale 7/09)

Dual Intel 5140 2.33GHz; 4X72GB HDD

Supported for upgrades only

Supported for upgrades only

Cisco MCS 7835-H2-RC1 (end-of-sale 7/09)

Single Intel 5140 2.33Ghz

Supported for upgrades only

Supported for upgrades only

Cisco MCS 7845-I2-RC1 (end-of-sale 7/09)

Dual Intel 5140 2.33GHz; 4GB

Supported for upgrades only

Supported for upgrades only

Cisco MCS 7835-I2-RC1 (end-of-sale 7/09)

HP equivalent: Single Xeon 5140 2.33GHz Processor, 2G RAM, 2x 72GB HDD

Supported for upgrades only

Supported for upgrades only



Notes:

  • 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)


Note: OS DVD is shipped with the Web Server software


Software
  • Cisco Unified MeetingPlace Web Server Release 8.0
  • (Optional) Cisco Security Agent Release 6.0.1.117
  • (Customer provided option) McAfee VirusScan Enterprise 8.0 or 8.5


SQL Server

Microsoft SQL Server 2000 (Service Pack 4)


Note: If you choose the remote SQL Server option during installation of the Web Server software, you can use SQL Server 2005 (Service Pack 2) instead of SQL Server 2000 (Service Pack 4). To use SQL Server 2005, first install the SQL Server 2005 backward compatibility software (the Distributed Management Objects [DMO] component only) on the Web Server.


You must also install and configure your SQL Server to be case insensitive. If you configure your SQL Server to be case-sensitive, the Web Server will not function properly.


Networking Requirements
  • If you are upgrading to Cisco Unified MeetingPlace Release 8.0 from Release 7.0 and want to preserve recordings, you must configure the Web Server with two static IP addresses on the same subnet.
Two static IP addresses are not required for new installations of Cisco Unified MeetingPlace Release 8.0.
  • Cisco Unified MeetingPlace Web Servers must be connected to network switch ports that are configured for 100/1000 Mb full duplex.


Additional Requirements
  • Make sure that all corporate fonts and standard Microsoft fonts, including Microsoft PowerPoint fonts, are installed.
  • NT File System (NTFS) with more than 2.5-GB free space available.
  • Additional disk space for recording.
See the "Recording Size" section in the Configuration Guide for Cisco Unified MeetingPlace Release 8.0 or the online Help in the administrator interface for more information about recording.
  • Make sure that you set the network port configuration on your Web Server to "Enable NetBIOS over TCP/IP" and not "Default."
  • Web Server software does not support "thin clients" (Citrix or Terminal Server).


Related Information


Segmented Meeting Access (SMA) Requirements

Cisco Unified MeetingPlace supports Segmented Meeting Access (SMA) deployments for external access.


Hardware

Two single Cisco Unified MeetingPlace Web Servers:

  • One Web Server deployed inside the private corporate network functioning as internal Web Servers.
  • One Web Server deployed in a network segment, such as a DMZ, functioning as external Web Servers.


Software
  • On internal Web Server: Cisco Unified MeetingPlace Web Server software Release 8.0 installed with the "Internal (Full Access)" server location option.
  • On external Web Server: Cisco Unified MeetingPlace Web Server software Release 8.0 installed with the "External (Limited Access)" server location option.


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.


The following ports are open inbound from the Internet to the DMZ:

  • TCP Port 80
  • TCP Port 1627 (strongly recommended for higher performance of the meeting room)
  • TCP Port 443 (if SSL is implemented)


Synchronized Globally Unique Identifiers (GUIDs)

The database of the internal Web Server and the database of the external Web Server must contain identical GUIDs.


Related Information

Cisco Unified MeetingPlace Phone View Requirements

Cisco Unified MeetingPlace Phone View is available only to Cisco Unified IP Phones that are registered to Cisco Unified Communications Manager.


Note: Cisco Unified MeetingPlace Phone View is not supported with the following:

  • Cisco Unified CallManager Express
  • Cisco Unified Communications Manager Express
  • Cisco Unified MeetingPlace Web Servers with SSL enabled
  • Cisco Unified MeetingPlace Application Servers with SSL enabled


The following Cisco Unified IP Phones are supported in Cisco Unified MeetingPlace Release 8.0:


Table: Cisco Unified MeetingPlace Phone View Requirements
Cisco Unified IP Phone Model Requirements

7940 G and G-GE series (SCCP only)

Minimum firmware version 6.0(4.3), also called App Load ID P00306000403 (1)

7941, 7942, and 7945

-

7960 G and G-GE series (SCCP only)

Minimum firmware version 6.0(4.3), also called App Load ID P00306000403 (1)

7961, 7962 and 7965

-

7970 G series

-

7971, 7975

-

8961

-

9971 and 9951

-

Cisco IP Communicator Release 1.1(5) or later

-



(1) For information about upgrading the firmware, see the Cisco Unified Communications Manager documentation


Determining the Cisco Unified IP Phone Model

Procedure
  1. Press the Settings button. (If this button is not labeled, then press the button just below and to the right of the round ? or i button.)
  2. Select Model Information.


Determining the Firmware Version on a Cisco Unified IP Phone

Procedure
  1. Press the Settings button. (If this button is not labeled, then press the button just below and to the right of the round ? or i button.)
  2. Select Status.
  3. Select Firmware Versions.
  4. Read one or both of the following fields:
  • App Load ID
  • Version


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:

  • Microsoft Windows Active Directory 2000
  • Microsoft Windows Active Directory 2003
  • Microsoft Windows Active Directory 2007
  • Microsoft Windows Active Directory 2008
  • ADAM 2003/2008 (ADLDS) with CUCM 7.1.3
  • iPlanet Directory Server Version 4.x
  • SunONE Directory Server Version 5.1
  • Sun Java Directory Server Version 5.2
  • Sun Java Directory Server Version 6.0
  • OpenLDAP 2.3.39/2.4 with CUCM 7.1.3
  • Novell eDirectory Release 4.x, 5.x, 6.x


Note: Novell eDirectory requires a custom configuration. See http://www.novell.com/coolsolutions/appnote/16752.html for information about Novell eDirectory Release 4.x and http://www.novell.com/communities/node/3028/ for information about Novell eDirectory Release 5.x and 6.x.

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.

To enable secure End user authentication via MP/Webex SSO integration, you must install an SSL certificated on the MeetingPlace Application Server for secure UserID and password authentication to LDAP (via UC Manager AXL interfaces).

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.
  • Third Party Authentication Servers - supports Siteminder and others
  • Web HTTP

License Requirements

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.

End-User Requirements for Web Conferencing

Note: This section refers to end-user requirements for Cisco Unified MeetingPlace Scheduling deployment options. For Cisco WebEx Scheduling deployments, see the end-user requirements on the Cisco WebEx Site: http://support.webex.com/support/system-requirements.html?_nfpb=true&_pageLabel=SystemRequirementsHome.


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.


Integration Requirements

Note: The IBM Lotus Notes, IBM Lotus Sametime, Jabber, and Microsoft Outlook integrations are only supported when using a Cisco Unified MeetingPlace Scheduling deployment option. Cisco WebEx Scheduling deployment options use WebEx Productivity Tools.


For more information about deployment options, see the Planning Guide for Cisco Unified MeetingPlace Release 8.0 in the following location: http://docwiki.cisco.com/wiki/Cisco_Unified_MeetingPlace%2C_Release_8.0_--_Planning_Your_Deployment


For information about WebEx Productivity Tools, see https://welcome.webex.com/docs/T26L/pt/mc0800l/en_US/support/releasenotes_productivitytools.htm.


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.
  • Webex Client interface supports any HTTP or SOCKS proxy server based on browser 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.
  • Apple MAC OS on client de4sktops are supported on Meeting Center only, not Event or Training Center.


Cisco Unified MeetingPlace Application Server

See the Application Server Requirements.


Cisco Unified MeetingPlace Web Server

Note: This is an optional component. A Web Server is only required if your deployment requires users to schedule from Cisco Unified MeetingPlace rather than from Cisco WebEx.


If your deployment requires a Web Server, the Cisco WebEx integration requires the following:

  • At least one internal Cisco Unified MeetingPlace Web Server.
  • (Optional) One external Web Server.


See the Web Server Requirements for hardware and software requirements.


Cisco WebEx Node for MCS

This is an optional component. If your deployment requires a Cisco WebEx Node for MCS, see the Cisco WebEx Node for MCS Requirements.


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 "+".



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

Cisco Unified MeetingPlace for IBM Lotus Notes Release 8.0

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.


The IBM Lotus Notes with Cisco Unified MeetingPlace integration requires the following servers:

  • Cisco Unified MeetingPlace Application Server
  • Cisco Unified MeetingPlace Web Server (which also hosts the integration)
  • IBM Lotus Domino Server


Cisco Unified MeetingPlace Application Server

See the Application Server Requirements.


Cisco Unified MeetingPlace Web Server

Note: The IBM Lotus Notes for Cisco Unified MeetingPlace integration is installed on the Web Server.


Component Requirement

Hardware

See the Web Server Requirements.

License

The Cisco Unified MeetingPlace lotusnotes license.

Software

IBM Lotus Notes client Release 6.0.x, 6.5.x, 7.0.x, 8.0.x, 8.5


Microsoft Internet Information Server (IIS) Release 6.0.

Note: Microsoft IIS Release 6.0 is installed and configured on the Cisco MCS when the operating system is installed.

IBM Lotus Domino Server
Component Requirement

Hardware

Microsoft Windows computer

Operating system

Windows

Software

IBM Lotus Domino Release 6.0.x, 6.5.x, 7.0.x, 8.0.x, 8.5

End-User System
Component Requirement

Hardware

Microsoft Windows computer

Software

Templates 6.0.5, 6.5.4, 6.5.5, 6.5.6, 7.0.2, 7.0.3, 8.0, 8.5


Users of IBM Lotus Domino Server Release 6 require:

  • IBM Lotus Notes Release 6.0.5
  • Template of the same release as the client


Users of IBM Lotus Domino Server Release 6.5 require:

  • IBM Lotus Notes Release 6.5.6 or earlier
  • Template of the same release as the client


Users of IBM Lotus Domino Server Release 7 require:

  • IBM Lotus Notes Release 7.0.3 or earlier
  • Template of the same release as the client


Users of IBM Lotus Domino Server Release 8 require:

  • IBM Lotus Notes Release 8.0 or earlier
  • Template of the same release as the client

Operating system

One of the following:

  • Windows ME
  • Windows Vista
  • Windows 2000 Professional
  • Windows 2000 Server Edition (SP2 or later)
  • Windows 2000 Advanced Server Edition (SP2 or later)
  • Windows XP

Cisco Unified MeetingPlace Click-to-Conference with IBM Lotus Sametime Instant Messaging Release 8.0

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


The IBM Lotus Sametime Web integration requires the following servers:

  • Cisco Unified MeetingPlace Application Server
  • Cisco Unified MeetingPlace Hardware Media Server or Express Media Server
  • Cisco Unified MeetingPlace Web Server
  • IBM Lotus Sametime Server


Cisco Unified MeetingPlace Application Server

See the Application Server Requirements.


Cisco Unified MeetingPlace Hardware Media Server

This is an optional component. If your deployment requires a Hardware Media Server, see the Hardware Media Server Requirements.


Cisco Unified MeetingPlace Web Server

See the Web Server Requirements.


IBM Lotus Sametime Server

The IBM Lotus Sametime Server requires the following software:

  • IBM Lotus Sametime Release 7.5.1 or later
  • IBM Lotus Notes Release 8.0.1 or later


Note:

  • IBM Lotus Notes Release 8.0.1 embeds Sametime Release 8.0, IBM Lotus Notes 8.0.2 and 8.5 embed Sametime Release 8.0.1, and IBM Lotus Notes 8.5.1 embeds Sametime Release 8.0.2.
  • IBM Lotus Sametime Release 8.5 is not supported.
End-User System
Component Requirement

Hardware

Microsoft Windows computer

Software and supported browsers

IBM Lotus Sametime Connect Client Release 7.5.1 or later

  • Mozilla Release 1.7.12 on Windows XP
  • Firefox Release 1.5 on Windows XP
  • Firefox Release 2.0
  • Internet Explorer Release 6.0 or 7.0 on Windows XP Professional, Windows XP Professional 64-bit

Operating system

Microsoft Windows

  • Windows XP Professional SP2
  • Windows XP Professional 64-bit only for web conferencing
  • Windows 2000
  • Microsoft Vista



Cisco Unified MeetingPlace for IBM Lotus Sametime Web Release 8.0

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


The IBM Lotus Sametime Web integration requires the following servers:

  • Cisco Unified MeetingPlace Application Server
  • Cisco Unified MeetingPlace Hardware Media Server or Express Media Server
  • IBM Lotus Sametime Standard Server


Notes:

  • 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:
    • Cisco Unified MeetingPlace for IBM Lotus Sametime Web
    (IBM Lotus Sametime server-side TCSPI integration with Cisco Unified MeetingPlace)
    • Cisco Click to Call and Conference with IBM Lotus Sametime
    (IBM Lotus Sametime server-side TCSPI integration with Cisco Unified Communications Manager)
These two server-side integrations are mutually exclusive and cannot both be deployed at the same time.
  • You can, however, deploy Cisco Unified MeetingPlace for IBM Lotus Sametime Web with either or both of the following client-side integrations:
    • Cisco Unified Messaging with IBM Lotus Sametime
    • Cisco Phone Control and Presence with IBM Lotus Sametime


Cisco Unified MeetingPlace Application Server

See the Application Server Requirements.


Cisco Unified MeetingPlace Hardware Media Server

This is an optional component. If your deployment requires a Hardware Media Server, see the Hardware Media Server Requirements.


IBM Lotus Sametime Server
Component Requirement

Hardware

Microsoft Windows computer

Operating system

  • Windows 2000 Server
  • Windows Server 2003 Standard
  • Windows Server 2003 Enterprise Edition SP2

Software


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.

End-User System

IBM Lotus Sametime Connect Client Release 7.5.1 CF1


IBM Lotus Sametime Connect Client Release 8.0

Jabber with Cisco Unified MeetingPlace Release 8.0

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


The Jabber with Cisco Unified MeetingPlace integration requires the following servers:

  • Cisco Unified MeetingPlace Application Server
  • Cisco Unified MeetingPlace Web Server
  • Jabber XCP server


Cisco Unified MeetingPlace Application Server

See the Application Server Requirements.


Cisco Unified MeetingPlace Web Server
Component Requirement

Hardware

See the Web Server Requirements for hardware specifications.

Software

Jabber XCP server Release 5.1


Sun Java Runtime Environment (JRE) Release 1.4.2.xx

License

Cisco Unified MeetingPlace jabber license

Other

Microsoft Internet Information Server (IIS) Release 6.0

Note: Microsoft IIS Release 6.0 is installed and configured on the Cisco MCS when the operating system is installed.



Jabber XCP Server
Component Requirement

Hardware

See the Web Server Requirements for hardware specifications.

Operating system

Microsoft Windows

Software

Jabber XCP server Release 5.1


Sun Java Runtime Environment (JRE) Release 1.4.2.xx



End-User System
Component Requirement

Hardware

Microsoft Windows computer

Software

Jabber Messenger Release 3.2, Windows version

Operating system

Microsoft Windows

Other

End users who initiate Cisco Unified MeetingPlace meetings from Jabber Messenger must be profiled users in Cisco Unified MeetingPlace.



Cisco Unified MeetingPlace for Microsoft Outlook Release 8.0

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


There are two options for Microsoft Outlook integrations:

  • Front-end integration-Enables users to schedule, reschedule, and cancel meetings from the Microsoft Outlook calendar. For information, see the Enabling Cisco Unified MeetingPlace Scheduling from Microsoft Outlook module in the Configuration Guide for Cisco Unified MeetingPlace.
  • Back-end integration-Enables Cisco Unified MeetingPlace to send Microsoft Outlook calendar notifications for meetings that are scheduled from the Cisco Unified MeetingPlace end-user web interface. For more information, see the Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the Cisco Unified MeetingPlace End-User Web Interface module in the Configuration Guide for Cisco Unified MeetingPlace.


Cisco Unified MeetingPlace Application Server

See the Application Server Requirements.


Microsoft Exchange Server
Component Requirement

Hardware

See the Web Server Requirements for hardware specifications.

Software

Microsoft Exchange Server 2003 SP2

  • Enable WebDAV access from Cisco Unified MeetingPlace.


Microsoft Exchange Server 2007 SP1

  • Enable EWS access from Cisco Unified MeetingPlace and use the Client Access server role.



End-User System
Component Requirement

Hardware

Microsoft Windows computer

Software

Microsoft Outlook XP, 2003, or 2007 Release 12.0.6023.x and later.


An HTTP or HTTPS connection to Cisco Unified MeetingPlace for Microsoft Outlook.

Operating system

One of the following:

  • Microsoft Windows ME
  • Windows Vista
  • Windows 2000 Professional
  • Windows 2000 SE with SP2
  • Windows 2000 AS with SP2
  • Windows XP
  • Windows Server 2003


Cisco WebEx Mobile Integration with Cisco Unified MeetingPlace

  • Cisco Webex offers integrations with iPhone and Blackberry mobile devices.
  • 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.


Upgrading from Release 7.0

You can upgrade to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0.1.4 (the FCS version) or from Release 7.0.2.14 (the Maintenance Release 1 version).


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


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


Migrating from Release 6.0

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

  1. If you are at an earlier release, first upgrade to Release 6.0 Maintenance Release 5.
    See Upgrading to Cisco Unified MeetingPlace Release 6.0.
  2. Migrate from Release 6.0 Maintenance Release 5 to Cisco Unified MeetingPlace Release 7.0.
    See Migrating to Cisco Unified MeetingPlace Release 7.0 from Release 6.0
  3. Upgrade from Release 7.0 to Release 8.0.
    See Upgrading to Cisco Unified MeetingPlace Release 8.0 from Cisco Unified MeetingPlace Release 7.0 module.


Notes:

  • Cisco Unified Communications Manager Release 6.1.2, 7.0, 7.1 or 8.0 is required for voice and video SIP integration to Cisco Unified MeetingPlace Release 8.0. For audio-only installations, you may connect Cisco Unified MeetingPlace to Cisco Unified Communications Manager Release 6.0(3) or later release.
  • Cisco Unified Communications Manager software is automatically provided with the Cisco Unified MeetingPlace Release 8.0 Application Server software. Nevertheless, you need to:
    • Obtain the Cisco Media Convergence Server (MCS) hardware for Cisco Unified Communications Manager.
    • 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.


You can migrate from either Cisco Unified MeetingPlace Express or Cisco Unified MeetingPlace Express VT, which provides ad hoc voice, web, and video conferencing.


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:


http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Rating: 0.0/5 (0 votes cast)

Personal tools