Federated infrastructure for eduMEET

version: 2025-12-30

1. Introduction

This document describes the requirements for infrastructure providers who wish to join the eduMEET federation and use eduMEET common services.

2. The concept of the eduMEET federation

The eduMEET federation service shares infrastructure resources for flexibility and scalability in the delivery of web conferencing services. It is centrally managed, but audio-video connections are optimised between distributed media nodes. Assignment to a node is based on geographical location and node load. If a node reaches its maximum load, subsequent participants in the call use a different node, and the system provides routing between nodes. Figure 1 shows a diagram of the eduMEET federation architecture.

eduMEET federation architecture diagram
Fig. 1 - eduMEET federation architecture diagram

3. Service for infrastructure providers

The infrastructure provider receives a web conferencing service for any use. The service is launched in the provider's domain (e.g. edumeet.nren-1.org) and integrated with an OpenID Connect-based identity provider (e.g. eduGAIN). The provider gains access to an administrative service for their domain, where they can manage users, their permissions and rooms. During the pilot period, the service is free of charge for the provider. After the pilot period, based on the volume of the infrastructure provided, the pool of simultaneously connected users who will be able to use the service without generating costs for the provider will be calculated. In the event of a long-term exceeding of the volume, the extension with additional infrastructure or the setting of an excess fee will be negotiated with the provider.

4. Requirements for infrastructure providers

Detailed requirements for the server, firewall, DNS, and SSO (optional) that the infrastructure provider should deliver are presented below.

4.1. Server

Servers made available for web conferencing as media nodes must meet the following simple rule: 1 CPU core + 50 Mbps outgoing connection bandwidth per 10 participants in the conversation. Therefore, we propose the following server configurations for providers:

The server is physically operated by the provider. It can be a physical or virtualised server. The server must have a public IPv4 address accessible from the Internet.

The supplier installs the Ubuntu 24.04 operating system on the server and adds the installation public key to the trusted SSH keys of the root user:

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIK4OD1LfqRHzQe0rMsF7E6VlcF4nQV4HhBNeW4WT0Q0L

At the operating system and eduMEET software level, maintenance and management are the responsibility of the eduMEET team.

4.2. Firewall

The provider configures the server access firewall according to the following rules for incoming traffic:

4.3. DNS

The provider configures DNS for its domain under which the eduMEET service is to be available to the provider's users (e.g.: edumeet.nren-1.org) by adding a DNS record:

4.4. SSO (optional)

eduMEET supports SSO login via OpenID Connect (OIDC). Integration with SSO is optional but recommended, as it enables the management of video-conference rooms and the creation of persistent rooms assigned to users with SSO.

To connect the provider's SSO login, the provider configures a new space in their SSO service:

The provider then passes the following parameters to the eduMEET team:

5. Contact