Contents
Installation Instructions
Prerequisites
The following is a list of required components that must be in place prior to the installation of the AutoDispatch Gateway 2 module.
- Manitou 2.1.0 patch 20 or greater
- .NET Core runtime version 3.1.x
- Individual Logins for each operator no duplicates or reuse of logins Installation
This application cannot be installed alongside the original AutoDispatch Gateway on the same machine.
Return to Contents
Initial Install Steps
1. Install the .NET Core runtime v3.1 and the ASP.NET Core runtime v3.1- This is not the same as .NET Framework
- .NET Core v3.1 can be obtained at these links: x64 | x86
- ASP.NET Core v3.1 can be obtained at these links: x64 | x86
To check which .NET Core runtimes are currently installed, open a command prompt and run:
dotnet --list-runtimes
If the dotnet command cannot be found, .NET Core is not installed at all.
A line starting with 'Microsoft.NETCore.App 3.1.x' indicates that the .NET Core 3.1 runtime is installed.
A line starting with 'Microsoft.AspNetCore.App 3.1.x' indicates that the ASP.NET Core 3.1 runtime is installed.
It is perfectly okay to have multiple versions of multiple runtimes installed simultaneously.
2. Copy files from the AutoDispatch2.zip file to a subdirectory of the Manitou directory. The suggested directory name is AutoDispatch2.3. Install the AutoDispatch.exe as a service
- Open an elevated Command Prompt
- Change the directory to the AutoDispatch2 subdirectory of the Manitou Directory
- Type autodispatch.exe –install and press enter
- You can verify the install of this service by going to the Windows Services and checking that Bold Automated Dispatch is listed
5. Configure the reverse commands for the specific driver. In the example below, we're configuring the ALRM reverse command for the GMS driver.
- These reverse commands need to be edited on the Monitoring Company in either MWC or OWS.
- This will vary for each driver. Refer to the Integrations chapter for the setup of the specific reverse commands required for each driver.
6. Create a new Output Device Type
- Open Supervisor Workstation
- Maintenance->Setup->Output Device Types
- Click Edit and then Add
- Choose a code and a description that is descriptive of the driver that you're installing.
- For example, if you're setting up AutoDispatch for the DC-09 driver, then use DC-09 for the code and DC-09 Device for the description.
- Click OK on the Add Output Device Type dialog
- Complete the rest of the information (from the Attribute field down) as shown below and click Save
7. Create a Reverse Channel Route
- Open Supervisor Workstation
- Maintenance->Setup->Reverse Channel Route
- Click Edit and then Add
- Choose the reverse protocol that you created earlier and provide a useful description. For example ASINC Reverse Protocol.
- Click OK on the Add Reverse Channel Route dialog.
- Complete the rest of the information (from Dealer down) as shown below and click Save
8. Create a New Service Provider Device
- Open Supervisor Workstation
- Maintenance->Setup->Service Provider Devices
- Click Edit and then Add
- Name the service provider device as appropriate for the driver you're configuring. For example, if you're configuring the ASINC driver, the ID might be ASINC and the description might be ASINC Dispatch. The Protocol should be set to Retransmission.
- Click OK on the Add Service Provider Device dialog.
- Complete the rest of the screen as shown and click Save.
- Ensure that the reverse commands you created earlier are specified correctly here. Most integrations only require the 'ALRM' reverse command, but some may use the UPD and VRFY commands as well. The ALRM reverse command will go into 'Reverse command', UPD will go into 'Follow-up Command', and VRFY will go into 'Verify Command'
- Make sure that Reverse Protocol and Reverse Route are set to the reverse protocol and reverse route you configured earlier
9. Add Auto Dispatch Gateway to the Config
- Open Supervisor Workstation
- Maintenance->Setup->Configuration
- Click Edit, then right-click on Applications under the machine AutoDispatch is installed on then Add
- Choose App Type 46 ‘Auto Dispatch Gateway’ then click OK
- Set the logger parameter to the appropriate entry
- Note that the ASINC driver will need additional parameters set. These are the same parameters that are used for ASAP to PSAP. Refer to that installation guide to get the command-line parameters (Param 1 through Param 5) if setting up ASINC.
- Click Save
- Repeat this for each system Configuration
10. Start the AutoDispatch Gateway in the MSM
11. Add a BOLDXML Receiver to each FEP
- Open Supervisor Workstation
- Maintenance->Setup->Receivers
- Click Edit, Click on the Name of the Fep, Click Add
- Choose a Receiver Type of BOLDXML
- Enter Description of Auto Dispatch
- Choose the Receiver Number you want to Assign to it and click OK
- Set Port Type to TCP/IP (Out)
- Enter the IP address of the machine the AutoDispatch Gateway is installed on.
- Enter Port 7014
- Default RLP can be used and you will need to choose a Default Transmitter
12. Add a new Contact Point Type
- Open Supervisor Workstation
- Maintenance->Setup->Contact Point Types
- Click Edit, Click Add
- Complete as shown, setting the description as appropriate for the driver you're configuring
- For example, if you're configuring the AFA driver, a description might be AFA Retransmission
- Click Save
Return to Contents
Setting up an Authority for Auto Dispatch
For each Authority that is dispatch capable- Add a Contact point on the customer of the type of contact point type you created earlier. Shown in the screenshot are three examples of AutoDispatch2 contact points for three different drivers:
- Ensure that the Output Device Type and Service Provider are set to the values you created earlier.
- Some drivers, like GMS will use the contact point to perform routing. The route ID should be set in the contact point.
