Contents
Overview
IIS Integration Configuration
Reverse Commands
Media Gateway Configuration
Event Codes and Event Mapping
Action Pattern
Overview
This document gives a look at the Manitou to RSPNDR Integration. The integration uses a web app called Integration. This will be the portal to pass information to and from RSPNDR integrated with setup In the Media Gateway via HTTP type Universal Connector. Operators can send a reverse command within an alarm that will trigger an event to be sent to the RSPNDR application. A security personnel can then choose to take the alarm within the RSPNDR app to go on to the site to verify. Messages sent back to Mantiou will include when the alarm in RSPNDR has been sent, published to the app, notes sent from RSPNDR via the website or the app, when the security personnel marks they have arrived, and when the security personnel marks that they have finished the alarm. Operators will also have the ability to send a reverse command to RSPNDR to cancel the alarm within the RSPNDR app.
Return to Contents
IIS Integration Configuration
The integration will be set up via Cloud Services. However, the customer will need to get and have available for setup the following:
- RSPNDR API Key and Secret
- The tenant ID assigned from RSPNDR
- The URL:Port for MGW
- What signal codes they want to use
Reverse Commands
There will need to be two reverse commands created under the Monitoring Station record. One reverse command will be used to send the alarm to RSPNDR. The other reverse command will be used to cancel the alarm that was sent to RSPNDR.
The reverse command to send the alarm to RSPNDR needs to look like this:
Details:
The reverse command to cancel the alarm in RSPNDR needs to look like this:
Details:
The details are the same with the exception of the Fixed Value for cancel is updated to "true". The easiest way to create this is to copy from the first reverse command to send to RSPNDR then to update the cancel to "true".
Return to Contents
Media Gateway Configuration
Data Packet
Create a Data Packet within the MG
- The address will be provided by the Cloud team based on their setup. The Packet name will need to match the Packet Value in the reverse command.
- The tenant ID will be assigned by RSPNDR
- The username and password can be coordinated with BOLD to protect the message channel. The customer can select one and let us know or we can choose it for them.
We also adjusted adding the Call List to the mapping:
- Edit the existing Data Packet if it already exists, or during initial setup, add an entry for "call_list": {19}. (not shown in the screenshot above)
- Edit that line to include “” (quotes) around the token and add a comma at the end.
- The entry should look like this: "call_list": "{19}",
- Save the changes and do a File > Reload & Restart.
Data Mapping
Create the following Data Mapping:
Return to Contents
Connectors
You will need to create two connectors. One for outgoing data and one for incoming data.
Create the following HTTP connector for outgoing data:
The outgoing HTTP connector will need to have an HTTP Header:
Create the following HTTP connector for incoming responses from RSPNDR:
Line Drivers
Two Line Drivers will need to be created. One for outgoing data and one
Incoming Line Driver:
Outgoing Line Driver:
Event Codes and Event Mapping
A series of Event Codes will need to be created for each possible response sent by RSPNDR.
"PUBLISHED": "RPBD",
"TAKEN": "RTKN",
"ARRIVED": "RARD",
"FINISHED": "RFND",
"CANCELLED": "RCND",
"NOTED": "RNTD",
"CONFIRMED": "RCFD",
"GROUNDING": "RGND",
"GROUNDED": "RGDD",
"SENT": "SENT"
The SIA codes in quotes are an example of what can be created as Event Codes. After the Event Codes are entered in Supervisor Workstation they also will need to be entered in Event Mapping for SIA. The decided-upon Event Codes will need to be noted and given to the Cloud team to update the appsetting file for RSPNDR.
Return to Contents
Action Pattern
This is an example of an Action Pattern that can be used to process a RSPNDR alarm. The initial action would be to send the reverse command to send the alarm data to RSPNDR. Once accepted in the app it will wait for a security personnel to pick up the alarm to verify on-site. A suspend action could come next while waiting for security personnel to take the alarm. If after a certain amount of time, it has not been picked up in the RSPNDR app, a call could be made to the site contact number. If the person at the site states to cancel the alarm in RSPNDR, that assistance is not needed, a reverse command can be sent to remove the alarm from the app. Otherwise, more time can be given while waiting for the alarm to be picked up in the app by security personnel.
Return to Contents
