Overview
ISS is a company that sells devices that detect if a vehicle is going the wrong way on a road. This device sends a signal via TCP to MG. MG interprets the signal and queries the device and retrieves the image associated with the signal. MG then sends the signal with the image into Manitou. The operator is supposed to verify that there is in fact a vehicle going the wrong way. If so, then the operator is supposed to 1. send an email with the device information and the image to an email address on the account, 2. forward the alarm information to an IP address setup on the account. You can have multiple devices (transmitters) on an account and they will all email and forward to the same addresses.
Manitou Data Setup
Transmitter Type
Create a transmitter type for the Wrong Way devices.
NOTE: I would make a new one instead of changing the “MEDIAGATEWAY” one like I did. Make sure it is video capable and the video type is “Still Image”.
You use the transmitter type when creating the transmitter. Set the transmitter type to the transmitter type you just created. Set the RLP to the RLP you have setup on the Bold XML FEP you have connected to the MG. Set the transmitter ID to the transmitter ID of the unit (the customer will have to get this from ISS). Set the Video Capable option.
Contact Point Types
Create a new contact point type.
This will be the address that you setup on the account to forward the alarm to after the operator has confirmed the alarm.
This is where you data enter it on the account.
You will also need a contact point type for emailing the confirmed wrong way signals. In this document, I used the “E-Mail 3” address type but you could create a contact point type specifically for this type of monitoring if the customer wants to (like “wrong way email”).
Event Code
Define an event code of “*WRGWAY”. You can set it up any way you want.
Script Message
Create a script message for the email you want to send. You can name it anything you want to.
Reverse Command
Set up a reverse command at the Monitoring Company level.
Action Patterns
Create a global Action Pattern at the Monitoring Company level using the Manitou Web Client (for some reason OWS won't let you create the action pattern the way it's supposed to be). These are the two commands that email and forward the signal. The customer may want their operators to be asked questions and only issue these commands based on if they’ve verified that there is a vehicle going the wrong way in the picture.
MediaGateway Setup
Connector
Make sure you set the connector up as a listen TCP connector. Make sure you have a No Activity time set. Make sure you set the Driver Type to be WrongWay. The customer will have to tell you which port it should listen on. The customer will have to work this out with ISS.
Data Mapping
You’ll want to set up the data map just like this. There is an attachment on this wiki that contains this data map that you can import into MG. You can use the attached WrongWaySignal.xml as a file to help data mapping.
Line Driver
Wrong Way JSON Config File
This is for controlling the port that MG uses to fetch the image when we receive an alarm. The device’s default to using port 80 but it is configurable. The config file has a default port of 80 and you can define a custom port per device by specifying the transmitter ID and an ImagePort value. MG reads this file for every Wrong Way signal it receives so there is no need to reload/restart MG to pick up the changes. There is a copy of this file on this wiki that you can use as a default.
This is the configuration file for the functionality outlined in this article:
(To download this file, right mouse click and choose "Save link as...") WrongWayConfig.json
Additional Info
If forwarding the alarm fails, MG will create a “*A” alarm on the account that is trying to be forwarded. The point ID will have information about the failure.
