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 organisation’s network configuration, ensuring learners have a seamless experience.


How to Test the Software

To test connectivity and functionality, please run a video connectivity test by clicking ‘run test’ on the tool available at: check.multiverse.io. If the test is successful - no further action is required!


Allowlisting Requirements

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 allow access to the required domains. Alternatively, please ensure your VPN configuration allows access, or advise learners to connect to the platform with the VPN disabled.

If your firewall or proxy requires or allows allowlisting via domain, please add the following:

  • *.sfu.whereby.com

  • *.sfu.svc.whereby.com

  • *.srv.whereby.com

  • *.svc.whereby.com

  • *.appearin.net

  • *.turn.whereby.com

  • *.turn.svc.whereby.com

  • turnserver.appearin.net

  • *.posthog.com

  • *.sentry.io

  • *.helpscout.net

  • *.amazonaws.net

  • *.cloudfront.net

IP Whitelisting

Whereby servers don't currently have a static range of IP addresses. We can provide a list of current server IPs to our annual an enterprise customers upon request. Please request this from your account executive as required.

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


Did this answer your question?