Technical onboarding

Federation onboarding requirements

Technical requirements and configuration steps for NRENs and institutions joining the African eduMEET Federation as infrastructure contributors.

Contact WACREN about joining View requirements

Overview

What this onboarding covers

This page describes the requirements for infrastructure providers who wish to join the African eduMEET Federation and use eduMEET common services.

The federation shares infrastructure resources for flexibility and scalability in the delivery of web conferencing services. It is centrally managed by the eduMEET team at PCSS, while audio-video connections are optimised between distributed media nodes across the WACREN backbone and contributing NREN PoPs.

Assignment to a node is based on geographical location and node load. If a node reaches its maximum load, subsequent participants use a different node, and the system provides routing between nodes.

Service subscribers Organisations that join as service subscribers do not need to provide local media-node infrastructure. Server, firewall, and DNS requirements below apply to infrastructure contributors. Contact WACREN at PMO@wacren.net to discuss subscriber onboarding.

Infrastructure providers

Service for infrastructure providers

The infrastructure provider receives access to a web conferencing service for its own use. The service is launched under the provider's domain — for example edumeet.nren-ng.net — and can be integrated with an OpenID Connect-based identity provider, including eduID.africa, BonafID, or any eduGAIN-compatible IdP.

The provider gains access to an administrative interface for their domain, where they can manage users, permissions, and rooms.

Cost model during pilot During the pilot period, the service is free of charge for infrastructure providers. After the pilot period, service entitlement is calculated based on the volume of infrastructure contributed. Long-term excess usage beyond that entitlement will be addressed through additional infrastructure contribution or an agreed excess fee.

Requirements

Requirements for infrastructure providers

Detailed requirements for the server, firewall, DNS, and optional SSO configuration are presented below. All requirements are identical to the European eduMEET Federation — the same software stack is used across both federations.

Server

Servers made available as media nodes should follow this sizing rule:

1 CPU core + 50 Mbps outgoing bandwidth per 10 participants

CPU	RAM	Storage	Network
Up to 16 cores	8 GB	80 GB SSD/HDD	1 Gbps
Up to 48 cores	16 GB	80 GB SSD/HDD	2.5 Gbps
Up to 128 cores	32 GB	80 GB SSD/HDD	10 Gbps

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

The provider installs Ubuntu 24.04 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 at PCSS.

Firewall

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

Source	Protocol / port	Purpose
ALL	ICMP	Ping
167.235.130.84	TCP 22	SSH — installation and maintenance access
ALL	TCP 80	Let's Encrypt certificates
ALL	TCP 443	TURN over TLS
91.99.192.218	TCP 3443	HTTPS/WSS — communication with management server
91.99.222.184	TCP 3443	HTTPS/WSS — management server backup
128.140.96.12	TCP 3443	HTTPS/WSS — Nagios monitoring
ALL	UDP 3478	TURN over UDP
ALL	TCP 40000–40249	DTLS over TCP, SRTP/SRTCP — media
ALL	UDP 40000–40249	DTLS, SRTP/SRTCP — media
ALL	UDP 50000–60000	DTLS, SRTP/SRTCP — media TURN

DNS

The provider configures DNS for the domain under which the eduMEET service will be available to their users — for example edumeet.nren-ng.net — by adding a CNAME record:

edumeet.nren-ng.net 300 IN CNAME rooms.edumeet.eu.

Replace nren-ng.net with your NREN's actual domain. The CNAME target (rooms.edumeet.eu) points to the federation's management node.

SSO / OpenID Connect

eduMEET supports SSO login via OpenID Connect. Integration with SSO is optional but strongly recommended for African federation participants — it enables institutional identity (eduID.africa / BonafID) to be used for room management and persistent room creation.

To connect the provider's SSO login, configure a new application in your SSO service:

client_id	`edumeet` or another chosen name
client_secret	Character string `[a-z][A-Z][0-9]`, minimum 32 characters
redirect_uri	`https://admin.edumeet.eu/oauth/tenant/callback`
post_logout_redirect_uri	`https://admin.edumeet.eu/auth/logout-close`

Pass the following parameters to WACREN, who will coordinate with the eduMEET team:

client_id
client_secret
discovery_url — your SSO provider's OpenID Connect discovery endpoint

If your institution uses eduID.africa or BonafID, your federation metadata is already compatible with OIDC integration. Contact WACREN to coordinate the specific configuration.

Contact

Contact WACREN to get started

Joining the federation

For matters related to joining the African eduMEET Federation as an infrastructure contributor or service subscriber.

PMO@wacren.net

Contact WACREN

eduMEET technical support

For technical support and operational questions from existing participants — contact the eduMEET team directly.

support@edumeet.eu

Contact eduMEET support