Log InContact Support

Intercom Network Settings

Learn about the required network settings for Verkada Intercoms

This article outlines the required network settings that your Verkada Intercom needs to communicate with Verkada Command. For more information on the required network settings for other Verkada product lines see Required Network Settings.

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.

Status LED

A flashing blue status LED on the top of the intercom indicates the intercom is not communicating with Command. If you see this behavior, check that the network is set up correctly with the intercom’s requirements. If the problem persists, contact Verkada Support.

IP address

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

If you require your intercom 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).

Verkada intercoms respond to ICMP ping requests.

Domain Name System

Intercoms 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 intercom where the DNS server is on the network and the intercom communicates using UDP port 53.

DNS over HTTPS (DoH) is currently not supported.

Power

Intercoms are powered through Power over Ethernet (PoE). This means the network switch needs to provide power to the intercom, or a PoE injector needs to be utilized. For specifics on power requirements, see the Intercom datasheet.

Firewall settings

Intercoms 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 intercoms to communicate with the general required endpoints.

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

Mandatory:

LiveKit enables high quality, low latency video and audio streaming with Verkada intercoms.

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

Your region is selected when you create an organization in Command.

Standard Verkada Endpoints

NTP Endpoints

Streaming Endpoints

Calling Endpoints

Access Control Endpoints

Cloud Backup Endpoints

Desk Station Endpoints

Footnotes:

†required for Desk Stations and Verkada Pass

‡required for cloud backup

Use the Verkada Network Tester to verify your devices can connect to Verkada Command. Select your region and the Intercom product type to run the check.

The following endpoints must be allowed on your network for the test to work:

  • speed.cloudflare.com

  • network-tester.support.verkada.com

Revisions

September 2024:

  • Added LiveKit endpoints for high-quality video and audio streams.

Last updated

Was this helpful?