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 Axis AVHS 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.
- Create a folder to hold the application. Typically "C:\inetpub\wwwroot\webhook"
- Unzip the WebHookPost application into this path
- Open the Web.Config file and edit the default values for the AxisSignalCache and AxisLogPath if desired. Also, create these folders if needed.

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

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

- Open a browser and navigate to the url for https://{default web site}/{alias}/avhs. 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 AxisSignalCache directory.
Media Gateway Data Mapping
Now we have to build the Media Gateway side. I would start with the Data Map. A sample file (attached) is useful for this part. Place the sample file on the server.
Here is where the sample file is useful. You can hit the ellipsis next to the label and point to the example file. You can then select the desired label from the parsed sample file.
- You will need to 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:
- event_notification/trigger/http = BA
- event_notification/device/connect = YK
- event_notification/device/disconnect = YC
- event_notification/trigger/application = BA
- event_notification/trigger/audio = BA
- event_notification/trigger/input = BA
- event_notification/trigger/pir = BA

The event code mapping listed is for all known topics coming from Axis currently. If they add more, this mapping would need to be updated.
Note that we are using the External site ID (exsiteid) and External Device ID (extdeviceid) from AVHS to create the TXID and Zone for the alarm. These MUST be set up in the AVHS portal for this to route correctly in Manitou.
Media Gateway Connector
Now we need to build the connector to pull in the files we receive from AVHS. Navigate to Universal Connector > Connector
- Hit Add and create a new File Connector called AXISAVHS
- Select the folder pointed to by the Web.Config called AxisSignalCache for the File Location
- Add ".SIG" for the File Extension

Media Gateway Line Drivers
The last piece is to configure the Line Driver to tie this all together. Navigate to the Line Drivers section.
- Add a new line by selecting the AXISAVHS connector from the first dropdown box
- Add a description (Axis AVHS)
- Choose Universal Connector for the Line Function
- Right click the Properties box and select Properties
- Set the Name = AXISAVHS
- Pick the FieldSet to the AXISAVHS data map we created
- Set the FEP that you wish to use
- Set the Receiver that was created to receive MGW signal
- Set the Line number you wish to use
- Pick the UCSEND menu

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 AxisSignalCache folder. The Media Gateway log should show it being processed and passed through to Manitou. 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.






