Settings for corporate network

If you are using a private or corporate network that has restrictions on connecting to external services, then add these addresses to the allow list or tell your IT department to add these addresses to the allow list.

In case of errors, please contact support@spatial.chat.

spatial.chat
*.spatial.chat

AWS Ireland region: https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html

Twilio Video
https://www.twilio.com/docs/video/ip-addresses
https://www.twilio.com/docs/stun-turn/regions

Our recommendation would also be to allow the domains *.millicast.com and *.xirsys.com. 

In case needed, our cloud vendor is Oracle Cloud.
IP ranges of
Oracle Cloud: https://docs.oracle.com/en-us/iaas/Content/General/Concepts/addressranges.htm

Firewall settings to Agora service:

.agora.io
.edge.agora.io
.sd-rtn.com
.edge.sd-rtn.com

Ports
TCP (allow) - 80; 443; 3433; 4700 - 5000; 5668; 5669; 6080; 6443; 8667; 9667; 30011 - 30013 (for RTMP converter)
UDP (allow) - 3478; 4700 - 5000

For Agora cloud proxy support (TCP fallback) use the following settings:

https://docs-preprod.agora.io/en/Video/cloud_proxy_na_web_ng?platform=Web 

On this page (and the pages linked to it) we have listed the exhaustive list of hosts, IP addresses, and ports that SpatialChat and our providers use to provide a full SpatialChat experience. This doesn't mean you have to whitelist them all. You should act as you encounter any issues, for example:

- if nothing works, you can't even see the website - start by whitelisting AWS;

- if you're having issues with SpatialRooms - whitelist Twilio Video;

- if you're having issues with Stage - whitelist Agora.

Some rules have to be set based on host, as the IPs are dynamic.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.