Reserve a Verkada intercom address through DHCP and verify its calling endpoints

Use the vendor’s regional endpoint categories to distinguish an addressing problem from a calling-function failure.

Source facts

Verkada intercoms use DHCP for addressing and network configuration. When a fixed address is needed, the vendor’s network guide directs administrators to create a DHCP reservation using the device MAC address. Intercoms use the DNS server supplied by DHCP, and the guide says DNS over HTTPS is not supported. Its firewall reference distinguishes general device communication, calling, access control, backup, and Desk Station endpoints, with region-specific requirements rather than one generic connectivity test.

Source: Verkada Help — Intercom Network Settings.

Applicability

Applies to Verkada intercom and Desk Station network requirements. Use the current endpoint table for the organization’s region; this article deliberately does not reproduce a static firewall allowlist that can become stale.

DSE recommendation

DSE recommends reserving the address through the managed DHCP service and recording the MAC-to-device mapping in inventory. Diagnose a failure by function: online status, ringing, speech, unlocking, and backup can have different dependencies. Have the network owner review the applicable regional table and scope rules to the required devices. Do not substitute a successful ping for an end-to-end calling check or broadly expose the device subnet to resolve one missing endpoint.

Verification

Verify the lease, reservation, DNS response path, and required regional destinations from the intended network. Place an approved test call and check media and door control separately. Record which function failed and the applicable endpoint category so Support receives a useful failure description rather than only an online/offline label.

Official reference

Verkada Help — Intercom Network Settings. Reviewed October 15, 2026.