Hardware Requirements in Cisco

Hardware Capacity

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	1000	1300
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

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

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

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

Express Media Server Requirements

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

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

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.

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	300	160

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.

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

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.

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

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

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

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

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

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.

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.

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

Network Requirement in Cisco

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

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)

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.

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

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.

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

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.

Cisco PIX

Cisco PIX (Private Internet eXchange) is a popular IP firewall and network address translation (NAT) appliance. It was one of the first products in this market segment.

In 2005, Cisco introduced the newer Adaptive Security Appliance (ASA), that inherited much of PIX features, and in 2008 announced PIX end-of-sale.

The PIX technology is still sold in a blade, the FireWall Services Module (FWSM), for the Cisco Catalyst 6500 switch series and the 7600 Router series.

PIX was originally conceived in early 1994 by John Mayes of Redwood City, California and designed and coded by Brantley Coile of Athens, Georgia. The PIX name is derived from its creators' aim of creating the functional equivalent of an IP PBX to solve the then-emerging registered IP address shortage. At a time when NAT was just being investigated as a viable approach, they wanted to conceal a block or blocks of IP addresses behind a single or multiple registered IP addresses, much as PBXs do for internal phone extensions. When they began, RFC 1597 and RFC 1631 were being discussed, but the now-familiar RFC 1918 had not yet been submitted.

The design, and testing were carried out in 1994 by John Mayes, Brantley Coile and Johnson Wu of Network Translation, Inc., with Brantley Coile being the sole software developer. Beta testing of PIX serial number 000000 was completed and first customer acceptance was on December 21, 1994 at KLA Instruments in San Jose, California. The PIX quickly became one of the leading enterprise firewall products and was awarded the Data Communications Magazine "Hot Product of the Year" award in January 1995.

After Cisco acquired Network Translation in November 1995, Mayes and Coile hired four long time associates: Jim Jordan, Tom Bohannon, and Richard Howes and Pete Tenereillo (both who worked for NTI prior to the acquisition). Together they continued development on Finesse OS and the original version of the Cisco PIX Firewall, now known as the PIX "Classic". During this time, the PIX shared most of its code with another Cisco product, the LocalDirector.

End-of-Life

On January 28, 2008, Cisco announced the end-of-sale and end-of-life dates for all Cisco PIX Security Appliances, software, accessories, and licenses. The last day for purchasing Cisco PIX Security Appliance platforms and bundles was July 28, 2008. The last day to purchase accessories and licenses was January 27, 2009. Cisco will continue to support Cisco PIX Security Appliance customers through July 27, 2013.

Adaptive Security Appliance (ASA)

Cisco ASA

In May 2005, Cisco introduced the Adaptive Security Appliance (ASA) which combines functionality from the PIX, VPN 3000 series and IPS product lines. The ASA series of devices run PIX code 7.0 and later. Through PIX OS release 7.x the PIX and the ASA use the same software images. Beginning with PIX OS version 8.x, the operating system code diverges, with the ASA using a Linux kernel and PIX continuing to use the traditional Finesse/PIX OS combination.

Description of operation

The PIX runs a custom-written proprietary operating system originally called Finese (Fast InterNEt Server Executive), but now the software is known simply as PIX OS. It is classified as a network layer firewall with stateful inspection, although technically the PIX would more precisely be called a Layer 4, or Transport Layer Firewall, as its access is not restricted to Network Layer routing, but socket based connections (a port and an IP Address - Port communications occur at Layer 4). By default it allows internal connections out (outbound traffic), and only allows inbound traffic that is a response to a valid request or is allowed by an Access Control List (ACL) or a conduit. The PIX can be configured to perform many functions including network address translation (NAT) and port address translation (PAT), as well as being a virtual private network (VPN) endpoint appliance.

The PIX was the first commercially available firewall product to introduce protocol specific filtering with the introduction of the "fixup" command. The PIX "fixup" capability allows the Firewall to apply additional security policies to connections identified as using specific protocols. Two protocols for which specific fixup behaviors were developed are DNS and SMTP. The DNS fixup originally implemented a very simple but effective security policy; it allowed just one DNS response from a DNS server on the Internet (known as outside interface) for each DNS request from a client on the protected (known as inside) interface. "Fixup" has been superseded by "Inspect" on later versions of PIX OS.

The Cisco PIX was also one of the first commercially available security appliances to incorporate IPSec VPN gateway functionality.

The PIX can be managed by a command line interface (CLI) or a graphical user interface (GUI). The CLI is accessible from the serial console, telnet and SSH. GUI administration was introduced with version 4.1, and it has been through several incarnations: PIX Firewall Manager (PFM) for PIX OS versions 4.x and 5.x, which runs locally on a Windows NT client; PIX Device Manager (PDM) for PIX OS version 6.x, which runs over https and requires Java; and Adaptive Security Device Manager (ASDM) for PIX OS version 7 and greater, which can run locally on a client or in reduced-functionality mode over HTTPS. Examples of emulators include PEMU and Dynagen , and with NetworkSims.com ProfSIMs (Networksims) for a simulator.

As the PIX is an acquired product, the CLI was originally not aligned with the Cisco IOS syntax. Starting with version 7.0, the configuration is much more IOS-like. As the PIX only supports IP traffic (as opposed to IPX, DECNet, etc.), in most configuration commands 'ip' is omitted. The configuration is upwards compatible, but not downwards. When a 5.x or 6.x configuration is loaded on a 7.x platform, the configuration is automatically converted to 7.x formatting, as long as the configuration was using ACLs, versus conduits and "outbounds". This allows for an easy migration from PIX to ASA. PIX OS v7.0 is only supported on models 515, 515(E), 525 and 535. Although the 501 and 506E are relatively recent models, the flash memory size of only 8 MB prevents official upgrading to version 7.x, although 7.0 can be installed on a 506E using monitor mode up to version 7.1(2). The 8MB flash size only allows for installation of the PIX OS software, not the ASDM software (GUI). For the PIX 515(E) to run version >7.0, a doubling of the memory size is required (32->64 MB for restricted and 64->128MB for Unrestricted/Failover licenses). A 515(E) UR/FO can run 7.0 with 64 MB memory installed, but that is not recommended as larger configuration and session/xlate tables can exceed the available memory.

Description of hardware

PIX 515 with top cover removed.

The original NTI PIX and the PIX Classic had cases that were sourced from OEM provider Appro. All flash cards and the early encryption acceleration cards, the PIX-PL and PIX-PL2, were sourced from Productivity Enhancement Products (PEP).Later models had cases from Cisco OEM manufacturers.

The PIX was constructed using Intel-based/Intel-compatible motherboards; the PIX 501 used an AMD 5x86 processor, and all other standalone models used Intel 80486 through Pentium III processors. Nearly all PIXs used Ethernet NICs with Intel 82557, 82558, and 82559 network chipsets, but some older models are occasionally found with 3COM 3c590 and 3c595 Ethernet cards, Olicom-based Token-Ring cards, and Interphase-based FDDI cards.

Some Intel-based Ethernet cards for the PIX are identified at boot with the designation "mcwa". This designation denotes a multicast receive bug in the card's firmware that the designers addressed with a feature they called Multi Cast Work Around.

Both the PIX 510 and 520 share basic components, such as motherboard, chassis, NICs, flash cards, etc., with the Cisco LocalDirector 416/420/430, the Cisco Service Selector Gateway 6510 (SSG-6510), and the Cisco Cache Engine CE2050, though the latter two run VxWorks, rather than a Finesse derivative.

The PIX boots off a proprietary ISA flash memory daughtercard in the case of the NTI PIX, PIX Classic, 10000, 510, 520, and 535, and it boots off integrated flash memory in the case of the PIX 501, 506/506e, 515/515e, 525, and WS-SVC-FWM-1-K9.

The PIX technology implemented in the FWSM, for the Catalyst 6500 and the 7600 Router, has a part code of WS-SVC-FWM-1-K9.

The PIX535 has a PCI-X 66 MHz/64 bit bus for expansion slots. This results in a much higher cleartext throughput, as the PCI bus is no longer the bottleneck (the PCI bus is 33 MHz and 32 bits, resulting in maximum throughput of 1.2 GBit without overhead taken in account). As the lower Cisco ASA models use a PCI bus, the PIX535 was faster for cleartext than its successor ASA, until the introduction of the ASA5580.

Specifications of latest and older models

Latest models

Model	501	506e	515e	525	535	FWSM
Introduced	2001	2002	2002	2000	2000	2003
Discontinued	2008	2008	2008	2008	2008
CPU type	AMD SC520 5x86	Intel Celeron (Mendocino SL36A)	Intel Celeron (Mendocino SL3BA)	Intel Pentium III (Coppermine)	Intel Pentium III (Coppermine)	One Intel Pentium III and three IBM 4GS3 PowerNP network processors
CPU speed	133 MHz	300 MHz	433 MHz	600 MHz	1 GHz	1 GHz
Chipset	AMD SC520	Intel 440BX Seattle	Intel 440BX Seattle	Intel 440BX Seattle	Broadcom Serverworks RCC	?
Default RAM	16 MB	32 MB	64 (128) MB	128 (256) MB	512 (1024) MB	1 GB
Boot flash device	Onboard	Onboard	Onboard	Onboard	ISA card & Onboard	Onboard
Default flash	8 MB	8 MB	16 MB	16 MB	16 MB	128 MB
Boot flash chips	1 x 28F640	1 x 28F640	1 x E28F128J3	1 x EF28F128J3	2 x i28F640J5	ATA CompactFlash
Minimum PIX OS version	6.1(1)	5.1(x)	5.1(x)	5.2(x)	5.3(x)	FWSM 2.3(x)
Maximum PIX OS version officially supported	Latest 6.3(x)	Latest 6.3(x)	8.0.4	8.0.4	8.0.4	FWSM 4.0(x)
Max interfaces	2	2	3(6)	6(10)	8(14)
PCI slots	0	0	2	3	9	1
Expansion cards supported	No	No	1 port FE, 4 port FE, 1 port 1000baseSX	1 port FE, 4 port FE, 1 port 1000baseSX	1 port FE, 4 port FE, 1 port 1000baseSX	Yes
Supports SSL VPN	No	No	No	No	No	No
VPN accelerator supported	No	No	Yes	Yes	Yes	No
Floppy drive	No	No	No	No	No	No
Failover supported	No	No	Yes	Yes	Yes	Yes
Model	501	506e	515e	525	535	FWSM

Older models

Model	NTI PIX	Classic 47-3158-01	10000	506	510	515	520
Introduced	1994	1995	1996	2000	1997	1999	1999
Discontinued	1995	1998	1998	2002	1999	2002	2001
CPU type	Intel 486DX2/ Intel Pentium	Intel Pentium	Intel Pentium Pro	Intel Pentium MMX	Intel Pentium	Intel Pentium MMX	Intel Pentium II (Deschutes)
CPU speed	66 / 90 MHz	100~133 MHz	200 MHz	200 MHz	166 MHz	200 MHz	233~350 MHz
Chipset		Intel 430FX/TX	Intel 440FX Natoma	Intel 430TX	Intel 430TX	Intel 430TX	440LX/BX Balboa/ Seattle
Default RAM	4 MB	8 MB	16 MB	32 MB	16 MB	32 (64) MB	128 MB
Boot flash device	ISA card	ISA card	ISA card	Onboard	ISA card	Onboard	ISA card
Default flash	512KB	512KB / 2 MB	2 MB	8 MB	2 MB	16 MB	2 MB / 16 MB
Boot flash chips	2 x i28f020	2 x i28f020 / 4 x 29C040	4 x 29C040	1 x i28F640J5	4 x 29C040	2 x i28F640J5	4 x 29C040 / 2 x i28F640J5
Minimum PIX OS version	1.x	2.x	4.4(x)	4.4(x)	4.4(x)	5.1(x)	4.4(x)
Maximum PIX OS version	4.2(2)	4.2(2) 5.1(x)	5.1(x)	Latest 6.3(x)	5.3(4)	Latest 8.x	Latest 6.3(x)
Max interfaces				2		6(3)	8(6)
Fixed internal interface	No	No	No	10baseT	No	10/100baseT	No
Fixed external interface	No	No	No	10baseT	No	10/100baseT	No
PCI slots	?	4	4	0	4+	2	4+
Expansion cards supported	?	1 port FE, 1 port Token Ring, 1 port FDDI	1 port FE, 1 port Token Ring, 1 port FDDI	No	1 port FE, 1 port Token Ring, 1 port FDDI	1 port FE, 4 port FE, 1 port 1000baseSX	1 port FE, 4 port FE, 1 port 1000baseSX
VPN accelerator supported	Yes	Yes	Yes	No	Yes	Yes	Yes
Floppy drive	Yes	Yes	Yes	No	Yes	No	Yes
Failover supported	No	No/Yes	Yes	No	Yes	Yes	Yes
Model	NTI PIX	Classic	10000	506	510	515	520

Performance specifications

Model	PIX Classic	PIX 10000	PIX 501	PIX 506	PIX 506e	PIX 510	PIX 515	PIX 515e	PIX 520	PIX 525	PIX 535	ASA 5520	FWSM
Cleartext throughput, Mbit/s		90	60	20	100		147	190	240	330	1655	450	5500
56-bit DES throughput, Mbit/s			6		20		n/a	n/a		n/a	n/a	?	n/a
168-bit Triple DES throughput, Mbit/s			3	6	16		10 / 63 (135)	20 / 63 (135)	20	30 / 72 (145)	50 / 100 (425)	225	n/a
AES-128 throughput, Mbit/s			4.5		30			45 / 130		65 / 135	110 / 495	225	n/a
AES-256 throughput, Mbit/s			3.4		25			35 / 130		50 / 135	90 / 425	225	n/a
Max simultaneous connections		16,000	7,500	10,000	25,000		64,000 / 128,000	48,000 / 130,000	256,000	140,000 / 280,000	250,000 / 500,000	280,000	999,900 total / 100,000 per second
Max simultaneous hosts (users)			10 / 50 / Unlimited		Unlimited			Unlimited	128 / 1000 / unlimited	Unlimited	Unlimited	?	256,000
Max number of ACL entries												?	80,000
Max simultaneous VPN peers			10	25	25			0 / 2000		0 / 2000	0 / 2000	750 IPSec, 750 SSL	n/a
Model	PIX Classic	PIX 10000	PIX 501	PIX 506	PIX 506e	PIX 510	PIX 515	PIX 515e	PIX 520	PIX 525	PIX 535	ASA 5520	FWSM

Cisco WebEx

WebEx Communications Inc. is a Cisco company that provides on-demand collaboration, online meeting, web conferencing and videoconferencing applications. Its products include Meeting Center, Training Center, Event Center, Support Center, Sales Center, MeetMeNow, PCNow, WebEx AIM Pro Business Edition, WebEx WebOffice, and WebEx Connect. In 2005 David Needle described WebEx as "the leading provider" of certain "online meeting applications"

History

WebEx was founded in 1996 the name ActiveTouch by Subrah Iyar and Min Zhu. Zhu had co-founded Future Labs (one of the first companies to produce multi-point document collaboration software) in 1991.Zhu met Iyar, then a vice president and general manager of Quarterdeck, when Quarterdeck acquired Future Labs in 1996. Iyar was named president of Future Labs, which had been made a Quarterdeck subsidiary, and the same year Iyar and Min went on to co-found WebEx. On March 15, 2007, Cisco Systems announced it would acquire WebEx for $3.2 billion.

Traveling Software, now known as LapLink, originally owned a software product called WebEx, which shipped to the public in June 1996. The LapLink product called WebEx was a utility to be run as a companion to be used for offline web browsing, a feature which is now integrated inside of most commercial modern day internet browsers.

Traveling Software originally registered the WebEx trademark in May 1996.

However, in 1999, after the original founder of LapLink returned as CEO, Traveling Software/LapLink.com sold the rights to the WebEx name to the company that is known today as WebEx.

Securities

Before the purchase by Cisco, WebEx featured in the NASDAQ Global Select Market.

Cisco acquisition

On March 15, 2007, Cisco Systems announced that it had agreed to pay $57 per share to acquire WebEx. The deal values WebEx at about $3.2 billion, or $2.9 billion when WebEx's cash reserves are factored into the price. WebEx's largest stockholder is Jan Baan with 9% of outstanding shares. In a press release Cisco said WebEx would "become a part of Cisco's Development Organization while maintaining its unique business model".Cisco has also said that its long-term plan is to absorb WebEx at both a technology and a sales level.

There is also increased use of WebEx as an online learning platform and classroom for a diverse set of education providers.The platform has worked for educational institutions because of real-time collaboration using an interactive whiteboard, chat, and VOIP technology that allows audio and video sharing. In distance-learning situations, while replacing the classroom with features, institutions have also looked for security features that are inherently strong in a Cisco powered collaboration environment. The downside is that WebEx is not a free platform like WiZiQ or Moodle and fees are paid per "host" of a classroom or a meeting. Some organizations are, however, beginning to integrate WebEx with Moodle.

Services

All WebEx applications are built on the MediaTone platform and supported by the WebEx MediaTone Network (originally called the WebEx interactive network),^[12] a global network intended for use with on-demand programs. The network was designed by Shaun Bryant, WebEx's Chief Network Architect, and Zaid Ali Sr, Network Architect, to be one of the first SaaS platforms on the internet.

WebEx Application Suite The firm provides a suite of applications designed for business processes such as sales, support, training and marketing processes:

• WebEx Meeting Center - recreates face-to-face meetings with real-time data, application-, voice- and video-sharing capabilities.
• WebEx Sales Center - features automatic attention notification to alert sales professionals when they are losing a prospect’s attention, branded prospect portals providing a secure location to share information, and real-time sales analytics and reporting.
• WebEx Training Center provides facilities for trainers, including breakout-session support and learner testing, tracking and reporting. In 2010 an on-demand LMS module was added , a component of the overall E-learning Suite
• WebEx Support Center - allows support agents to identify, resolve and track customer issues within a secure, online support session
• WebEx Event Center - intended for web seminars and events; WebEx Event Center includes automated lead-scoring, email-invitation management and an event-producer dashboard
• WebEx LiveStream - intended for large events (100 - 200,000 attendees) that require onsite production, TV-quality video, voice, and powerpoint.
• WebEx Consulting Services - expert teams can provide education, content, and delivery related to building online sales teams, universities, marketing programs, etc.
• WebEx WebOffice - an on-demand collaboration suite designed for small businesses, with a document manager, group calendar, database manager, task manager and other collaborative business tools.
• MeetMeNow and PCNow
  • MeetMeNow - a lightweight web meeting application for individuals, allowing them to conduct unlimited instant meetings with up to 15 attendees. Does not include custom-branded site.
  • PCNow - allowing users to securely access remote computers by using a mobile phone or web browser.

The company acquired Intranets.com in 2005, providing entrance into the small- and mid-size business market through the company's customer base of businesses with fewer than 100 employees. It acquired the ability to offer online collaboration tools such as discussion forums, document sharing and calendaring while Intranets.com provided access to the WebEx communications environment for its customers.

On February 21, 2006, AOL and WebEx announced plans to launch a business version of AOL's instant-messaging software, AIM Pro, with additional features to help workers collaborate using conferencing tools offered by WebEx.

On September 26, 2006, the company announced plans to offer a web collaboration "mashup" platform called "WebEx Connect".

Legal proceedings and inquiries

Goldman Sachs securities fraud investigation

As a result of a securities fraud investigation initiated by the SEC and by various state Attorney General offices, Goldman Sachs faced charges of issuing unfair research, including coverage of WebEx, and IPO violations. WebEx management allegedly dictated to Goldman Sachs analysts what the research should and should not include. WebEx maintains the management's information was accurate.Another charge accuses Goldman Sachs of violating securities law in its allocation of shares in WebEx's initial public offering.

Raindance lawsuit for patent infringement

On September 27, 2005, WebEx sued Raindance Communications, Inc., a competitor, for patent infringement. On October 14, 2005, Raindance filed a countersuit against WebEx for patent infringement. Both parties sought both damages and an injunction enjoining further acts they claim to be infringing on patents. On March 31, 2006, the parties agreed to the dismissal of both actions, releases of claims for past infringement, payments associated with those releases, and cross-licenses to each other's patents. The agreement resulted in Webex receiving $1.0 million from Raindance.