Working with Firewall
When it comes to connectivity issues, firewall is frequently the culprit. You'll find some best practices for identifying if firewall is the issue and troubleshooting said problems with dscout Live below.
Test your system's compatibility with Twilio
dscout uses Twilio's cloud-based API to connect you to your mission leader during your Live session. If you believe firewall is prohibiting you from establishing a connection, run this test and verify that all steps pass.
Your test should pass the three tests listed below:
- TURN UDP Connectivity
- TURN TCP Connectivity
- TURN TLS Connectivity
If your test failed any of the three tests or doesn't look like the image to the right, this means that your firewall could be the issue. Your firewall should allow outgoing UDP to the public internet from Google Chrome and allow return traffic in response.
Twilio Whitelisted IP Address Ranges
To configure your firewall to allow communication with Twilio's API, please refer to the following whitelisted IP address ranges:
|Server IP Address Range / Hostnames||Port and Protocol|
| 22.214.171.124 - 126.96.36.199,
188.8.131.52 - 184.108.40.206
Ports used: 10,000 - 20,000 UDP/SRTP/SRTCP
More information about Twilio’s requirements can be found here.
Antivirus or Firewall Software
If you’re using an antivirus or firewall software, please ensure that Chrome and dscout are trusted or allowed by these programs. You could temporarily disable your antivirus or firewall to see if this resolves the issue.
Testing on a Different Environment
If all of the tests you ran above don't help to identify the issue, try using a different network and/or computer for your session and complete the following steps: