Chapter 1 Introducing Cisco Unified MeetingPlace Web Conferencing
About Cisco Unified MeetingPlace Web Conferencing
How Users Connect to 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
The meeting console communicates with the Flash Media Server on the Web Conferencing server through TCP port 1627, as shown in Figure
The web server also supports tunneling over HTTPS by using Secure Sockets Layer (SSL).
Figure 1-1 How Users Communicate with Cisco Unified MeetingPlace Web Conferencing
Using the home page and meeting console
1
Using the home page
Using the meeting console
(TCP port 80)
2
(TCP port 1627)
3
Web-
conferencing
server
191838
1.For external participants, the meeting console tunnels communication by using HTTP through TCP port 80.
2.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.
3.For internal participants using the meeting console, connection is made directly to the web server over TCP port 1627.
How Web Conferencing Fulfills Requests
Figure 1-2 shows how Cisco Unified MeetingPlace Web Conferencing components work together to fulfill user requests.
Installation and Upgrade Guide for Cisco Unified MeetingPlace Web Conferencing Release 6.x
|
| ||
|
|
