For the majority of networks, there will be no issues using the Dolby.io Communications Client SDKs. However if you have an environment that is behind a restrictive network, use the following information to create the proper firewall whitelist configuration:
From the client perspective, there are three types of traffic: HTTP requests, WebSocket requests, and media traffic. The following table lists the destination ports to add to your firewall whitelist:
|Network Traffic Type||Port / Type||Destination Domain|
|HTTP||443 / TCP||session.voxeet.com|
|WebSocket||443 / TCP||ws-region.voxeet.com|
region is the conference region; the possible values are:
- ca: Canada
- us: United States
- eu: Europe
- in: India
- au: Australia
|Media||20000-65000 / UDP||Open to all traffic|
For HTTP and WebSocket requests, you can optionally whitelist *.voxeet.com and *.dolby.io.
Traffic to telemetry.voxeet.com is not critical and is used for network monitoring and support.
For media traffic, you must open the ports to all traffic. If this is not possible, as an add-on feature, you can use our fixed IP pool, where we provide a list of IP addresses to whitelist on those ports. We do not provide FQDNs for our media servers.
For the Dolby.io Communications REST APIs, you will need to whitelist TCP port 443 for api.voxeet.com and *.api.dolby.io.
Updated 9 months ago