The SightCall integration requires some ports to be open on your network.
When using the RTCCdriver:
- Port TCP 443 (HTTPS)
Make sure these ports are not blocked on your firewall/proxy.
Network setup for restricted Networks
If you maintain a restricted network and cannot open port 443 for all connections, make sure the following URL schemes and ports are open/allowed :
- *.rtccloud.net : TCP 443 (default), optionally you can setup alternative ports 5204 and 11005 from the Admin Console to more easily identify SightCall packets
- *.rtccloud.net : allow UDP traffic
- *.sightcall.com: TCP 443
- *.mapbox.com (Enables geolocation)
Regardless, 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
In order to prevent any quality problem during video session, the global network bandwidth usage as well as SightCall specific usage should be monitored. Internet usage should never exceed 90% of the link capacity.
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). See here for more details: 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 to video sessions.