Manitou Core - YourSix Setup and Configuration

Installing WebHookPost

The first piece that needs to be set up and configured is the tool used to listen for the POST coming from the YourSix system. This is called internally the WebHookPost but can be called anything we like on the IIS server. This should be installed on a machine with IIS that is externally accessible.

  1. Create a folder to hold the application. Typically "C:\inetpub\wwwroot\webhook".
  2. Unzip the WebHookPost application (WebHookPost-CI-1.0.0.10251.zip ) into this path.
  3. Open the Web.Config file and edit the default values for the "Y6SignalCache" and "Y6LogPath" if desired. Also, create these folders if needed.

image-1666303063254.png

  1. In IIS, add application to the site you wish this to live under. Typically "Default Web Site"

  1. Provide whatever alias you like the path to be called. This is part of the URL that would be given to the YourSix system to know how to send the POST to Manitou.
  2. Set the Physical Path to point to the folder created in Step 1.

  1. Open a browser and navigate to the URL for https://{default web site}/{alias}/y6signal. You should get the following message if it is all configured correctly. Now any POSTS to that same URL should result in a JSON file being created in the Y6SignalCache directory.

image-1666303180778.png

Media Gateway Data Mapping


We have to build the Media Gateway side. Start with the Data Map. A sample file (YourSix-10620221714824.sig) is useful for this part. Place the sample file on the server.

  1. Navigate to the Universal Connector > Data Mapping form
  2. Add a new one called Y6DATAMAP
  3. Set the Mapping Type to XML/JSON
  4. Under the formatting section set the Signal type = signal and the Event Type = SIA
  5. Set the Packet Root Node = root
  6. Set the Signal Root Node = root\signals
  7. Add the following fields as shown below:

image-1666303254240.png

Here is where the sample file is useful.

  1. Click the ellipsis next to the label and point to the example file.
  2. Select the desired label from the parsed sample file.
    The event code mapping listed is for all known topics coming from YourSix currently. If they add more, this mapping would need to be updated.
  3. Add the "Replace" Field Mapping Method for the topic field. (Ellipsis to the far right) These are what become different event codes. We suggest using the following as defaults:
  4. Note that we are using the CentralStationAccount from YourSix to create the TXID, the groupDescription to create the Area, and the Device Name to create the Zone for the alarm. These MUST be set up in the YourSix portal for this to route correctly in Manitou.
image-1666303297166.png

Media Gateway Connector

We need to build the connector to pull in the files we receive from YourSix. Navigate to Universal Connector > Connector

  1. Click Add and create a new File Connector called Y6
  2. Select the folder pointed to by the Web.Config called Y6SignalCache for the File Location
  3. Add ".SIG" for the File Extension

    image-1666303463933.png


Media Gateway Line Drivers

The last piece is to configure the Line Driver to tie this all together. Navigate to the Line Drivers section.

  1. Add a new line by selecting the Y6 connector from the first dropdown box
  2. Add a description (YourSix)
  3. Choose Universal Connector for the Line Function
  4. Right-click the Properties box and select Properties
    1. Set the Name = YOURSIX
    2. Pick the FieldSet to the Y6DATAMAP we created
    3. Set the FEP that you wish to use
    4. Set the Receiver that was created to receive MGW signal
    5. Set the Line number you wish to use
    6. Pick the UCSEND menu

      image-1666303488490.png

You are now done setting up the Media Gateway. Save and if needed "Re-load & Restart all Devices".

Initial Testing

Initial testing can be done by copying/pasting the example file into the Y6SignalCache folder. The Media Gateway log should show it being processed and passed through to Manitou. You can look at the Raw Data Log to make sure it gets received correctly. It will likely end up in the default system account but should create an alarm.


Was this article helpful?
Thank you for your feedback!
User Icon

Thank you! Your comment has been submitted for approval.