> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/install-connect-and-integrate/allow-list-urls.md). # Allow List URLs Information on URLs we recommend to allow. ## 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 --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.solink.com/docs/install-connect-and-integrate/allow-list-urls.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.