Learn how to activate your Verkada TD52 Video Intercom in Command
Updated over a week ago
Once your intercom is connected to a PoE-enabled switch, it will automatically start to boot up:
• Power over Ethernet (PoE)/PoE+: 11.5W (IEEE 802.3af PoE)
• Extended Temperature Range: 25.5W (IEEE 802.3at PoE)
Add the intercom to Command
1.In Verkada Command, go to All Products > Add Devices.
2.Find the intercom you want to work add.
3.Enter the serial number. You can find the serial number in these places:
◦ Printed on the back of the device (just below the I/O cover on the back of the unit and on the top side of the box)
◦ The packaging
◦ The order number
Configure the intercom before mounting
If you want to update and configure TD52 before mounting it, connect the device to your network using the Ethernet port, located in the cable bay, on the back of the device.
Example: Information label located on the back of the TD52
Example: Information label (on the top side of the box)
Bring your intercom online
After entering or scanning your intercom’s serial number, here’s what you can expect:
• The camera starts transmitting video. It typically takes 3–4 minutes for the video stream to appear in Verkada Command.
• An LED above the camera indicates the status of the intercom.
• A set of white LEDs (located between the camera and the call button) indicates what stage the unit is on during the initial startup.
Create and Use Shared Call Flows
Create and Use Shared Call Flows
Learn how to configure shared call flow lists for Verkada Intercoms
Updated over a week ago
Verkada Intercom devices dial out to a preset list of receivers. This preset call flow can be tied exclusively to one intercom, or it can be shared among many. This article explains shared call flows that multiple intercoms can subscribe to.
Can modify a call flow list if the user has permissions on all associated intercoms.
Site Viewer of any site with an intercom
Can read the shared call flow from the intercom’s detail page.
Daha fazla göster
Understand how a shared call flow works with local SIP
1.Intercoms subscribed to a shared call flow list that includes a local SIP extension attempt to call the local SIP extension for their SIP account as long as it exists.
2.The intercom skips this SIP receiver if the intercom is not registered to a local SIP server, or if the extension is not known by the server the intercom is registered to.
Create a shared call flow
1.In Verkada Command, go to All Products > Intercom.
2.On the left navigation menu, click Call Flows.
3.On the Call Flows page, at the top, click Add Flow to create a new call flow.
4.At the top left (next to your call flow name), click Pencilto rename your call flow.
5.On your new call flow, under Receivers > Call List:
2.(Optional) If you need to copy configurations from another receiver list (including individual intercoms) or clear your current configuration, select Advanced.
3.(Optional) Switch between multiple different call lists in a single call flow based on a schedule. Click Enable Schedule to enable schedules.
4.(Optional) Click Add Call List to create additional call lists.
5.(Optional) Assign a call list to a day/time range, hover over a day in the scheduler, and select Create Schedule.
6.(Optional) In the Create Schedule menu, select the call list you want to apply, the time range, and the days you want it to repeat.
6.When you are finished with your call list configuration, at the top, click Intercoms and select Intercoms.
7.Select the thumbnails for the intercoms you want to add. The selected intercoms are highlighted in blue and overlaid with a checkmark.
8.When finished, click Apply to save your selections.
9.If you select intercoms that already have individual (or shared) call flows configured, on Replace Call Flow, you need to click Yes to approve the change.
Administrative tasks
Move an intercom to a different call flow
1.In Verkada Command, go to All Products > Intercom.
2.On the left navigation, click Shared Call Flow.
3.Navigate to the Call Flow you want to move the device to.
4.Go to the Intercoms tab and click Edit.
5.Select the intercom(s) you want to move and click Apply.
6.On Replace Call Flow?, click Yes.
Unlink an intercom from a call flow
1.In Verkada Command, go to All Products > Intercom.
2.On the left navigation, click Shared Call Flow.
3.Go to the Intercoms tab of your call flow list.
4.Hover over the intercom you want to unlink, and to the right of the name, click Unlink.
5.When the Unlink Intercom popup prompts, confirm you want to unlink the intercom. This resets its receiver list.
Delete a Call Flow
1.In Verkada Command, go to All Products > Intercom.
2.On the left navigation, click Shared Call Flow.
3.Check the box next to the call flow list you want to delete.
4.At the top right, click Delete.
Note: When you delete a shared call flow list, all of the intercoms that subscribed to that flow are effectively reset. Before placing a call on those intercoms, you need to reconfigure their call flow settings.
Reset a call flow list
1.In Verkada Command, go to All Products > Intercom.
2.On the left navigation, click Shared Call Flow.
3.Reset a shared call flow list (or an individual intercom’s call flow list):
1.Navigate to the Receivers tab of your call flow list.
2.Go to Advanced > Reset Call Flow to clear the list.
3.Restart from the beginning before calling again.
Intercom Teams Integration
Intercom Teams Integration
Set up CyberGate for Teams calling with your Verkada TD52 Video Intercom
2.Under Marketplace, select CyberGate SIP intercom connect to Teams.
3.Fill out the subscription form. For Number of users, input the number of intercoms you plan to have calling into Teams, not the number of Teams users.
Configure CyberGate
1.Navigate to the Azure resource you just created for CyberGate. If you have trouble finding it on your homepage, try searching for the name you defined in your subscription page.
2.Click Open Saas Account on publisher’s site.
3.Navigate to the Global settings and add your WAN IP address. You can also enable the following on the Global settings page:
1.Teams call forwarding
2.SIP trunk support
3.TLS enforcement
4.Teams call recording
Add your device(s) to CyberGate
1.Click Device > Add Device.
2.Required. On Add Device:
1.Enter Display name. This will be the caller ID for this device in Teams.
2.Toggle on Allow calls from Teams to device to enable talk down from Teams (you will need to enable this in Verkada Command as well).
Note: it is not necessary to provide an Open-door code. When you want to unlock the door, simply input any number 0–9 in the teams dialpad, as shown below.
3.When finished, click Add to save your work.
You should be navigated back to the Device page, where you can see your new device under Directly connected devices. The Authentication Username and Password are used to configure SIP settings in Verkada Command.
4.At the top of the Device page, click Download to download the PowerShell configuration script. Use this later to enable Caller ID, Talk down, and Teams Call Forwarding.
Configure your intercom(s) in Command
Run the CyberGate configuration script
Run the configuration script you downloaded from the Device menu:
• Enables Caller ID, Talk down, and Teams call forwarding.
• Add your SIP phones as receivers in your Call List
• Custom Caller ID for your Intercoms
• Unlock the door by pressing any button 1–9
• Talk down to your Intercom by dialing its extension
• SIP calls work even during a site internet outage
How it works
Step 1: Provision your Intercom as a user/phone in your SIP system
Recommendation. To do this step, we recommend that you follow the user/device provisioning instructions, supplied by your SIP provider.
Follow these general steps, as you would to add a traditional SIP phone:
1.Add your intercom as a user. (This is typically where you define the extension.)
2.Add your intercom as a device, then assign this device to the user you created in step 1. (This typically requires the device’s media access control (MAC) address, which can be found in the device settings or on the back of the device.)
Step 2: Configure your Intercom in Command
1.In Verkada Command, go to All Products > Intercom.
2.Click Settings > Call > Add Account.
3.At a minimum, fill out the Required section. Your SIP account name is used to tag events in Command, and is not sent to the SIP server. The Domain, User ID, and Password should match what you configured in step 1.
For many SIP applications, the Required section is enough information. For instance, a local PBX server may only need the information seen below.
However, if you’re using an off-premises solution, such as Zoom or RingCentral, they may provide you with an Outbound Proxy address, which you can paste in the Proxy section.
Some providers (both on and off premises) may require that you configure an Authentication Username. Zoom calls this an Authentication ID, where Cisco expects the Authentication Username to match the End User ID created in the Cisco Unified Communication Manager, and freePBX requires nothing.
Overall, different providers expect varying values in the Optional fields, and if you experience trouble configuring the correct options, contact Verkada Support for guidance.
4.Once you’ve successfully provisioned your Intercom, you should see a green checkmark under Device Settings > Call > SIP Account.
Step 3: Add your SIP phones as receivers
1.Navigate to your Intercom’s Receivers tab and examine the Call List.
2.In your Call List groups, click the plus (+) icon and select SIP Phone.
3.Enter the extension of the recipient you want to add to the call list. Alternatively, to call the intercom from your SIP devices, simply dial its extension.
Upload Audio Messages to Intercom
Upload Audio Messages to Intercom
Learn how to upload the audio messages to your Verkada Intercom
Updated over a week ago
Audio messages are a convenient way to inform people who try to enter your building.
Configure audio messages
You can upload these types of automated audio messages to your Verkada Intercom, where they can play when certain conditions are met:
• An Offline message plays when the device has no internet connection and the call button is pressed.
• A Lockdown message plays when there is an active lockdown and the call button is pressed.
• A No One Home message plays when the call list has been exhausted
You can toggle these automated messages in Verkada Command and use the default messages, record your own message, or upload your own .wav or mp3 file, up to 20 MB (about 2 minutes of audio).
You can configure all automated message types individually or globally (applies to all Intercoms in your organization).
Configure all audio message types individually
Configure an Offline message
1.In Verkada Command, go to All Products > Intercom.
2.Go to your Intercom’s Settings page > Messages.
3.Toggle on Offline.
4.On the right, click the kebab (three dots) icon.
5.When prompted, click Record or Upload (for a message).
Configure a Lockdown message
1.In Verkada Command, go to All Products > Intercom.
2.Go to your Intercom’s Settings page > Messages.
3.Toggle on Lockdown.
4.To the right of the Default message, click the kebab (three dots) icon.
5.When prompted, click Record or Upload.
6.You can also toggle on Loop Message.
Configure a No One Home message
1.In Verkada Command, go to All Products > Intercom.
2.Go to your Intercom’s Receivers Tab > Call List.
3.Toggle on No One Home Message.
4.To the right of the Default message, click the ellipsis (three dots) button. You are then prompted to select Record or Upload.
Configure messages globally
An individual Intercom plays the globally configured message if and only if it does not have a custom (non-default) message configured. After you configure a global message, you still need to toggle on the message at the individual Intercom level. Thereafter it auto-populates with the global message.
1.In Command, go to All Products > Intercom.
2.Click Settings > Automatic Messages.
3.To the right of the selected Default message, click the kebab (three dots) icon, where you can select Record Message or Upload Message. This example shows a configured global message (example.wav) for lockdowns.
4.If you toggle on Lockdown, it auto-populates with example.wav as long as no custom message has been previously configured (shown below).
.
.
to rename your call flow.
.
.
.
.
.
.
.
.
.
.
