The Oracle Web Conferencing and Oracle Messenger console clients attempt to connect to the Oracle Real-Time Collaboration system using one of the following methods, attempting them in the following order until successful:
1. Direct TCP/IP: Clients within a corporate intranet connect directly to the RTC Redirector, which hands off connections to the Client Connection Manager (for instant messages) or Multiplexer (for Web conferences), using XMPP/XMPPS for messaging, or proprietary protocols (MX) with TCP/IP or SSL for Web Conferences. This takes place over port 1025.
2. HTTPS direct: Clients in the open Internet or across transparent proxies connect using HTTPS. The mod_imeeting plug-in uses the Oracle HTTP Server as the single listening point over port 443, then hands the socket off to the Connection Manager or Multiplexer, and the console connects directly to one of these.
3. HTTPS tunnel: Clients in a different intranet coming through their own internal proxy provide the console with proxy information from the browser settings. The console establishes a connection to the Oracle HTTP Server, which hands the connection off to the Connection Manager or Multiplexer over an HTTPS tunnel through the remote proxy. Again, the listening port is 443.
Reverse proxies in front of RTC for internet web conferencing are not supported. The traffic between the console and the back-end server is not plain HTTP, therefore reverse proxies (which can only deal with HTTP) would not be able to pass them further.
No comments:
Post a Comment