IP Device Configuration

You can integrate OneAlert with a variety of IP devices, such as scrolling LED signs, IP speakers, strobes, and access control devices.

Intrado partners with a number of hardware manufacturers who make these different products, and they are all certified to work with OneAlert. You can see a complete list of Certified Endpoint Partners on our website.

Once you add the device to your network, OneAlert registers it as an IP Device and is aware of its capabilities. Once registered, OneAlert automatically creates default configurations for each capability.

View all your registered IP devices at Configuration > Other Devices > IP Device, and select the IP Devices tab.

  • Triggers — If the device has contact closures, which may support buttons or sliders, OneAlert creates a trigger for the device.

    You assign this device as the trigger when creating a notification, therefore, when someone comes by and pushes the button, adjusts the slider, or activates whatever mechanism that causes contact closure, the associated notification is activated.

    You can also assign location information to the device so that if it is used to activate a notification, you can provide the location in the notification.

    View all your recognized IP devices that can be triggers at Configuration > Other Devices > IP Device, and select the Actions tab.

  • Endpoints — For example, if the device is a speaker that can receive audio and scroll text when it receives a notification, OneAlert creates an endpoint for the device. This allows you to customize the configuration of the device, such as volume settings (default, minimum, or maximum), or how fast or slow you want the text to scroll across the screen.

    View all your recognized IP devices that can be endpoints at Configuration > Endpoints, and select the Endpoint List tab.

  • Dual-use — Some devices can be both an endpoint and trigger. For example, an IP Speaker can receive notifications (endpoint) and also be used to activate a notification (trigger) because OneAlert also detected that the device has contact closures.

    Therefore, OneAlert creates any triggers and endpoints that are associated with that device.

Configuring your IP devices video linkConfiguring Your IP Devices to work with Revolution2:13

After connecting an IP device to your network, it receives its IP Address from a Dynamic Host Configuration Protocol (DHCP). At this point it will auto-register to OneAlert via the DHCP Option 72 WWW server value. See DHCP option 72 for more information.

Note: If your IP device has stopped working properly, first reboot the device to force re-registration with OneAlert. If that does not work, you should upgrade the device to the latest firmware.

You can set up notifications to be triggered by an IP device. There are many types of IP devices, including buttons, strobes, and Paging Relays.

IP devices can trigger (or activate) notifications, such as panic buttons and sensors.

For example, I'm a small business owner and am not always in the front of my store. I want to make sure I know when a customer has entered. So, I have a "Customer Entered" notification set up that plays a simple chime whenever the door to my business opens. This is accomplished by setting up a sensor at the door of my business. When the door opens, the sensor is triggered, which then triggers my notification to play the chime.

See the Stored Audio Notification example.

To add an IP device as a trigger when creating or editing a notification:

  1. Go to the Select Triggers section.

  2. For Activator, select IP Device and search for a specific device.

    Select Triggers pane shows all IP Devices

You can set up notifications to be sent to endpoints that are IP devices, such as IP speakers and signs.

You can view them by going to Configuration > Endpoints, and selecting the Endpoint List tab.

To add an IP device as an endpoint to your notification:

  1. Go to the Select Endpoint & Contact Selection section.

  2. Select your IP device from the Endpoints tab or narrow down the selection in the System Tags tab, for example using groups such as Manufacturer or Model.

See the topic Configuring Endpoints for more information.

From the IP Devices page, you can manage many aspects of your IP devices. Access the page by selecting Configuration > Other Devices > IP Device.

  • IP Devices tab — Review all IP devices recognized by OneAlert.

    IP Devices tab

    Action Description
    1 Bulk Deleting IP Devices
    2 Filter the list of devices.
    3 Open the IP Address of the device to access the device settings directly.
    4

    View a modal window of the device settings.

    Rebooting an IP device.

    For Paging Relays, configure them reach additional multicast networks or networks that are not using standard 254 device CIDR setup (Classless Inter-Domain Routing). See the Paging Relays topic.
    5 Delete a single IP device.

  • Actions tab — Review all IP devices that can be used as triggers to notifications.

    IP Device Actions tab

    Action Description
    1

    Bulk Updating IP Device Action Properties

    Importing IP Device Action Properties from CSV

    2 Downloading IP Device Action Properties to CSV
    3 Refresh the list of actions
    4

    Filter the list of actions
    5 Edit the action properties in a new window. See Editing IP Device Details.

  • Settings tab — Control various settings related to IP devices.

    • General Settings

      • IP Device Polling Interval — Define how often you want OneAlert to poll for new IP devices and update the list of devices displayed on the IP Device page.

        Note: Polling does not remove inactivate or retired devices.

      • IP Request Timeout — If your network is slow, you may want to allow more time for OneAlert to connect with speakers. The default setting is 5 seconds.

    • Advanced Settings — Most customers will never need to adjust these settings. We recommend using the default settings unless you are trying to reach large numbers of endpoints (several thousands) in as short a time as possible. Adjusting these settings allows OneAlert more time to connect to endpoints to send notifications.

      • Device Authentication Credentials —

      • Rate Limit Count and Rate Limit Time – Adjusting these settings allows OneAlert more time to connect to endpoints to send notifications. The default settings are 150 and 500, respectively.

        Most customers will never need to adjust these settings. We recommend using the default settings unless you are trying to reach large numbers of endpoints (several thousands) in as short a time as possible.

        The settings work like this:

        within x amount of time, process n number of notifications to endpoints

        where x=Rate Limit Time and n=Rate Limit Count.

        Less rate time / higher rate count – decreases the chances of OneAlert connecting to all assigned endpoints within the given time frame.

        More rate time / lower rate count – increases the chances of OneAlert connecting to all endpoints within the given time frame.

From the IP Devices page, you can delete active or inactive devices. See Decommissioned Hardware for more information about inactive devices.

  1. (optional) If deleting an inactive device, once you have removed the device wait for the Revolution system heartbeat (minimum 3 minutes) so the device registers as inactive.
  2. Go to Configuration > Other Devices > IP Device.
  3. (optional) Filter the list to narrow down the devices shown.
  4. Select the Edit icon Edit icon then Bulk Delete.
  5. Do one of the following:
    • Select the header check box to select all devices in filter results.
    • Select the check box for individual devices.
  6. Select Delete Selected.

Once OneAlert registers your devices, you can further edit information about each device.

  1. Go to Configuration > Other Devices > IP Device.

  2. Select the Actions tab.

  3. Filter (Filter icon) for the IP Device you want to edit.

  4. Select the IP Device Name to open the General Settings page for the device.

    • Name – Change the name OneAlert uses to identify your device. By default, OneAlert uses information provided by the device to uniquely identify it. You can change this name to be more descriptive for your environment. You will see this name on this page and when selecting triggers for your notifications.

      Renaming an IP Device: Configuration > Other Devices > IP Device; Filter for and Edit device; Name field.

      Note: Each Paging Relay has a GPI, GPO (Relay), and Line Out. GPI is a trigger; Relays and Line Outs are endpoints. You can only change the name of GPIs.

    • For Available in All Sites:

      • Enable to ensure all your site locations have access.
      • Disable and select a Site to limit which site has access.

    • Activate On – Set the activation rule for the IP Device; will it trigger when opened, closed, or both.

      Setting activation rule for an IP Device: Configuration > Other Devices > IP Device; Filter for and Edit device; Activate On field.

      For example, assume you have several emergency alert stations around your college campus and that each station has a panic button and an IP speaker. You could create a high-priority notification called Panic Alert that sends a message to your security phones and sends an audio file to the IP speaker announcing that "Security is on the way". In this case, you need to decide if you want the IP device to trigger when the panic button is pushed down (pin closed) or when the panic button is released (pin open).

    • Location – Enter a name for the location.

      This value is used for the source.location text variable in notifications.

    • Location Map – Use the map to select the latitude and longitude of the device.

      Setting location information for an IP Device: Configuration > Other Devices > IP Device; Filter for and Edit device; use the Location field and Location Map.

      1. Enter a Location – Use this to narrow down the map.

      2. Drop Pin – Select this to place a movable pin at the center of the map, which you can move to refine the location.

      As you move the Pin around, the Latitude and Longitude boxes will adjust. You will need to manually enter any Elevation data.

      OneAlert uses this location information in many ways, including as text variable data within your notifications (source.latitude, source.longitude, and source.elevation), to set various area restrictions, and passed to outgoing webhooks. See Create your sites for additional information about how OneAlert collects location information from endpoints.

You can download a CSV file of your IP Device action properties for your own records or to edit and reimport into OneAlert.

  1. Go to the Actions tab.

  2. (optional) Filter the list of IP device actions to narrow down the list to include only those devices you want to capture in the CSV. If you do not filter the list, you will download information from all IP devices.

  3. Select the download icon.

  4. In the resulting dialog box, specify the name and location for saving your CSV file.

You can edit IP device action properties by importing a CSV file.

It is suggested that you download action property information from OneAlert to create your base CSV file. See Downloading IP Device Action Properties to CSV.

Note: Do not edit the Action Urn column, as that is how you will match your edited data to the information in OneAlert.

You can use headers within your CSV file to assist in the import, as OneAlert will attempt to match column headers to properties.

The values you select from the CSV will overwrite any existing data.

  1. Create a new, or edit an exported, CSV file containing information to add to existing actions.

    CSV Formatting Rules

    • Header — (optional) You may include a header that defines the data order.

      The header values must match the built-in fields, which are:

      Name, ActionUrn, IPAddress, MAC, ActivateOn, Location, Latitude, Longitude, Elevation

      Note that the UI drop-down values are in a more user-readable form, for example different capitalization and spaces.

      If you do not include a header, you will still be able to match the data to one of the built-in fields.

      Note: OneAlert will restrict any changes to IPAddress or MAC.

    • Required Columns — The CSV must include at least two columns.

      One column that identifies what you want to match the data to, which must be Action Urn.

      A second column containing another property data.

    • The CSV can include any additional columns, including any information you may not want to import, as you can ignore the information during import.

  2. From the Actions tab, select the Bulk Edit icon then Bulk Update from CSV.
  3. Use Choose File to load your CSV file.
  4. The Column Mapping window allows you to define how the columns of the CSV should be used. It will only show the first 10 rows of your table to assist you in the import.
    1. For Match Data to, select Action Urn to match the information you have in your CSV.
    2. Use the drop-down of the column selectors to define which property the column defines, or whether you want to ignore the column.
    3. Select Import.

You can edit IP device action properties in a single view and submit them all at once.

  1. (optional) Filter the list of actions to narrow down the entries you want to edit.

  2. Select the Bulk Edit icon and then Bulk Edit Properties.

  3. For each action, you can edit the following properties:

    Name, Activate On, Location, Latitude, Longitude, and Elevation

  4. Select Apply Changes to finalize your edits.

Go to Global Settings and select IP Device to set the following behavior:

  • IP Device Inactive Interval — By default, OneAlert checks every 15 minutes for IP device heartbeats. When OneAlert does not receive a heartbeat, it changes the status of the device to inactive.

Should the IP device become unregistered, you can reboot it from the IP Devices page. For example, if the status column shows Unknown.

  1. Go to Configuration > Other Devices > IP Device.
  2. Find your Device.
  3. Select Settings Settings Icon to view details about the device.
  4. Select Reboot.

For some older devices, you may need to reboot them from the device interface. Refer to the device documentation for instructions.

When a device is no longer used, follow the steps in the Decommissioned Hardware topic for the type of IP device.

Once you have retired the device, OneAlert removes it from any notifications it is assigned to.

You can instruct OneAlert to immediately refresh all the IP device information.

  1. Go to Status > System Status.

  2. Expand the IP Devices Module.

  3. Select Refresh.

Note: An empty ipspeaker.xml file is provided for your convenience. Consult your speaker manufacturer's documentation on how to configure the file. Typically, this file is used to configure your speaker clock.

  1. Log in to the OneAlert server.
  2. Open Windows IIS Manager.
  3. In the Connections pane, expand your local host > Sites.
  4. Right-click on UnifiedGui and select Add Virtual Directory.
  5. Enter IPspeaker as the Alias.
  6. For Physical path, create or select an existing folder for the ipspeaker.xml file and click OK.

    7. Tip: We recommend creating a new folder in c:\Program Files (x86)\Syn-Apps called IPspeakers. Browse to c:\Program Files (x86)\Syn-Apps, then click Make New Folder > type IPspeaker > select OK.

  7. Open File Explorer and put a copy of your ipspeaker.xml file for your legacy IP speakers into the c:\Program Files (x86)\Syn-Apps\IPspeakers folder you just created. Consult your speaker documentation to find out where the ipspeaker.xml file is stored.

    8. Add virtual directory dialog box

  8. Verify the ipspeaker.xml file is present.

    Browse to http://<IP address>/<folder name>/ipspeaker.xml

    where <IP address> is your OneAlert IP address and <folder name> is the name of the folder where you copied the ipspeaker.xml file to (IPspeaker for our example).

  9. Download the ipspeaker.xml file and verify its contents are correct. This also verifies the speaker will be able to download the XML file.