7.3.8. Data Integrations¶
Data Integrations page provides functionality that integrates with and accept data from third party systems and enable special handling of some data within the recorder. For example, a generic ANI/ALI integration could be configured to receive information over serial or IP, parse it based on user specified rules and apply it to ongoing calls.
This page shows a list of the available Data Integrations, with information on which are licensed and which are enabled. You can restrict the list to just the licensed integrations with the Hide unlicensed integrations checkbox.
Fig. 7.53 Data Integrations Page¶
To configure or enable an Integration, select a licensed Data Integration from the list and click Edit Integration. This will open a page with:
Script Version: This will show the System version and the Current version of the integration script. If an integration has been configured, it is not updated when an upgrade happens, to prevent it from breaking. To bring it up-to-date, copy the Configuration file to a text editor (for reference), disable the integration, save, edit again and reconfigure based on the new configuration file.
Configuration File: This contains all variables that need to be set for the integration to work.
Integration Enabled: This checkbox turns on or off this Integration.
Some integrations also offer these options:
View Processing Logs: See how the Integration has processed the input.
View Input Logs: See the input from the CAD system.
Replay Timestamp: Copy the timestamp from the input log and enter it here to have it replay based on the current configuration setting. This allows for iterative development of the integration.
7.3.8.1. Broadcastify¶
Eventide Communications NexLog DX-Series recording systems can support streaming one or more recorded streams to a feed on https://www.broadcastify.com/ Licensing is on a per-stream basis, and a stream can contain one or more recorded resources/talkgroups. Keep in mind that in this case they will be streamed together. Please contact Eventide Communications sales for the per stream pricing. Before attempting to stream from the NexLog DX-Series to Broadcastify, a feed will need to be created on Broadcastify.com. Credentials and required details to stream to that feed will also need to be obtained. Instructions on how to establish a feed, and the terms and conditions related to streaming content to a feed are not part of this document. Please refer to the Broadcastify.com -> “Broadcast” section for further details. Administrative level knowledge of the NexLog DX-Series configuration manager and tools is assumed when using this document. If you are not familiar with the NexLog DX-Series Web Configuration Manager, please contact your local Eventide Communications dealer/reseller for assistance.
- Software, Licensing and Configuration
Once the NexLog DX-Series recorder is licensed for Broadcastify, the integration can be edited and enabled for streaming to the Broadcastify.com website.
- Licensing
Contact Eventide Communications Sales to purchase an add-on license key if your recorder is not already licensed for Broadcastify. You will need to know how many unique streams you plan to stream to Broadcastify. The license generated is on a per-stream-basis.
Log in to the Configuration Manager
Go to “System” -> “License Keys”
Click “Add Key”
In the “License Key” field, enter the add-on key provided by Eventide Communications
- Configuration of the Broadcastify stream(s)
Log in to the Configuration Manager
Go to “Recording” -> “Data Integrations”
Select “Broadcastify Integration” and click “Edit Integration”. Here you will need to configure a mount point for the Broadcastify stream. Details about the parameters to enter are shown in the screenshot below
When complete check the “Integration Enabled” box (as seen in the screenshot below) and then click the “Save” button
Fig. 7.54 Broadcastify Configuration¶
Below are descriptions of the configuration fields as seen in the above screenshot:
recorderUserName: Recorder user that has access to playback of the resource/talkgroup being recorded
recorderUserPassword: Password for the recorder user that has access to playback of the resource/talkgroup being recorded
talkgroup (i.e. resource name): Name of the resource/talkgroup being recorded that will be associated with a Broadcastify playback stream. You can add multiple resources/talkgroups to one stream. Note, if multiple resources are configured for one stream, they may transmit audio over each other and may not be audible. Multiple separately streamed resources/talkgroups must be configured with their own unique [Stream] sections of the configuration.
mount: Name of the mount where the Broadcastify playback stream can be accessed (acquired from Broadcastify)
host: Server address of the Broadcastify playback stream (acquired from Broadcastify)
port: Port to be used for the Broadcastify playback stream (acquired from Broadcastify)
password: Source client password (acquired from Broadcastify)
user: Source client username (acquired from Broadcastify)
name: Name of the Broadcastify stream for identification on the NexLog DX-Series DX server. If you configure multiple streams, then each stream should have a unique name. Refer below for details on how to configure multiple streams.
delay: This is a configuration option that sets the delay between a recording and when it will playback on a Broadcastify stream. The default and minimum delay is 30 seconds, which means that the Broadcastify playback will occur 30 seconds after the recording. This can be reconfigured to suit local requirements, though must be less than the value used for retention time of the recording/resource itself.
- Configuring Multiple Streams
You can configure a recorder to have multiple streams. Each stream requires the following:
A separate “[Stream]” section as seen in the screenshot below. The first stream in the example below is dedicated to a “Fire” talkgroup, while the second stream is dedicated to a “Police” talkgroup
Each stream should have its own unique mount as seen in the screenshot below
Each stream should have its own unique name as seen in the screenshot below
Fig. 7.55 Broadcastify Configuration Multiple Streams¶
- Configuring AGC and Gain
From software version 2020.4 onwards in the NexLog DX-Series DX-Series, Broadcastify streams can be configured to enable AGC and gain settings.
- AGC Configure
To configure AGC, follow the steps below:
Log in to the Configuration Manager
Go to “Recording” -> “Data Integrations”
Select “Broadcastify Integration” and click “Edit Integration”.
On a new line in this configuration file, add the following text: agc: 1
Save the configuration file
To disable AGC, you can either change the configuration value from 1 to 0, or you can just remove the line of the text with the AGC configuration.
- Gain Configure
To configure gain, follow the steps below:
Log in to the Configuration Manager
Go to “Recording” -> “Data Integrations”
Select “Broadcastify Integration” and click “Edit Integration”.
On a new line in this configuration file, add the following text: gain: <value of gain>
The supported gain values are: -4,-3,-2,-1,0,1,2,3,4,5 where -4 is the softest volume setting, and 5 is the highest.
Save the configuration file
To disable a gain setting, you can either set the configuration value to 0, or you can just remove the line of text with the gain configuration.
Please also keep the following two points in mind when configuring AGC or gain:
Both AGC and gain settings must be specified under a particular stream. They will apply to all talkgroups that are a part of that stream.
If both AGC and gain are specified, only AGC will get applied.
- Stream Address
Once the Broadcastify Integration Configuration File is saved, you will be able to access the Broadcastify stream by going to the address specified in the configuration file. The format of the address is:
<host>:<port>/<mount>
Based on the example in the screenshot above, the address of the mount would be:
a1.broadcastify.com:8000/dfg42yweu901
- Connectivity and Access
The most common problem when setting up Broadcastify.com streaming is connectivity between the Eventide Communications NexLog DX-Series system and the Broadcasity.com mount point. Configuring access between the NexLog DX-Series system and Broadcastify is unique to each enterprise networking environment and outside the scope of this document.
7.3.8.2. ProPhoenix CAD Integration¶
New in version 2024.1.
This integration adds all the necessary custom fields to integrate ProPhoenix Computer Aided Dispatch (CAD) into the NexLog DX-Series system.
License Required
This feature must be licensed to be used. Contact your Eventide Communications Dealer for assistance.
Once the Data Integration has been licensed and enabled, the following Fields are added to the Custom Fields menu:
FIELD NAME | GROUP NAME | FIELD TYPE | INDEXED | EDITABLE |
|---|---|---|---|---|
CAD_ADDRESS | CAD | TEXT | False | False |
CAD_AGENT | CAD | TEXT | False | False |
CAD_ARRIVAL_TIME | CAD | TEXT | False | False |
CAD_CALLNR | CAD | TEXT | False | False |
CAD_CFS | CAD | TEXT | False | False |
CAD_CFS_DESCRIPTION | CAD | TEXT | False | False |
CAD_CSZ | CAD | TEXT | False | False |
CAD_DISPATCH_TIME | CAD | TEXT | False | False |
CAD_INCIDENT_ID | CAD | TEXT | False | False |
CAD_LOCATION | CAD | TEXT | False | False |
CAD_RPTDATE | CAD | TEXT | False | False |
7.3.8.3. Tait DMR -SMS/SDS Integration¶
One of many benefits of DMR Digital two-way radios when compared to Analog radios is the ability to send text messages to just one individual or a group without switching channels.
This Data Integration allows supported systems to log SMS/SDS events.
License Required
This feature must be licensed to be used. Contact your Eventide Communications Dealer for assistance.
In the Recording -> Data Integrations Section, select the “Tait DMR REST Integration”, then click “Edit Integration”.
Changed in version 2024.1.
The following settings can be edited based on the user’s preferred DMR configurations:
doSMS: 0 or 1 to enable tagging calls with text SMS as annotations.
SMS_Pointer: a date in the format of “YYYYMMDD” to indicate how far back to start searching for SMS calls. If left empty, will start at the current time.
Fig. 7.56 Tait DMR Integration¶
Once settings have been configured, ensure Integration Enabled has been selected and click “Save”
DMR SMS and SDS events should now be recorded and visible via MediaWorks DX.
7.3.8.4. NexLog Database Fusion¶
New in version 2024.1.
Eventide Communications NexLog DX-Series has the ability to import data and tag recordings from any database system that has an accessible SQL database. For example, if your agency has a Computer Aided Dispatch(CAD) system with an accessible database, the NexLog DX-Series Database Fusion can connect the data to easily associate incidents with recordings on your recorder.
This service is configured by an Eventide Communications technician and works by checking the database for new records or incidents and consuming them on a configurable interval. In most circumstances, 911 audio can be tagged with the associated CAD incident data within 15 seconds of being entered into the CAD system. As the CAD incident develops, other information is associated to the 911 recording such as units dispatched and unit arrival times. This integration often provides more detailed and flexible data than a customized CAD integration. For example, you can choose to import data like ‘call disposition’ or ‘CAD notes’.
CAD records can be searched by agent or position to get a complete picture of all the data entered into the CAD system over a period. Researchers can easily locate the CAD record and then drill down with the new ‘Show More’ feature to locate the 911 Audio, radio, screen recordings, and other data associated with the Incident.
Additionally, the system can store CAD data unrelated to 911 calls, like automated security alarms and police-initiated events.
To use the “Eventide CAD Data Importer Service,” the following conditions must be met:
Provide a CAD replication database.
The database should be an SQL database with ODBC or MSSQL connectors.
The recorder must be able to network with the CAD replication database using the database connector port.
The recorder requires credentials to authenticate with the replication database.
The provided credentials must have access to the table or view from which the information will be retrieved.
Note
The SQL database requires a table view that matches the schema provided by Eventide Communications.
7.3.8.5. Prepared 911 Data Integration¶
New in version 2024.1.
License Required
This feature requires a Prepared911 Integration license to be used. Contact your Eventide Communications Dealer for assistance.
Prepared Live is a platform that facilitates communication and enables Public Safety Answering Points (PSAPs) to collect rich multimedia information directly from 911 callers before the arrival of any first responders. When integrated with Eventide Communications’s |NL| recording solution, dispatchers and call-takers exchange messages with a caller and collect live video, photographs, videos, and GPS location.
7.3.8.5.1. NexLog DX-Series Configuration¶
There are two parts to configuring the NexLog DX-Series recorder:
Get credentials from Prepared Live
Add configuration to the NexLog DX-Series software
To initiate the integration between Prepared Live and Eventide Communications NexLog DX-Series, customers should follow these steps:
Reach out to either their Prepared Live Customer Success Manager (CSM) or their Eventide Communications Dealer.
Request their account to contact the NexLog DX-Series dealer. It’s important to note that the integration on Eventide Communications’s end will not function unless a separate license from Eventide Communications is obtained.
After completing the necessary steps with the dealer, and upon receiving approval from either the dealer or the customer, the Prepared Live Go-to-Market (GTM) representative will proceed.
Once generated, Prepared Live will provide client_id and client_secret credentials to the CSM representative, who will then forward to the customer.
To configure the Prepared911 integration, log into NexLog DX-Series Configuration Manager, then go to Recording > Data Integrations, select Prepared911 Integration and hit the Edit Integration button.
Here you’ll select Enable Integration and add the Server, ClientId, and ClientSecret details that were provided by Prepared Live.
Note
For additional information, please contact your Eventide Communications Representative.
7.3.8.6. Motorola Premier One CAD Integration¶
New in version 2024.1.
This integration supports call tagging and data importing modes to connect your Motorola Premier One CAD system with your NexLog DX-Series recorder.
License Required
PREMIERONE CAD INTEGRATION requires a license to be used. Contact your Eventide Communications Dealer for assistance.
Once this feature is Licensed and enabled, all data field variables are listed in order to properly configure this integration, including but not limited to:
Server
Port
User
Password
Call Start Difference (the number of seconds to look ahead and behind of incident’s created time for a recorded call to attach metadata to)
Fig. 7.57 PremierOne CAD Integration¶
For more details, please contact Eventide Communication’s technical support.
7.3.8.7. Intelcan Skycom ATM Integration¶
New in version 2024.1.
The Intelcan Skycom ATM Integration establishes a connection between Eventide Communications’s NexLog DX-Series system and Intelcan’s Skycom system. This connection aids in helping air traffic controllers effectively monitor, track, and control aircraft within their assigned airspace, utilizing information such as target data, flight plans, and other essential aeronautical data.
Additionally, the system is an important utility for supervisors, who use it to oversee operations, manage settings, and configure the system as needed.
License Required
Intelcan Skycom ATM Integration requires a license to be used. Contact your Eventide Communications Dealer for assistance.
Once this feature is Licensed and enabled, you have access to configuring the CommandPort.
Fig. 7.58 Intelcan Skycom ATM Integration¶
Note
The default port is 5000 but it can be configured when enabling the integration.
For more details, please contact Eventide Communication’s technical support.