Use Mark43 CAD with
PageGate
Send Text and SMS Messages through Mark43 CAD
PageGate can receive alerts from Mark43 CAD by using PageGate's Mark43 API poller in conjunction with the GetASCII module. In this writeup, we'll be discussing what the PageGate Filter Pack can bring to the table for these integrations as well.
One key component of this implementation is understanding what you want done with the data you get from CAD.
Do you want every notification or call type to go to every district?
Should only certain agency codes receive messages?
Understanding the answers to questions like these is key to knowing whether you can benefit from PageGate's advanced filtering system.
Step 1: Create a directory for the script to reside in
1) Contact NotePage Support to request a copy of the Mark43 API poller library, which will include an install script, a remove script and the poller script itself.
2) After receiving the archive, in Windows on the PageGate server, create a new directory for the script to reside in.
Example: C:\PageGateData\Mark43\
3) Unzip the archive Mark43 poller zip file in to that folder.
4) Open your preferred text editor (Notepad, Wordpad, EditPad, NotePad++, etc)
5) Copy and paste the Mark43 API Powershell Script in to your new, blank document.
6) Modify $WorkingDir to reflect the path you created in step 1.
Example: $WorkingDir = "C:\PageGateData\Mark43\"
7) Modify $RequestUri to reflect the IP address and port of your Mark43 API host.
Example: $RequestUri = "https://Enter the Mark43 host here/partnerships/api/external/cad/events/active?include_unit_status_history_data"
8) Modify $Base64Credentials to reflect what Mark43 provided for access.
9) Modify $LogFile to reflect the path you created in step 1.
Example: $LogFile = "c:\PageGateData\Mark43\CADPollerLog.txt"
10) Save the file as pollmark43.ps1 in the directory you created in step 1.
Example: c:\PageGateData\Mark43\pollmark43.ps1
Step 2: Create an Event Log source for the script
1) Run Powershell as administrator.
2) Type the following and hit enter:
New-EventLog -LogName Application -Source "PageGateMark43Poller"
3) Close Powershell.
Step 3: Create a Windows Service for the script
1) There are a few service manager utilities you could use but we recommend using NSSM https://nssm.cc/download. Unzip the nssm-verzion.zip file in to your script's directory.
Example: c:\PageGateData\Mark43\nssm-2.24\
2) Open your preferred text editor (Notepad, Wordpad, EditPad, NotePad++, etc)
3) Copy and paste the Mark43 to PageGate Service Installation Script in to your new, blank document.
4) Modify $NssmPath to reflect the directory you unzipped NSSM to.
Example: $NssmPath = "c:\PageGateData\Mark43\nssm-2.24\win64\"
5) Modify $PsPath to point to the pollMark43.ps1 script you created above.
Example: $PsPath = "c:\PageGateData\Mark43\pollMark43.ps1"
6) Save the file as install.ps1 in the directory the script resides in.
Example: c:\PageGateData\Mark43\
7) Run Powershell as administrator.
8) Change directory in to the folder the script resides in.
Example: c:\PageGateData\Mark43\
9) Type the following and hit enter:
.\install.ps1
10) Close Powershell.
11) Open the Services list in Windows.
12) Go in to the properties of the PageGateMark43Poller service.
13) Select the 'Log On' tab
14) Specify a service account with permission to run powershell scripts. A normal user account is usually sufficient but this user must have logged in to Windows and run Microsoft Edge or the Internet Explorer at least once.
15) Start the PageGateMark43Poller service.
NOTE: To remove the script, use the Mark43 to PageGate service removal script.
Step 4: Configure GetAscii
This part of the configuration will be determined by what you want to do with the data retrieved from Mark43's API.
•Basic Implementation (see documentation)
In the most basic configuration, PageGate will match the value in to its recipients and groups list, allowing any call to that agency to go through regardless of incident type or nature code used.
•Implementation with filtering (see documentation)
With PageGate's filter pack, you have the ability to determine what dispatches should trigger outbound messages by keying off of any data returned by the API.
Examples of what you can do with filtering:
•Specify which notification types an agency should receive
•Determine whether additional assets should be messaged based on address and notification type
•Restrict certain notification types to only go to specific agencies or assets
|
