The SightCall integration requires some ports to be open on your network. When using the RTCC Driver, make sure the following ports are not blocked on your firewall/proxy:
- TCP 443 (HTTPS)
Network Setup For Restricted Networks
If you maintain a restricted network, make sure the following URL schemes and ports are open / allowed:
- *.rtccloud.net : TCP 443 (mandatory)
- *.rtccloud.net : TCP 5204 (optional - used if 443 is blocked)
- *.rtccloud.net : TCP 11005 (optional - used if 443 is blocked)
- *.rtccloud.net : Allow UDP traffic (dynamic port range)
- *.sightcall.com : TCP 443 (mandatory)
- *.mapbox.com : TCP 443
- 1 and 5 are the minimum requirements to make it work, but 4 is highly recommended for better reliability and performance.
- TLS 1.0 and 1.1 are not supported. Make sure TLS 1.2 or newer is used instead.
- 6 is required if you use Geolocation feature in the use case.
- If your network only allows IP whitelisting, you can review this article for details.
If you are using Zscaler Cloud Solution or a similar network security solution, you need to disable Deep Packet Inspection / SSL Inspection for *.rtccloud.net
Monitoring Internet Bandwidth Usage
To prevent any quality problem during video sessions, the global network bandwidth usage, as well as SightCall specific usage, should be monitored. Internet usage should never exceed 90% of the link capacity.
The video quality may be temporarily affected by network congestion.
The network bandwidth must be sufficient to support the targeted number of simultaneous video sessions (300 - 500 kbps per call depending on the use case). More details can be viewed here: https://support.sightcall.com/hc/en-us/articles/202614365-Bandwidth-Requirement-Data-Usage
SightCall packets should be tagged as the highest priority streams (real-time) to ensure that they will be forwarded as quickly as possible.
Depending on the network configuration, some bandwidth may even be reserved for video sessions.