Size a CyberGate subscription by intercoms rather than Teams recipients

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

Source facts

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.

Source: Verkada Help — Intercom Teams Integration.

Applicability

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. 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.

Verification

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.

Official reference

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