> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/sound-systems/getting-started/sound-systems-network-settings.md).

# Sound Systems Network Settings

Learn about the required network settings for Verkada Sound Systems devices

This article outlines the required network settings that your Verkada Sound Systems devices need to communicate with [Verkada Command](/command/getting-started/get-started-with-verkada-command.md). For more information on the required network settings for other Verkada product lines, see [Required Network Settings](/command/need-help/required-network-settings.md).

{% hint style="warning" %}
Verkada devices are incompatible with LANs that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Verkada Command.
{% endhint %}

### Status LED

#### Network Speakers

{% hint style="warning" %}
The LED on Sound Systems network speakers will turn off after a few minutes of normal operation. 
{% endhint %}

Sound Systems network speakers, such as the NS151, NS261, and NS631, have a status LED on the front. When the speaker detects a network error, the LED flashes a code that indicates why it cannot connect to Verkada servers.

When the speaker successfully connects to Verkada servers, the LED turns solid blue for a few minutes. If the speaker detects no network errors during this time, the LED turns off.

For information about specific network error codes, see the device's [install guide](https://www.verkada.com/docs/?search=network+speaker\&products=soundSystems\&type=setupGuide).

### IP address

Sound Systems devices must be assigned an IPv4 address to communicate on the LAN and to Verkada Command. Sound Systems devices use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations.

If you require your Sound Systems device to have a specific IP address, create a DHCP reservation using the device's Media Access Control (MAC) address (found on the device's label).

### Domain Name System

Sound Systems devices use the DNS server to resolve Verkada's fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the Sound Systems device where the DNS server is on the network and the device communicates using UDP port 53.

{% hint style="warning" %}
DNS over HTTPS (DoH) is currently not supported.
{% endhint %}

### Power

{% hint style="info" %}
The NP21 and NP81 network audio players can be powered over AC. This is the recommended power option for these devices.
{% endhint %}

Sound Systems devices are powered through Power over Ethernet (PoE). This means the network switch needs to provide power to the Sound Systems device, or a PoE injector needs to be utilized. For specifics on power requirements, see the [Sound Systems datasheet](https://docs.verkada.com/docs/network-speakers-overview.pdf).

### Firewall settings

Sound Systems devices require access to many endpoints to ensure they can communicate with Command and all features will be accessible. Many customers may want to allow the Sound Systems devices to communicate with the general required endpoints.

These are the general domains to allow, **applicable for all organization-regions**:

| Domain/IP           | Protocol/Port |
| ------------------- | ------------- |
| \*.verkada.com      | TCP/UDP:443   |
| time.cloudflare.com | UDP:123       |
| \*.amazonaws.com    | TCP/UDP:443   |

If you prefer a more granular allowlist, you can add both IP addresses and full FQDNs to your firewall rules based on the region where your devices are located.

{% hint style="warning" %}
Your region is selected when you [create an organization](/command/getting-started/get-started-with-verkada-command.md) in Command.
{% endhint %}

{% tabs %}
{% tab title="United States" %}
**Standard Verkada Endpoints**

<table><thead><tr><th width="396">Domain/IP</th><th>Protocol/Port</th></tr></thead><tbody><tr><td>api.control.verkada.com</td><td>TCP/UDP:443</td></tr><tr><td>api.prod1.control.verkada.com</td><td>TCP/UDP:443</td></tr><tr><td>api.global-prod.control.verkada.com</td><td>TCP/UDP:443</td></tr><tr><td>api.prod-us-ohio.control.verkada.com</td><td>TCP/UDP:443</td></tr><tr><td>relay.control.verkada.com</td><td>TCP/UDP:443</td></tr><tr><td>relay.prod1.control.verkada.com</td><td>TCP/UDP:443</td></tr><tr><td>relay.global-prod.control.verkada.com</td><td>TCP/UDP:443</td></tr><tr><td>relay.prod-us-ohio.control.verkada.com</td><td>TCP/UDP:443</td></tr><tr><td>vpava.prod1.verkada.com</td><td>TCP/UDP:443</td></tr><tr><td>vpava.prod-us-ohio.verkada.com</td><td>TCP/UDP:443</td></tr><tr><td>vpava-moq.prod1.verkada.com</td><td>TCP/UDP:443</td></tr><tr><td>vpava-moq.prod-us-ohio.verkada.com</td><td>TCP/UDP:443</td></tr><tr><td>verkada-vpava-media-prod1.s3.us-west-2.amazonaws.com</td><td>TCP/UDP:443</td></tr><tr><td>verkada-vpava-media-prod-us-ohio.s3.us-east-2.amazonaws.com</td><td>TCP/UDP:443</td></tr><tr><td>time.cloudflare.com</td><td>UDP:123</td></tr></tbody></table>
{% endtab %}

{% tab title="Europe" %}
**Standard Verkada Endpoints**

| Domain/IP                                            | Protocol/Port |
| ---------------------------------------------------- | ------------- |
| api.prod2.control.verkada.com                        | TCP/UDP:443   |
| api.global-prod.control.verkada.com                  | TCP/UDP:443   |
| relay.prod2.control.verkada.com                      | TCP/UDP:443   |
| relay.global-prod.control.verkada.com                | TCP/UDP:443   |
| vpava.prod2.verkada.com                              | TCP/UDP:443   |
| vpava-moq.prod2.verkada.com                          | TCP/UDP:443   |
| verkada-vpava-media-prod2.s3.eu-west-1.amazonaws.com | TCP/UDP:443   |
| time.cloudflare.com                                  | UDP:123       |
| {% endtab %}                                         |               |

{% tab title="Australia" %}
**Standard Verkada Endpoints**

<table><thead><tr><th width="399">Domain/IP</th><th>Protocol/Port</th></tr></thead><tbody><tr><td>api.prod-ap-syd.control.verkada.com</td><td>TCP/UDP:443</td></tr><tr><td>api.global-prod.control.verkada.com</td><td>TCP/UDP:443</td></tr><tr><td>relay.prod-ap-syd.control.verkada.com</td><td>TCP/UDP:443</td></tr><tr><td>relay.global-prod.control.verkada.com</td><td>TCP/UDP:443</td></tr><tr><td>vpava.prod-ap-syd.verkada.com</td><td>TCP/UDP:443</td></tr><tr><td>vpava-moq.prod-ap-syd.verkada.com</td><td>TCP/UDP:443</td></tr><tr><td>verkada-vpava-media-prod-ap-syd.s3.ap-southeast-2.amazonaws.com</td><td>TCP/UDP:443</td></tr><tr><td>time.cloudflare.com</td><td>UDP:123</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

***

## Third-party music provider network requirements

### Soundtrack network requirements

Sound Systems devices streaming music from Soundtrack must adhere to [Soundtrack's firewall requirements](https://help.soundtrack.io/hc/en-us/articles/115002592192-Firewall-settings) and [network settings](https://help.soundtrack.io/hc/en-us/articles/115002592212-Network-settings). Soundtrack cannot provide a complete list of hostnames for firewall configuration. For more information, see [Soundtrack's technical requirements page](https://help.soundtrack.io/hc/en-us/sections/115000567232-Technical-Requirements).

### Spotify network requirements

Sound Systems devices using Spotify Connect must be able to reach Spotify's servers. Spotify cannot provide a list of hostnames or IP addresses for firewall configuration, so allow outbound traffic from your Sound Systems devices on TCP:443 and exclude them from any proxy or web filtering. For more information, see [Spotify Connect](https://support.spotify.com/us/article/spotify-connect/).

### Local Area Network requirements

Sound Systems devices stream audio directly to each other over your local area network (LAN) using IPv6 link-local multicast. Devices automatically assign their own IPv6 link-local addresses, so you don't need to configure IPv6 addressing or routing. However, you *must* allow IPv6 traffic between devices on the same network segment.

{% hint style="danger" %}
Verkada Sound Systems devices do not support networks with Multicast Listener Discovery (MLD) Snooping enabled.
{% endhint %}

| Domain/IP                                                                    | Protocol/Port |
| ---------------------------------------------------------------------------- | ------------- |
| <p>224.0.0.251 </p><p><strong>Note:</strong> This is a multicast address</p> | UDP:5353      |
| (Device IP address)                                                          | TCP:7001-7024 |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/sound-systems/getting-started/sound-systems-network-settings.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.