{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/size-a-cybergate-subscription-by-intercoms-rather-than-teams-recipients/", "item": { "id": "https://update.dsesecurity.com/updates/size-a-cybergate-subscription-by-intercoms-rather-than-teams-recipients/", "slug": "size-a-cybergate-subscription-by-intercoms-rather-than-teams-recipients", "url": "https://update.dsesecurity.com/updates/size-a-cybergate-subscription-by-intercoms-rather-than-teams-recipients/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/size-a-cybergate-subscription-by-intercoms-rather-than-teams-recipients.md", "json": "https://update.dsesecurity.com/api/v1/posts/size-a-cybergate-subscription-by-intercoms-rather-than-teams-recipients/" }, "title": "Size a CyberGate subscription by intercoms rather than Teams recipients", "summary": "Count source intercoms separately from Teams recipients and retain a clear mapping for gateway caller identities.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "cyber-defense", "label": "Cyber defense", "alt": "Layered glass and metal cyber-defense structure with controlled blue and gold signal paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-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:56+00:00", "modified_at": "2026-10-15T13:36:14+00:00", "reviewed_on": "2026-10-15", "reading_minutes": 2, "word_count": 262, "potentially_affected": "Applies to Verkada’s documented CyberGate-to-Teams integration. Confirm current subscription terms with the provider; this article does not quote prices or establish that a tenant already has the required service.", "dse_recommendation": "DSE recommends counting source intercoms separately from recipient users and groups before requesting licensing.", "primary_source": { "name": "Verkada Help — Intercom Teams Integration", "url": "https://help.verkada.com/intercom/configuration/intercom-teams-integration", "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": "

Count source intercoms separately from Teams recipients and retain a clear mapping for gateway caller identities.

\n

Source facts

\n

Verkada’s Teams intercom integration uses the CyberGate SIP gateway from the Microsoft marketplace. In the subscription form, the guide says the user quantity is the number of intercoms calling Teams, not the number of Teams recipients. CyberGate device credentials are used in the Command SIP account. Its device display name supplies caller ID, while the Command account name labels internal events. The documented transport is TCP or TLS; UDP does not work for this setup.

\n

Source: Verkada Help — Intercom Teams Integration.

\n

Applicability

\n

Applies to Verkada’s documented CyberGate-to-Teams integration. Confirm current subscription terms with the provider; this article does not quote prices or establish that a tenant already has the required service.

\n

DSE recommendation

\n

DSE recommends counting source intercoms separately from recipient users and groups before requesting licensing. Keep a mapping between each physical entrance, CyberGate device, and Command account to avoid misleading caller identification. Have the Teams owner approve incoming calls, forwarding, and any talk-down capability. Review the downloaded configuration script before use under the organization’s change process and keep gateway credentials in approved secret storage rather than the project worksheet.

\n

Verification

\n

Check the configured source-device count and caller ID, then place calls to one approved individual and any required multi-ring group. Verify the selected TCP/TLS path and test speech and door controls independently. Allow for documented provisioning propagation before interpreting an immediate failure as a reason to recreate the subscription.

\n

Official reference

\n

Verkada Help — Intercom Teams Integration. Reviewed October 15, 2026.

", "content_text": "Count source intercoms separately from Teams recipients and retain a clear mapping for gateway caller identities.\nSource facts\nVerkada’s Teams intercom integration uses the CyberGate SIP gateway from the Microsoft marketplace. In the subscription form, the guide says the user quantity is the number of intercoms calling Teams, not the number of Teams recipients. CyberGate device credentials are used in the Command SIP account. Its device display name supplies caller ID, while the Command account name labels internal events. The documented transport is TCP or TLS; UDP does not work for this setup.\nSource: Verkada Help — Intercom Teams Integration.\nApplicability\nApplies to Verkada’s documented CyberGate-to-Teams integration. Confirm current subscription terms with the provider; this article does not quote prices or establish that a tenant already has the required service.\nDSE recommendation\nDSE recommends counting source intercoms separately from recipient users and groups before requesting licensing. Keep a mapping between each physical entrance, CyberGate device, and Command account to avoid misleading caller identification. Have the Teams owner approve incoming calls, forwarding, and any talk-down capability. Review the downloaded configuration script before use under the organization’s change process and keep gateway credentials in approved secret storage rather than the project worksheet.\nVerification\nCheck the configured source-device count and caller ID, then place calls to one approved individual and any required multi-ring group. Verify the selected TCP/TLS path and test speech and door controls independently. Allow for documented provisioning propagation before interpreting an immediate failure as a reason to recreate the subscription.\nOfficial reference\nVerkada Help — Intercom Teams Integration. Reviewed October 15, 2026.", "content_markdown": "Count source intercoms separately from Teams recipients and retain a clear mapping for gateway caller identities.\n\n## Source facts\n\nVerkada’s Teams intercom integration uses the CyberGate SIP gateway from the Microsoft marketplace. In the subscription form, the guide says the user quantity is the number of intercoms calling Teams, not the number of Teams recipients. CyberGate device credentials are used in the Command SIP account. Its device display name supplies caller ID, while the Command account name labels internal events. The documented transport is TCP or TLS; UDP does not work for this setup.\n\nSource: [Verkada Help — Intercom Teams Integration](https://help.verkada.com/intercom/configuration/intercom-teams-integration).\n\n## Applicability\n\nApplies to Verkada’s documented CyberGate-to-Teams integration. Confirm current subscription terms with the provider; this article does not quote prices or establish that a tenant already has the required service.\n\n## DSE recommendation\n\nDSE recommends counting source intercoms separately from recipient users and groups before requesting licensing. Keep a mapping between each physical entrance, CyberGate device, and Command account to avoid misleading caller identification. Have the Teams owner approve incoming calls, forwarding, and any talk-down capability. Review the downloaded configuration script before use under the organization’s change process and keep gateway credentials in approved secret storage rather than the project worksheet.\n\n## Verification\n\nCheck the configured source-device count and caller ID, then place calls to one approved individual and any required multi-ring group. Verify the selected TCP/TLS path and test speech and door controls independently. Allow for documented provisioning propagation before interpreting an immediate failure as a reason to recreate the subscription.\n\n## Official reference\n\n[Verkada Help — Intercom Teams Integration](https://help.verkada.com/intercom/configuration/intercom-teams-integration). 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/size-a-cybergate-subscription-by-intercoms-rather-than-teams-recipients/", "url": "https://update.dsesecurity.com/updates/size-a-cybergate-subscription-by-intercoms-rather-than-teams-recipients/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-15" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/size-a-cybergate-subscription-by-intercoms-rather-than-teams-recipients/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Size a CyberGate subscription by intercoms rather than Teams recipients", "item": "https://update.dsesecurity.com/updates/size-a-cybergate-subscription-by-intercoms-rather-than-teams-recipients/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/size-a-cybergate-subscription-by-intercoms-rather-than-teams-recipients/#article", "identifier": "https://update.dsesecurity.com/updates/size-a-cybergate-subscription-by-intercoms-rather-than-teams-recipients/", "url": "https://update.dsesecurity.com/updates/size-a-cybergate-subscription-by-intercoms-rather-than-teams-recipients/", "headline": "Size a CyberGate subscription by intercoms rather than Teams recipients", "description": "Count source intercoms separately from Teams recipients and retain a clear mapping for gateway caller identities.", "abstract": "Count source intercoms separately from Teams recipients and retain a clear mapping for gateway caller identities.", "articleBody": "Count source intercoms separately from Teams recipients and retain a clear mapping for gateway caller identities.\nSource facts\nVerkada’s Teams intercom integration uses the CyberGate SIP gateway from the Microsoft marketplace. In the subscription form, the guide says the user quantity is the number of intercoms calling Teams, not the number of Teams recipients. CyberGate device credentials are used in the Command SIP account. Its device display name supplies caller ID, while the Command account name labels internal events. The documented transport is TCP or TLS; UDP does not work for this setup.\nSource: Verkada Help — Intercom Teams Integration.\nApplicability\nApplies to Verkada’s documented CyberGate-to-Teams integration. Confirm current subscription terms with the provider; this article does not quote prices or establish that a tenant already has the required service.\nDSE recommendation\nDSE recommends counting source intercoms separately from recipient users and groups before requesting licensing. Keep a mapping between each physical entrance, CyberGate device, and Command account to avoid misleading caller identification. Have the Teams owner approve incoming calls, forwarding, and any talk-down capability. Review the downloaded configuration script before use under the organization’s change process and keep gateway credentials in approved secret storage rather than the project worksheet.\nVerification\nCheck the configured source-device count and caller ID, then place calls to one approved individual and any required multi-ring group. Verify the selected TCP/TLS path and test speech and door controls independently. Allow for documented provisioning propagation before interpreting an immediate failure as a reason to recreate the subscription.\nOfficial reference\nVerkada Help — Intercom Teams Integration. Reviewed October 15, 2026.", "datePublished": "2026-10-15T13:31:56+00:00", "dateModified": "2026-10-15T13:36:14+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/size-a-cybergate-subscription-by-intercoms-rather-than-teams-recipients/" }, "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/size-a-cybergate-subscription-by-intercoms-rather-than-teams-recipients/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Size a CyberGate subscription by intercoms rather than Teams recipients" }, "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": 262, "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 Teams Integration", "url": "https://help.verkada.com/intercom/configuration/intercom-teams-integration" } } ] } }