Cisco Cisco Unified MeetingPlace 7.0 Guida All'Installazione
36
System Requirements for Cisco Unified MeetingPlace Release 6.x
OL-13432-02
Requirements for Cisco Unified MeetingPlace Web Conferencing Release 6.x
Hardware Requirements
•
Two single Cisco MCSs or clusters of Cisco MCSs (in the case of load balancing)
–
One server or cluster of servers deployed inside the private corporate network functioning as
internal web servers.
internal web servers.
–
One server or cluster of servers deployed in a network segment, such as a DMZ, functioning as
external web servers.
external web servers.
Software Requirements
•
On internal web servers, Cisco Unified MeetingPlace Web Conferencing Release 6.x installed with
the “Internal (Full Access)” server location option.
the “Internal (Full Access)” server location option.
•
On external web servers, Cisco Unified MeetingPlace Web Conferencing Release 6.x installed with
the “External (Limited Access)” server location option.
the “External (Limited Access)” server location option.
DNS Configuration Requirements
•
For segmented DNS, the same host name must resolve to the internal web server on the internal DNS
and resolve to the external web server on the external DNS.
and resolve to the external web server on the external DNS.
•
For information on configuring notification templates to accommodate nonsegmented DNS, see the
administration guide for your particular Cisco Unified MeetingPlace notification application.
administration guide for your particular Cisco Unified MeetingPlace notification application.
•
Make sure that the internal host names and IP addresses are accessible only from the internal
network.
network.
•
Make sure that the external host names or IP addresses are accessible from both the internal network
and the Internet.
and the Internet.
Port Access Requirements
•
Make sure that the following ports are 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 Audio Servers (primary server and shadow server, if one exists).
MeetingPlace Audio Servers (primary server and shadow server, if one exists).
If you configured your network for reverse connection, where your web servers are configured
with a MeetingPlace Server hostname instead of an IP address, the Audio Server can initiate a
reverse connection to the web server in the DMZ when port 5003 inbound is blocked.
with a MeetingPlace Server hostname instead of an IP address, the Audio Server can initiate a
reverse connection to the web server in the DMZ when port 5003 inbound is blocked.
•
Make sure that 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 console)
–
TCP Port 443 (if SSL is implemented)
Additional Requirements
•
Synchronized GUIDS between Internal and DMZ servers
The database of the internal server and external server must contain identical GUIDS.
WebConnect Requirements
WebConnect is used to make web scheduling and meeting attendance seamless across multiple
Cisco Unified MeetingPlace systems. Make sure that your system meets the following requirements
before you configure WebConnect.
Cisco Unified MeetingPlace systems. Make sure that your system meets the following requirements
before you configure WebConnect.