Build Your Own eduMEET Service
eduMEET is an Open Source web-conferencing service from GÉANT portfolio. It is an interactive, web-based videoconferencing platform, supporting distant learning processes, including audio-video communication, chat, screen and file sharing.
Created by our community for our community. Trustworthy, self-hosted, secure. Integrated with community owned STUN/TURN service. Keeping traffic inside community networks. All this makes eduMEET safe and cost effective alternative to commercial solutions.
1. eduMEET installation
1.1 eduMEET service requirements:
Min. configuration of VM / server
- typical modern CPU (8 cores)
- RAM: ~ 8 GB
- HDD: ~ 100GB
- 1 network adapter (1Gb/s)
- OS: Ubuntu / Debian
- public IP address (without any NAT)
- domain name assigned (for certificates)
With this minimum configuration the eduMEET service is able to handle up to ~600 concurrent users.
1.2 eduMEET software installation
Before you start the installation please request LTC STUN/TURN credentials for your eduMEET instances
There are two recommended ways of installations:
1) Ansible installation
- GitHub repository: github.com/edumeet/edumeet-ansible
- Video tutorial (step-by-step terminal recording) : asciinema.org/a/311365
2) Direct docker image installation
- GitHub repository: github.com/edumeet/edumeet-docker/tree/dev
- DockerHub repository: hub.docker.com/r/edumeet/edumeet
2. eduTURN installation
2.1 eduTURN description
eduTURN is community owned and managed STUN/TURN service, based on open source coturn. It is not a must have service, but very helpful for overcoming NAT, firewall and packets filtering issues (because of which about 30% of connections can fail). There are 10 nodes in Europe already now, but - the more, the better. Moreover - it's good to have a node close to VC participants.2.2 eduTURN service requirements
Two medium class virtual or physical machines!
Reason: 2 authentication types are supported:
- Long Term Credential
- REST
Both of them can not be implemented in one service (they conflicts because REST reuse TURN username/password part in a different way).
Min. configuration of each server:
- typical CPU (2-4 cores)
- RAM: ~ 8GB
- HDD: ~ 100GB
- at least 1, (or better 2) network adapters
- OS - stable Debian 8
Additional requirements:
- at least 1, (or better 2) public global IPv4 addresses,
- at least 1 (or better 2) IPv6 addresses,
- DNS resolvers: 2x IPv4 and 2x IPv6,
- and the host FQDN.
2.3 eduTURN software installation
- GitHub repository: coturn.net