eduMEET Logo

Federation onboarding

Overview

What this onboarding covers

Requirements for infrastructure providers joining the African eduMEET Federation and using eduMEET common services. The federation 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 maximum load, subsequent participants use a different node, and the system routes between nodes.

Note for Subscribers

Service subscribers don't need local media-node infrastructure. The server, firewall and DNS requirements below apply to infrastructure contributors. Contact PMO@wacren.net about subscriber onboarding.

Benefits

Service for infrastructure providers

Providers receive a web conferencing service under their own domain, for example edumeet.nren-ng.net, integrated with an OpenID Connect identity provider (eduID.africa, BonafID or any eduGAIN-compatible IdP), plus an admin interface to manage users, permissions and rooms.

Pilot Period Costs

Cost during the pilot: free for infrastructure providers. Afterwards, entitlement is based on contributed infrastructure. Long-term excess use is covered by additional contribution or an agreed excess fee.

Deployment Checklist

Everything you need to set up your infrastructure for the African eduMEET Federation.

Node DeploymentMedia Server Clustering & Firewall Ingress Topology
01

Server Sizing

Size media nodes using this rule: 1 CPU core + 50 Mbps outgoing bandwidth per 10 participants. Install Ubuntu 24.04. OS and eduMEET software maintenance is handled by the eduMEET team at PCSS.

  • Up to 16 cores 1 Gbps, 8GB RAM
  • Up to 48 cores 2.5 Gbps, 16GB RAM
  • Up to 128 cores 10 Gbps, 32GB RAM

Add this to root's trusted SSH keys:

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIK4OD1LfqRHzQe0rMsF7E6VlcF4nQV4HhBNeW4WT0Q0LCopy
02

Firewall Config

Configure your firewalls to allow incoming WebRTC and signaling traffic for optimal media relay and fallback connectivity.

  • TCP 443, 80: TURN over TLS, Let's Encrypt
  • TCP 22: SSH from 167.235.130.84
  • TCP 3443: Management nodes (91.99.192.218, 91.99.222.184)
  • TCP/UDP 40000–40249: DTLS, SRTP/SRTCP media
  • UDP 50000–60000: Media TURN
03

DNS Setup

Add a CNAME record for the domain your users will use. The target points to the federation's management node.

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

Replace nren-ng.net with your domain.

SSO / OpenID Connect

Optional but strongly recommended: it enables institutional identity for room management and persistent rooms. Register a new application in your SSO service:

ParameterValue
client_idedumeet, or another chosen name
client_secretString of [a-z][A-Z][0-9], at least 32 characters
redirect_urihttps://admin.edumeet.eu/oauth/tenant/callback
post_logout_redirect_urihttps://admin.edumeet.eu/auth/logout-close

Send WACREN your client_id, client_secret and discovery_url. WACREN coordinates with the eduMEET team. Institutions on eduID.africa or BonafID already have OIDC-compatible metadata.

Contact WACREN

For joining the federation as an infrastructure contributor, email PMO@wacren.net or use the enquiry form.