Kopano Web Meetings is an extension package for Kopano, it enables Real-Time-Communication for all users on the Kopano platform. The additional communication features are video, voice, chat, screen-sharing, content-sharing and filetransfer. All functionality is integrated into the WebApp. A presence-service indicates if a user is logged in and ready to receive a call or a chat-message.
This document explains how a user can work with these new communication features.
Although we, Kopano, try our best to keep the information in this manual as accurate as possible, we withold the right to modify this information at any time, without prior notice.
1.1. Intended Audience¶
This manual is intended for system administrators responsible for installing, maintaining, and supporting the Kopano deployment. We assume readers of this manual will have a thorough understanding of:
- Linux system administration concepts and tasks
- Assigning ports up HTTP servers and proxy concepts
The Kopano Web Meetings setup combines multiple server technologies running behind a common proxy server. The frontend proxy server is an NGINX server, which passes requests and connections on to an Apache server running Webapp and the Web Meetings server.
The installations of Kopano Web Meetings will require modification of the following components:
- Kopano WebApp (
kopano-webapp) - The next generation collaboration web client, which offers integration with chat, presence and video conferencing.
- Kopano Web Meetings service (
kopano-webmeetings) - A full featured WebRTC video conferencing interface that enables users to collaborate from any computer with an internet connection, a modern webbrowser (Iridium, Google Chrome, Firefox or Opera browser), a camera and a microphone.
- Apache - Serves web pages of the WebApp to the users browser, this server will need to be reconfigured to use a different port.
- NGINX - Serves as the frontend proxy server for both WebApp and Web Meetings and delivers tgese to the users browser from a common domain.
1.4. Protocols and Connections¶
All WebApp applications connect to the Kopano Server using HTTPS. The Web Meetings server maintains persisitent Web Socket connections which are upgraded from HTTPS connections. These are proxied through the frontend NGINX server.
1.4.1. Secure HTTP (HTTPS)¶
The Kopano Web Meetings browser Client needs to connect to the server over HTTP secured with SSL (HTTPS). All connections over the network will then be encrypted, making eavesdropping virtually impossible.
The Kopano Web Meetings server must be configured to also accept SSL connections (NGINX configuration). This requires the creation of SSL certificates. When the server certificate is created, SSL connections can be directly accepted from a client.