# E911 Subnet Lookup via CSV App
If you have a Network inventory of subnets in CSV, you can use this App to identify the location of a phone based on the subnet it's connected to, and add custom data to the output for use in alerts.
You can use this for Emergency Call Alerts, to identify if the caller is onsite or remote, so that on-site staff can react appropriately.
This app compares the Subnet discovered from the Phone to a CSV list, with optional data fields adding more context for alerts or sharing data with APIs via webhooks.
# App Outputs
- result - no_phone | success | no match
- Data.type location - remote, local, or no match
- message - end user message
- provider_message - technical message
# App Configuration
- CSV File - Paste in CSV format with the following format:
- subnet,mask,anyfieldname1,customfield2,...(all headers are available as variables)
There are 2 matches - Remote or Local subnets. You can use this to identify if a phone is remote or local, and use this in an alert template to send a message to the end user about the location of the phone.
Optional Hourly CSV download
# Message field
The message field is used to render a message to the end user about the outcome of the App. You can use this to build extra context information for Location based alerts, and pull it in as a varaible to the Alert template in a rule. This is useful for providing more detail to the end user about Network specific inventory found via Subnets.
You can use any of your variables as a template to build conditional match results for the end users. For example, if you have a field called "Location" in your CSV, you can use this to build a message to the end user about the location of the phone. You can add any cusom fields, it automatically pulls from the CSV headers.
This template would evaluate to: User is on a local subnet - 1234 Main St, Anycity, Anystate
If you have a Network invenory generating CSVs on a regular basis, you can schedule an hourly download of the CSV to be used in the App.