Multiverse Video Conferencing

Multiverse hosts delivery sessions within our own “on-platform” video conferencing for every Apprentice. This platform is fundamental for all learners and allows us to introduce features that strengthen our dynamic learning approach, and create a seamless learner experience for apprentices.

Learners must be able to access our video conferencing platform for their Flying Start (first session on program).

Please click ‘run test’ on the video connectivity test via this tool: check.multiverse.io

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 allowlisting via domain, add the following hosts and domains to your allow lists:

IP Whitelisting: If you are unable to allowlist 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:

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.

The session records the coach’s screen whilst they deliver the content. This will include: session length, in-session chat, chat participants, participant names, participants joining time, participant leaving time, resources that were used during the session, educational material used during the session, full video stream, and full audio streams. The recording will be shared with the apprentice’s cohort to enable apprentices to refer back to and revisit the session.