evalink talos Alarm Dispatcher

Migrate from 'DC09 ARC Connection' to the 'Alarm Dispatcher' in evalink talos


In this article, we are going to describe how to migrate from DC09 ARC Connection to the Alarm Dispatcher.
The DC09 ARC Connection integration will soon be decommissioned from evalink talos. The replacement is the Alarm Dispatcher, an integrated tool allowing you to handle forwarding of alarms to different ARCs while selecting your criteria and the protocol.

In order to use the Alarm Dispatcher, go to Company > Settings > Dispatcher and click on “Add Monitoring Station”.

Fill in the Name of your New Monitoring Station and then click on “Add new Target” and give the name of the target.



 You can then click on the “Target”, select the protocol, and add the connection details (account, encryption, IP, port).

 

After, you go to your Site > Dispatcher and you click on “Create Alarm Dispatcher”.

On the left side of the screen, you can add a Default Destination – this means that all alarms will be forwarded to this particular destination.

On the right side, you can select Specific Destinations - alarms based on your criteria could be sent to another Monitoring Station (ARC).


Picture above: on the right side of the Dispatcher screen, you can select Specific destinations. For example, FIRE alarms to a specific Fire Brigade ARC while all the rest are handled by the
default destination on the left.


Click on “Choose a Monitoring Station” to select the Monitoring Station you created in the previous steps.

Obviously, you can create as many Monitoring Stations as you want and select them for your Sites. You can even select more than one targets per Site.

Whenever you finish your configuration, don’t forget to click on the Save button at the bottom of the page.


After you finish configuring the Alarm Dispatcher, head back to your Site's Integrations tab and delete the DC09 ARC Connection.

    • Related Articles

    • Different Workflows for Multiple Receivers under one Site in evalink talos

      In this article, we are going to describe how to distinguish between multiple receivers within one site and execute a different workflow for every alarm triggered by each receiver.   If several transmitters of the same type are connected to a site, ...
    • Subscribing and using evalink analytics

      Problem As an Alarm Receiving Center (ARC) administrator, I want to easily review the performance of my team and monitor my day-to-day operations. Solution evalink analytics is an add-on service that you can enable in your evalink talos tenant. It ...
    • Serial Data from Tyco MX4000 panel to evalink talos using ipTNA4i transmitter

      In this article we will describe how to interpret the serial data from a Tyco MX4000 panel in evalink talos and how to extract the useful information for further actions. The panel we have is a Tyco MX4000 which provides serial data to evalink talos. ...
    • Error "Call Error 31402 - UserMedia Acquisition Failed Error" with Twilio VoIP integration

      In this article we will explain the reason behind the error 31402 when using the Twilio VoIP integration. Problem Description When trying to make a call in talos using the Twilio VoIP integration, you get the following error: Call Error 31402 ...
    • Failed to export PDF in evalink talos

      In this article, we are going to explain how a Windows OS setting can affect the PDF export in evalink talos and how you can fix this issue. Problem description When you try to export a PDF report in evalink talos and you see a message "Failed to ...