Cisco Systems Unified MeetingPlace Web Conferencing 사용자 설명서

Users connect to the Web Conferencing home page to sign in, schedule or find meetings to attend, and 
update their profile settings. This connection uses the primary IP address (or hostname) configured on 
the Web Conferencing server and port 80.

When a meeting is scheduled to begin, the Cisco MeetingPlace Agent Service instructs the web engine 
to initiate the meeting. As users join the web component of the meeting, the Flash-based meeting console 
is downloaded on their desktops, allowing them to connect to the Flash Media Server running on the Web 
Conferencing system by using the secondary IP address (or hostname) configured on the server.

The meeting console communicates with the Flash Media Server on the Web Conferencing server 
through TCP port 1627, as shown in 

. If this port is blocked due to a firewall, the Flash client 

establishes a tunnel connection over HTTP through port 80. This process allows the meeting console to 
bypass firewall restrictions so that external users can participate in web conferences. 

The web server also supports tunneling over HTTPS by using Secure Sockets Layer (SSL). 

For external participants, the meeting console tunnels communication by using HTTP through TCP 
port 80.

Cisco Unified MeetingPlace Web Conferencing home page traffic (signing on, scheduling meetings, 
changing profile settings, etc.) for both internal and external participants uses port 80.

For internal participants using the meeting console, connection is made directly to the web server 
over TCP port 1627.

 shows how Cisco Unified MeetingPlace Web Conferencing components work together to 

fulfill user requests.

Web-

conferencing

server

(TCP port 1627)

(TCP port 80)

Using the 

home page and

meeting console

Using the 

home page

Using the 

meeting console

191838