Solink Recording Device
The following outbound communications from the Solink Recording Device to these domains must be allowed for the Solink service to work:
*solinkcloud.com HTTPS
*solinkcloud.com UDP 3478 (WebRTC)
*amazonaws.com HTTPS
*solinkshare.io HTTPS
*backblazeb2.com HTTPS
*solink.direct HTTPS
8.8.8.8 DNS (or 1.1.1.1, etc - customer provided DNS via DHCP)
time.aws.com UDP 123 (if not using customer NTP server)
Solink Client Devices
The following outbound communications from the Solink client devices to these domains must be allowed for the Solink service to work:
*solinkcloud.com HTTPS
*solinkcloud.com UDP 3478 (WebRTC)
*amazonaws.com HTTPS
*solinkshare.io HTTPS
*solink.direct HTTPS (if local playback is used)
time.aws.com UDP 123 (if not using customer NTP server)
If your IT team needs more details, please contact our Sales Engineering team.
Video Alarms
The following outbound communications to these domains must be allowed for Solink Video Alarms to work:
SIP Speakers
*.sip.us1.twilio.com TCP 5061 (SIP TLS) - SIP Signalling
168.86.128.0/18 UDP 10000-60000 (SRTP) - Audio
Video Alarm Tablet (v2)
mason.glbth.com TCP 443 (HTTPS) - API and Streaming Services
mason-mq22.glbth.com TCP 443 (HTTPS) - Message Broker for push delivery
visomdm.com TCP 443 (HTTPS) - MDM Device management
*.pushy.me TCP 443 (HTTPS) - Notification Push Service API endpoints
*.pushy.io TCP 443 (HTTPS) - Notification Push Service Delivery Infrastructure
*.twilio.com TCP 443 (HTTPS) - WebRTC
us-west-2-turn.glbth.com TCP 5349 (TURN TLS) - Audio relay
168.86.128.0/18 UDP 10000-60000 (SRTP) - Audio