watchRTC collects its metric via a secure WebSocket connected to the testRTC backend servers.
The only connection you need to configure on your firewall is for devices reaching out to wss://watchrtc.testrtc.com and/or https://watchrtc.testrt.com – both on port 443.
watchRTC offers 3 alternatives to deal with firewalls:
- Configure the firewall by opening connections to wss://watchrtc.testrtc.com and https://watchrtc.testrtc.com on port 443
- Set up your own CNAME redirection to watchrtc.testrtc.com (something like watchrtc.<your-domain>.com). This has the added benefit of requiring less configuration for your end users if you are already asking for them to wildcard *.<your-domain>.com for example
- Setup a proxy in your own data centers and configure it to our servers. You will also need to configure the SDK by redirecting it to your proxy