|
How to Integrate PageGate with Spillman Video:
Welcome to the overview of how PageGate integrates with Spillman’s FLEX API.
In this tutorial, we’ll be going over how to poll data from Spillman’s FLEX API, and then process it with PageGate’s GetASCII interface and filter script.
Before we begin, this will be an overview tutorial and specific configuration steps should be referenced in PageGate’s written documentation. The documentation is available in the support section of our website and can also be found in the pg.chm file in the PageGate program directory.
The specific section you’ll want to references is How PageGate Accepts Messages – API Polling – Example: Spillman XML API. This details the exact process you will need to follow.
To review the concepts and process in the documentation, though, it works like this:
We provide a PowerShell script and service installation utility in PageGate’s documentation. This PowerShell script service polls Spillman’s FLEX API every 3 seconds for data stored in the CAD Active Call Table and Radio Status Log Table. As you can see, there are several sections of the script that you will need to provide values for, like the API credentials, address of the Spillman FLEX API and logging directory.
To note it, you will need a username and password to access the Spillman FLEX API. Those credentials are configured in Spillman and they control what data is available to request.
If the Spillman API credentials you provide can only access specific data, you may not need a filter script as you wouldn’t need to worry about polling irrelevant or non-dispatchable data.
However, if the Spillman API credentials can see all data in the tables, you will need a filter script to determine which call types should be messaged to which agencies and which call types shouldn’t.
All data returned by the Spillman API is written to the script’s folder for PageGate’s GetASCII system to process through the Filter Script system and what you want done is ultimately determined by what you need to dispatch.
To go over a few examples, you may want:
- All SEARCH and RESCUE calls to dispatch to the same group in addition to the agency actively being called on.
- Calls at specific addresses (like a school’s address) should dispatch additional resources in addition to the agency actively being called on in CAD.
- Certain agencies should receive all call types
PageGate’s filtering system is entirely capable of handling your circumstance and scenario; it’s just a matter of configuring the appropriate parameters.
Once data makes its way through the filtering system, it’s queued for immediate delivery, whether that’s direct SMS to phones, sending email, delivering through a public safety service like IamResponding, Active911 and similar, or all three.
This concludes the video tutorial on how to upgrade to PageGate version 9. For more tutorials, including how to register PageGate, please visit our website, www.notepage.net
|
