Overview
Multiverse hosts learning sessions using video conferencing software that is integrated into the learning platform. This guide is designed to support clients and their IT teams in preparing the organization’s network configuration, ensuring learners have a seamless experience.
How to Test the Software
To ensure connectivity and functionality, run a video connectivity test by clicking ‘run test’ on the tool available at: check.multiverse.io.
Required Access and Network Configuration
To ensure the smooth operation of learning sessions, please coordinate with your IT teams to perform the following actions. If learners’ devices utilize a VPN, the VPN provider must also implement these changes to avoid access issues.
Allow-listing Requirements:
If your firewall or proxy supports domain-based allow-listing, add the following hosts and domains:
sfu.whereby.com
rtcstats.srv.whereby.com
signal.appearin.net
sfu.appearin.net
any.sfu.whereby.com
signal.srv.whereby.com
rtcstats.appearin.net
check.multiverse.io
Note on Signalling (wss): During video calls, control messages (signalling) are transmitted over secure web sockets (wss), which use the same ports as HTTPS for two-way connections. Firewalls and proxies intercepting HTTPS traffic must be configured to permit web socket traffic for the listed hosts/domains.
TURN Server Configuration:
Add these TURN server hosts/domains to your allow lists:
*.turn.whereby.com
turnserver.appearin.net
Note on TURN/SFU (Media): To ensure the transmission of video and audio, our platform employs a network of global TURN servers for relaying media packets when a direct path is not available. These servers enhance call quality by connecting participants to the nearest server via port 443 using either UDP (preferred for optimal performance) or TCP. The TURN servers can be identified by the aforementioned hostname patterns.
Port Configuration:
Open port 443 for all TCP and UDP traffic. Since we don’t have a static IP address range, this practice simplifies and speeds up the setup process.
Connections are initiated in the outbound direction only. There’s no need for inbound ports to be open, and no port forwarding is required. The following can be set as outbound rules:
Service | Source | Destination port | Protocol |
browser-device | 443 | TCP | |
Whereby TURN relay (TCP/TLS) | browser-device | 443 | TCP |
Whereby TURN relay (UDP) | browser-device | 443 | UDP |
browser-device | 1024-65535 | UDP |
Have further questions? Reach out to [email protected] for help.