# InformaCast Integration

[Verkada Command](/command/getting-started/get-started-with-verkada-command.md) has the ability to integrate with [InformaCast](https://www.singlewire.com/) and gives you the ability to trigger a building lockdown via the traditional Command and Informacast methods, including:

* Verkada lockdown via Command
* Verkada panic buttons
* Verkada alarms
* InformaCast number via direct number dial
* InformaCast Message Template

The person in distress has several options to send an alert and lock down the doors on-premise.

***

## Integrate with InformaCast

To integrate with the InformaCast system, you can utilize the on-premise InformaCast hardware and Verkada’s hybrid-cloud physical security system to link the physical contact closure in each location with Command.

### Components

#### InformaCast Fusion Server (virtual machine or a physical server)

This is the on-premise server that relays communication to the InformaCast Cloud.

<div align="left" data-with-frame="true"><img src="/files/Bovq7GtRGIZzB44yImzy" alt=""></div>

#### Contact closure

This device physically integrates the Verkada access control system with the on-premise server.

<div align="left" data-with-frame="true"><img src="/files/DhOWbzmJy0Budhsq6UH2" alt=""></div>

#### Verkada door controller

The door controller manages the lockdown configuration on the Verkada side.

<div align="left" data-with-frame="true"><img src="/files/QiY1wJyRfgSD3fnSdgaj" alt=""></div>

#### InformaCast Cloud

From Informacast Cloud, you can configure:

* Message templates, which devices receive that message (IP speakers, digital signage, instant messaging platforms), and who receives that message.
* The integration with the contact closure, and ultimately the integration with Verkada.

<div align="left" data-with-frame="true"><img src="/files/cVkzD2jrGVXcRipIF1Fk" alt=""></div>

### Architecture

This image illustrates a high-level view of how the different components communicate with each other.

<div align="left" data-with-frame="true"><img src="/files/lnj2zdJ0Kgiwhd6FAQ7H" alt=""></div>

### Configuration

#### InformaCast Fusion Server

Refer to the [InformaCast Fusion documentation](https://support.singlewire.com/s/article/InformaCast-Fusion-Documentation). This can be either a Virtual Machine or a physical on-premise server.

#### Contact closure

Refer to the [list of supported contact closures and configuration instructions](https://www.singlewire.com/help/InformaCast/v12.0.2/advanced/cucm/index.htm#rhsyns=%20\&t=InformaCast%2FPlugin_Management%2FConfigure_Individual_Plugins%2FM2M_Plugin%2FM2M_Plugin.htm).

In this example, a Barix Barionet 50 is used as the contact closure.

Wire the Barix inputs to the auxiliary outputs on the AC41, and the Barix outputs to the auxiliary inputs on the AC41. This allows the lockdown to be initiated from either system. The image highlights the inputs on the Barix and the outputs on the AC41.

<div align="left" data-with-frame="true"><img src="/files/I1LltNCzNV9Rg0emkKHg" alt=""></div>

To configure the contact closure, set up a Simple Network Management Protocol (SNMP) trap to the InformaCast Fusion server. Refer to InformaCast documentation for detailed instructions on configuring the Barix Barionet 50 contact closure.

#### Verkada door controller

The door controller requires all the initial setup and the configuration of a lockdown via an auxiliary port. You need to [configure an input/output (I/O) scenario](/access-control/integrations-and-alerts/configure-access-control-event-alerts/emergency-lockdown.md).

#### InformaCast Cloud

The InformaCast Cloud is where all of the InformaCast configurations live. The 2 major parts of the configuration are **recipients** and **notifications**.

#### Recipients

Configure message recipients, including contact closures, IP speakers, paging systems, and email. This example focuses on the configuration of the contact closure.

<div data-with-frame="true"><img src="/files/rDtNEd5oLYbaszF8uBo2" alt=""></div>

#### Contact closures

This section is where you configure your contact closures. In this test environment, there is only one, but you could have one per location in a production environment.

{% stepper %}
{% step %}
**In the top right, click** <i class="fa-plus">:plus:</i> **to add the first contact closure.**
{% endstep %}

{% step %}
**Configure the setting for the local contact closure and click Save.**

<div align="left" data-with-frame="true"><img src="/files/s1bb4ksVLzSVRW2LxlIo" alt=""></div>
{% endstep %}

{% step %}
**Configure the input and output triggers on the contact closure, and click Save. This example shows the input, but the output is configured in the same manner.**

<div align="left" data-with-frame="true"><img src="/files/lqD97vQ6p22MIJQp63tP" alt=""></div>
{% endstep %}

{% step %}
**Configure the port ID that matches the correct input on the contact closure, the value to turn it off, the message template to send, and the recipients. Refer to the** [**Singlewire Software**](https://www.singlewire.com/) **documentation for information on how to identify the port ID for the supported contact closures.**

This message gets sent to the contact closure as well as emails to users. We will review the message template in the next section.
{% endstep %}
{% endstepper %}

#### Notifications

This portion of InformCast focuses on how the notifications appear. These examples use the message templates, where the emergency lockdown is the default message.

{% stepper %}
{% step %}
**Click Message Templates to configure the settings.**

<div align="left" data-with-frame="true"><img src="/files/sop1mZIXeRMemNbttpas" alt=""></div>
{% endstep %}

{% step %}
**You should see a list of the default InformaCast message templates. Under Details, click the pencil icon for Emergency Lockdown.**

<div align="left" data-with-frame="true"><img src="/files/ZqqlUCZgjy7jYLkJvxMH" alt=""></div>
{% endstep %}

{% step %}
**Set the subject and body of the message, audio, an incident plan, and so on.**

<div align="left" data-with-frame="true"><img src="/files/C1UtrC8xd0fLNeD82kJA" alt=""></div>
{% endstep %}

{% step %}
**Set up who should receive the message when it is triggered. This example configuration includes email, contact closure, and SMS.**

<div align="left" data-with-frame="true"><img src="/files/D8FCx6BA06z0G3FLQDFG" alt=""></div>
{% endstep %}
{% endstepper %}

### **Testing**

After you configure the notifications, you should be able to trigger a lockdown from either system. This example triggers from InformaCast. In a real deployment, you can initiate this via a phone, panic button, and so on. This example configures it in the UI and manually triggers the message template.

{% stepper %}
{% step %}
**Go to Notifications > Message Templates > Emergency Lockdown > Play.**

<div align="left" data-with-frame="true"><img src="/files/tkgaD9AKC3iXk6ZF3Gfa" alt=""></div>
{% endstep %}

{% step %}
**This triggers a lockdown to Verkada, sends emails to users, and SMS, if configured.**

<div align="left" data-with-frame="true"><img src="/files/iF8L6PL3SyFVkEOc8vzh" alt=""></div>

<div align="left" data-with-frame="true"><img src="/files/rPlOzMua1K6FrgVF7KQC" alt=""></div>
{% endstep %}

{% step %}
**You can also see the Relay status on the Enclosure and the associated lock status.**

<div align="left" data-with-frame="true"><img src="/files/qu3IyoPTGE6HTeWOTXG4" alt=""></div>
{% endstep %}

{% step %}
**You should also get an email from Verkada Command and see the lockdown banner in Verkada Command.**

<div align="left" data-with-frame="true"><img src="/files/lX257xXFttl96lY4r91m" alt=""></div>

{% hint style="info" %}
You can also trigger this in reverse from Command. When you do, Command sends the same messages to the same recipients. You can initiate a lockdown in Command using the standard methods.
{% endhint %}
{% endstep %}
{% endstepper %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.verkada.com/access-control/integrations-and-alerts/informacast-access-control-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.