Skip to main content
Preparing Your Network for Multiverse Video Conferencing

A guide for IT teams to prepare the organization's network configuration to meet the requirements of Multiverse Video Conferencing

Updated over a week ago

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

In order to ensure your learners’ delivery sessions run smoothly on our platform in the coming weeks and months, please work with your IT teams to take the following actions. If apprentices' devices use a VPN, the VPN provider will also need to action the following to ensure this does not cause access challenges.

1. If your firewall or proxy requires or allows whitelisting via domain, add the following hosts and domains to your allow lists:

  • .sfu.whereby.com

  • .sfu.svc.whereby.com

  • .srv.whereby.com

  • .svc.whereby.com

  • .appearin.net

  • .turn.whereby.com

  • .turn.svc.whereby.com

  • check.multiverse.io

    IP Whitelisting: If you are unable to whitelist domains directly, we can provide a list of current server IPs upon request.
    Additional info - signaling (wss): During a call, control messages between servers (signaling) are transmitted over secure websockets (wss). Websockets use the same ports as HTTPS, establishing persistent two-way connections. Proxies and firewalls intercepting HTTPS traffic need to be configured to allow websocket traffic towards the above hosts/domains.


2. Add the following turn server hosts/domains to your allow lists:

  • .turn.whereby.com

  • .turn.svc.whereby.com

  • turnserver.appearin.net

    Additional info -TURN/SFU (media): To transmit video and audio, participants need to send and receive media packets. If a direct path isn't available, our video conferencing tool uses a network of global TURN servers as relays. These servers help maintain call quality by connecting participants to the nearest server via port 443, using either UDP or TCP. UDP is the preferred protocol for optimal performance. The TURN servers can be identified by the hostname patterns above.

3. Open port 443 to all TCP and UDP traffic:


We require this as we don't have a static range of IP addresses, so opening 443 to all TCP and UDP traffic is a quicker and simpler solution. Connections are initiated in the outbound direction. There is no requirement for ports to be open inbound and there are no port forwarding requirements. The following information can be set as outbound rules only.

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.

Did this answer your question?