Firewall and network settings for Physitrack

If a firewall only allows internet traffic to certain URLs or IP addresses, it uses the so-called whitelisting approach. Are you using Physitrack or Telehealth behind such a firewall? If so, make sure the following ports and URLs are whitelisted for our platform to work correctly.

Required

• XX.physitrack.com:443
• XX.physiapp.com:443
• search-XX.physitrack.com:443

• assets.physitrack.com:443
• cdn.physitrack.com:443
• physitrackuploads.s3.amazonaws.com:443
• *.firebaseio.com:443 (WebSocket Secure & HTTPS)
• identitytoolkit.googleapis.com:443
• media.physitrack.com:443
• cdn.jsdelivr.net:443
• *.algolia.net:443
• s3.eu-central-1.amazonaws.com:443 (we can provide a list of subpaths if this is too wide)
• s3.eu-west-1.amazonaws.com:443 (we can provide a list of subpaths if this is too wide)
• s3.us-east-1.amazonaws.com:443 (we can provide a list of subpaths if this is too wide)
• session.voxeet.com:443
• eu.comms.sdk.dolby.io:443 (WSS & HTTPS)
• th_eu.physitrack.com:443

Telemetry and monitoring

• *.ingest.sentry.io:443
• telemetry.voxeet.com:443

Tracking

• cdn.eu.pendo.io:443
• assets.customer.io:443

Support tools

• beacon-v2.helpscout.net:443

• To make sure we go through firewalls, we automatically switch from User Datagram Protocol (UDP) to Transmission Control Protocol (TCP; HTTPS).
• Currently, video calling does not go through China's firewall system.
• Check that there are no network errors in our Physitrack Telehealth system test.

See Google's documentation for presence detection (Google Firebase).

To test that your firewall settings work, start a test call (browser to browser) at https://app.voxeet.io/.

Make sure that each participant enters the same room name.