All Collections
Intercom
Intercom Network Settings
Intercom Network Settings

Learn about the required network settings for Verkada Intercoms

Updated over a week ago

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.

Note: 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).

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.

Note: 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:

  • *.amazonaws.com - TCP+UDP/443, UDP/1024 to 65535

  • *.backblazeb2.com - TCP/443

  • *.twilio.com - TCP+UDP 443, 5060, 5061

  • *.verkada.com - TCP+UDP/443, UDP/123

  • *:4100 - TCP/UDP on LAN

  • 34.216.15.26 - UDP/123

  • 35.166.49.153 - TCP+UDP/443, UDP/123

  • 168.86.128.0/18 - UDP 10000 to 60000

  • time.cloudflare.com - TCP/4460 + UDP/123

If your firewall does not allow wildcard masking, or you prefer to have the entire FQDN of the endpoint in your firewall rules, you can add the domains to your allowlist based on the region your devices are in.

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

Region: United States

Standard Verkada Endpoints

  • api.control.verkada.com - TCP+UDP/443

  • api.global-prod.control.verkada.com - TCP+UDP/443

  • api-ga.control.verkada.com - TCP+UDP 443

  • device.pyramid.verkada.com - TCP+UDP/443

  • device-nlb.verkada.com - TCP+UDP/443

  • firmware.control.verkada.com - TCP+UDP/443

  • nlb.verkada.com - TCP+UDP/443

  • update.control.verkada.com - TCP+UDP/443

  • user.pyramid.verkada.com - TCP+UDP/443

  • vconductor.global-prod.command.verkada.com - TCP+UDP/443

NTP Endpoints

  • 34.216.15.26 - UDP/123

  • 35.166.49.153 - UDP/123 + TCP+UDP/443

  • time.control.verkada.com - UDP/123

  • time.cloudflare.com - TCP/4460

  • time.cloudflare.com - UDP/123

Streaming Endpoints

  • *:4100 - TCP/UDP on LAN (only required for local streaming)

  • index.control.verkada.com - TCP+UDP/443

  • relay.control.verkada.com - TCP+UDP/443

  • relay.global-prod.control.verkada.com - TCP+UDP/443

  • *.kinesisvideo.us-west-2.amazonaws.com - TCP+UDP/443, UDP/1024 to 65535 (webrtc)

Calling Endpoints

  • 168.86.128.0/18 - UDP 10000 to 60000

  • chunderm.gll.twilio.com - TCP 443†

  • ers.twilio.com - TCP 443†

  • eventgw.twilio.com - TCP 443†

  • verkada-erik-sip.sip.twilio.com - TCP+UDP 5060, 5061

  • verkada-erik-sip.sip.us1.twilio.com - TCP+UDP 5060, 5061

  • verkada.sip.us1.twilio.com - TCP+UDP 5060, 5061

  • verkada-vinter-audio-files-prod1.s3.amazonaws.com - TCP+UDP 443

Access Control Endpoints

  • access.control.verkada.com - TCP+UDP/443

  • vcerberus.command.verkada.com - TCP+UDP/443

Cloud Backup Endpoints

  • s3.ap-southeast-2.amazonaws.com - TCP/443‡

  • s3.ca-central-1.amazonaws.com - TCP/443‡

  • s3.us-west-004.backblazeb2.com - TCP/443‡

  • s3.us-west-2.amazonaws.com - TCP/443‡

Region: Europe

Standard Verkada Endpoints

  • api.global-prod.control.verkada.com - TCP+UDP/443

  • api.prod2.control.verkada.com - TCP+UDP/443

  • api-ga.control.verkada.com - TCP+UDP 443

  • update.control.verkada.com - TCP+UDP/443

  • vconductor.global-prod.command.verkada.com - TCP+UDP/443

  • vconductor.prod2.command.verkada.com - TCP+UDP/443

NTP Endpoints

  • 35.166.49.153 - UDP/123 + TCP+UDP/443

  • time.control.verkada.com - UDP/123

  • time.cloudflare.com - TCP/4460

  • time.cloudflare.com - UDP/123

Streaming Endpoints

  • *:4100 - TCP/UDP on LAN (only required for local streaming)

  • index.prod2.control.verkada.com - TCP+UDP/443

  • relay.global-prod.control.verkada.com - TCP+UDP/443

  • relay.prod2.control.verkada.com - TCP+UDP/443

  • *.kinesisvideo.eu-west-1.amazonaws.com - TCP+UDP/443, UDP/1024 to 65535

Calling Endpoints

  • 168.86.128.0/18 - UDP 10000 to 60000

  • chunderm.gll.twilio.com - TCP 443†

  • ers.twilio.com - TCP 443†

  • eventgw.twilio.com - TCP 443†

  • verkada-prod2.sip.twilio.com - TCP+UDP 5060, 5061

  • verkada-prod2.sip.us1.twilio.com - TCP+UDP 5060, 5061

  • verkada-vinter-audio-files-prod2.s3.amazonaws.com - TCP+UDP 443

Access Control Endpoints

  • access.prod2.command.verkada.com - TCP+UDP/443

  • vcerberus.command.verkada.com - TCP+UDP/443

Cloud Backup Endpoints

  • s3.eu-central-003.backblazeb2.com - TCP/443‡

  • s3.eu-west-1.amazonaws.com - TCP/443‡

Footnotes:

†required for Desk Stations and Verkada Pass

‡required for cloud backup

Did this answer your question?