💡 In normal conditions Videosync will work fine on any network having access to public internet with HTTPS connections. However, in corporate networks you may need to adjust your Firewall or VPN rules.

Contents

Videosync event viewers

To make sure that Videosync is working smoothly in your network, you should make sure that following domains are accessible by user. We also recommend you to configure split tunneling in your VPN for the main domains to avoid unnecessary load to your network.

Viewing pages and the video stream

We recommend you to whitelist all HTTPS traffic to *.videosync.fi

Note: if your event site has custom domain (e.g. events.inderes.com, you also need to whitelist that domain).

If for some reason you can’t use wildcard for the subdomains, ask support@videosync.fi for the up to date list of the subdomains.

For the actual video stream delivery, we use HLS streaming delivered via AWS Cloudfront CDN.

Optional & external domains and their use cases

Player licensing: HTTPS to licensing.bitmovin.com (player actually works even if this domain is blocked)

Custom fonts from Typekit (if used in event): HTTPS use.typekit.net

You can verify that the stream is working on this stream test page.

https://flik.videosync.fi/katsoja-testi

Please note that your own event’s subdomain is most likely something else than “flik”!

Requirements for production crews using external RTMP encoder

This requirement applies only for internet connection used by stream production encoder (e.g. vMix or OBS).

For live stream encoding Videosync uses RTMP stream ingest. The encoder needs to have TCP port 1935 open to Videosync RTMP servers on domains: (IPs are unlikely to change)

| Domain | IP | Ports | | eu-n-1.videosync.fi | 13.49.2.41 | TCP 1935, 443 | | eu-n-2.videosync.fi | 13.48.36.178 | TCP 1935, 443 | | eu-w-1.videosync.fi | 52.51.231.171 | TCP 1935, 443 | 💡 As a technical producer, you can switch to RTMPS address (which is more likely to work in enterprise networks by default) by modifying the RTMP url to RTMPS url: rtmps://xxx.videosync.fi:443/acme_1

Videosync Web Studio requirements

Videosync Web Studio is powered by Daily.co & uses Daily’s infrastructure to power Videosync’s real time functionality.

Daily’s network requirements and guidance on corporate networks can be found here:

https://docs.daily.co/guides/privacy-and-security/corporate-firewalls-nats-allowed-ip-list.

Daily network compatibility test

When you open a Web Studio admin or speaker link, it automatically does a firewall check in background and if your Firewall limits your connectivity to Daily.co servers, you should get prompted a warning.

You can also use Daily network tests to verify your device & network readiness and to understand which connection might be blocked in your network or device.

New network test: network-test-v2.daily.co Old network test: network-test.daily.co/index.html

Legacy Teleconference Speaker Link

Videosync Teleconference service is powered by TurboBridge.

Following applies only for Speakers connecting to legacy presenter view. If your presenters are using Web studio to connect, please see the Videosync Web Studio requirements above

Legacy Web Call interface for remote presenters is hosted on following domains: https://palvelu.flik.fi/ and https://conference.financialhearings.com/.

Users connecting to teleconference via browser (remote presenters using Web Call) need to have firewall allowing port 443 TCP Outbound (Signaling Web Sockets) and ports 7800-32000 UDP Outbound (Voice Traffic ports) to 185.167.188.0/22 network.

Additionally, if HTTP proxy is being used, this proxy must allow web socket connections to wss://ws.turbobridge.com.