{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/reserve-a-verkada-intercom-address-through-dhcp-and-verify-its-calling-endpoints/", "item": { "id": "https://update.dsesecurity.com/updates/reserve-a-verkada-intercom-address-through-dhcp-and-verify-its-calling-endpoints/", "slug": "reserve-a-verkada-intercom-address-through-dhcp-and-verify-its-calling-endpoints", "url": "https://update.dsesecurity.com/updates/reserve-a-verkada-intercom-address-through-dhcp-and-verify-its-calling-endpoints/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/reserve-a-verkada-intercom-address-through-dhcp-and-verify-its-calling-endpoints.md", "json": "https://update.dsesecurity.com/api/v1/posts/reserve-a-verkada-intercom-address-through-dhcp-and-verify-its-calling-endpoints/" }, "title": "Reserve a Verkada intercom address through DHCP and verify its calling endpoints", "summary": "Use the vendor’s regional endpoint categories to distinguish an addressing problem from a calling-function failure.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "managed-it", "label": "Managed IT operations", "alt": "A controlled technology lifecycle progressing from assessment to approved production.", "card_url": "https://update.dsesecurity.com/assets/editorial/managed-it-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/managed-it-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "access-control", "name": "Access Control", "url": "https://update.dsesecurity.com/topic/access-control/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-15T13:31:59+00:00", "modified_at": "2026-10-15T13:36:14+00:00", "reviewed_on": "2026-10-15", "reading_minutes": 2, "word_count": 265, "potentially_affected": "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.", "primary_source": { "name": "Verkada Help — Intercom Network Settings", "url": "https://help.verkada.com/intercom/getting-started/intercom-network-settings", "published_on": null, "authority": "help.verkada.com" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

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

\n

Source facts

\n

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.

\n

Source: Verkada Help — Intercom Network Settings.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official reference

\n

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

", "content_text": "Use the vendor’s regional endpoint categories to distinguish an addressing problem from a calling-function failure.\nSource facts\nVerkada 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.\nSource: Verkada Help — Intercom Network Settings.\nApplicability\nApplies 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.\nDSE recommendation\nDSE 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.\nVerification\nVerify 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.\nOfficial reference\nVerkada Help — Intercom Network Settings. Reviewed October 15, 2026.", "content_markdown": "Use the vendor’s regional endpoint categories to distinguish an addressing problem from a calling-function failure.\n\n## Source facts\n\nVerkada 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.\n\nSource: [Verkada Help — Intercom Network Settings](https://help.verkada.com/intercom/getting-started/intercom-network-settings).\n\n## Applicability\n\nApplies 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.\n\n## DSE recommendation\n\nDSE 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.\n\n## Verification\n\nVerify 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.\n\n## Official reference\n\n[Verkada Help — Intercom Network Settings](https://help.verkada.com/intercom/getting-started/intercom-network-settings). Reviewed October 15, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/reserve-a-verkada-intercom-address-through-dhcp-and-verify-its-calling-endpoints/", "url": "https://update.dsesecurity.com/updates/reserve-a-verkada-intercom-address-through-dhcp-and-verify-its-calling-endpoints/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-15" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/reserve-a-verkada-intercom-address-through-dhcp-and-verify-its-calling-endpoints/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Reserve a Verkada intercom address through DHCP and verify its calling endpoints", "item": "https://update.dsesecurity.com/updates/reserve-a-verkada-intercom-address-through-dhcp-and-verify-its-calling-endpoints/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/reserve-a-verkada-intercom-address-through-dhcp-and-verify-its-calling-endpoints/#article", "identifier": "https://update.dsesecurity.com/updates/reserve-a-verkada-intercom-address-through-dhcp-and-verify-its-calling-endpoints/", "url": "https://update.dsesecurity.com/updates/reserve-a-verkada-intercom-address-through-dhcp-and-verify-its-calling-endpoints/", "headline": "Reserve a Verkada intercom address through DHCP and verify its calling endpoints", "description": "Use the vendor’s regional endpoint categories to distinguish an addressing problem from a calling-function failure.", "abstract": "Use the vendor’s regional endpoint categories to distinguish an addressing problem from a calling-function failure.", "articleBody": "Use the vendor’s regional endpoint categories to distinguish an addressing problem from a calling-function failure.\nSource facts\nVerkada 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.\nSource: Verkada Help — Intercom Network Settings.\nApplicability\nApplies 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.\nDSE recommendation\nDSE 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.\nVerification\nVerify 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.\nOfficial reference\nVerkada Help — Intercom Network Settings. Reviewed October 15, 2026.", "datePublished": "2026-10-15T13:31:59+00:00", "dateModified": "2026-10-15T13:36:14+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/reserve-a-verkada-intercom-address-through-dhcp-and-verify-its-calling-endpoints/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/reserve-a-verkada-intercom-address-through-dhcp-and-verify-its-calling-endpoints/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Reserve a Verkada intercom address through DHCP and verify its calling endpoints" }, "articleSection": [ "Access Control" ], "keywords": [ "Access Control", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Access Control", "url": "https://update.dsesecurity.com/topic/access-control/" } ], "wordCount": 265, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Verkada Help — Intercom Network Settings", "url": "https://help.verkada.com/intercom/getting-started/intercom-network-settings" } } ] } }