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, you can process alarms that arrive from each transmitter according to a separate workflow.

To configure transmitter-specific alarm processing:

1.     On the Workflows page of the site, create a workflow

2.     In the Incoming Alarm area of the workflow editor, click the Add Condition button and set the workflow conditions as follows:

1. Alarm code: [alarm code], for example, 110
   
2. Alarm header: x-receiver is [receiver_type:property].
   

   

In the above example, x-receiver is dc09:39666064, where dc09 means we use a DC-09 receiver and 39666064 is the 'Dc09 Account' value from the corresponding site-level integration page.

3.     Configure further steps of the workflow as desired and save the workflow. All incoming alarms from this particular transmitter will be processed by this workflow.

For more details on alarm expression syntax, see https://documentation.evalink.io/talos/admin/advanced-features-in-evalink-talos/alarm-expression-syntax

---

Below you can find some other examples of receivers and what information is relevant for them.

- For a Frontel-GI receiver, you need the Frontel GI Server ID and the Account Number:

1. frontel-gi-receiver:[Frontel GI Server ID/Frontel GI Account Number]

 

- For a TNA device, you need the MAC address, written without colons:

1. tna:[MAC]
   

e.g.: tna:080064AABBCC

- For a VdS receiver, you need the VdS ID:

1. vds:[VDS ID]

e.g.: vds:97518081

• Related Articles

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

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

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

• Change the email used to log in your evalink talos tenant

  In this article we will explain how to change your email used for logging in evalink talos. Problem Description You need to change the email address you use to log in evalink talos. Solution There is no direct way for a user to change the email ...