Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry AtHoc
  3. BlackBerry AtHoc Integrations
  4. IIM Release Notes
  5. New in Release 6.1.x

New in Release 6.1.x

6.1.0.x – DISA – July 2025

Overview
BlackBerry AtHoc
 interfaces with both indoor and outdoor Giant Voice (GV) warning systems via the IP Integration Module (IIM), enabling effective dissemination of wide-area Mass Notification System (MNS) alerts. GV systems convey critical information using audio broadcasts, including prerecorded messages, audible tones, and text-to-speech (TTS) messages. Typically, large outdoor speakers are mounted on poles in geo-directional arrays to ensure that emergency messages override ambient noise within designated coverage areas. Once integrated with a GV system, the IIM enables operators to transmit emergency alerts and audio messages to internal and/or external speaker systems directly from the
BlackBerry AtHoc
 management system. The IIM supports interoperability with a wide range of GV original equipment manufacturer (OEM) platforms.
The IIM interfaces with OEM GV systems using dry-contact switch closures, auxiliary audio inputs, and closed serial communication protocols, including RS-232, RS-485, and USB. These interfaces connect to the OEM’s base station controllers, allowing the IIM to also trigger predefined messages stored in the GV systems’ activation lists. Depending on the OEM’s nomenclature, these messages may be referred to as "keys", "hotkeys", or "stored messages." For consistency, we will refer to them as "keys" throughout this document.
Examples of OEM GV systems that the IIM can integrate with include, but are not limited to:
  • Federal Signal
  • Acoustic Technologies, Inc. (ATI)
  • SiRcom
  • Monaco
  • American Signal Corporation (ASC)
  • Whelen (incl. variants used with WeatherWarn/RapidWarn systems)
  • Motorola OptiWarn
IIM Operational Software Architecture
The IIM is a PC-based appliance running Microsoft Windows Server 2022. It operates using the Capnode system, an application built on the Microsoft .NET Framework version 4.8, which must be installed on the host machine to ensure proper functionality. Additionally, the IIM may utilize dry-contact switch closures as its physical interface, depending on the GV OEM it is integrating with. If required, these switch closures are provided by a third-party PCIE-based relay card.
Due to the IIM’s integration with a diverse array of OEM systems, the Capnode software must support distinct and disparate communication protocols tailored to each OEM’s proprietary command structure. Despite these differences, the core functions performed by the IIM remain consistent across vendors. As a result, variations in the Capnode software occur only in the specific command structure used to communicate with each manufacturer’s control equipment. For its .NET build, the basic version structure of the Capnode software follows the versioning format 6.1.0.xxx.
For each incoming alert, the IIM executes a predefined sequence of operations to maintain system integrity and ensure correct behavior. Upon receipt, the alert triggers the following structured activation protocol within the IIM:
  • The IIM initiates the relevant communication protocol (switch closure, auxiliary audio input, UART serial communications, etc.), activating the GV control station.
  • The GV control station processes the input from the IIM and activates the specified broadcast method (TTS, prerecorded audio file, or key.)
  • Based on the selected activation mode, the GV controller transmits the audio message to the speakers or endpoints of the GV system.
  • The IIM sends a system deactivation or cancellation command to the GV controller to terminate the active alert.
This repeatable process ensures efficient and reliable delivery of the selected alerts across the system, regardless of the GV OEM.
Migrating the IIM to the new .NET framework offers several key advantages over the legacy Java-based system. The .NET environment provides seamless integration with Windows-based applications and services, making it well-suited for enterprises that rely on Microsoft technologies. It also includes a comprehensive set of libraries and tools that boost developer productivity and simplify debugging and deployment. Additionally, because .NET is a Microsoft product, running it on the Microsoft Server platform enhances security and streamlines management across the IIM infrastructure.

6.1.0.304 – IPBSe – March 2025

A configurable parameter was added to the config file to control relay activation delay for improved timing precision.

6.1.0.270 – IPBSe – October 2024

  • IPBSe (IIM Push Button System Enhanced) was introduced.
  • IPBSe integrates with ADAM 6066 modules, allowing a single IIM to manage multiple push-button consoles over a network.
  • The ADAM modules act as network bridges between the IIM and the consoles, eliminating the need for proximity between them.
  • Previously, IIM IPBS supported only a single push-button console.

6.1.0.247 – INFPe – August 2024

  • INFPe now supports the attachment of multiple USB-based relay cards to a single IIM, increasing the number of fire panel inputs that can be controlled. This eliminates the need for multiple IIMs, even in scenarios where fire panels require more than 16 inputs.
  • Expanded the number of inputs from 16 to 128.
  • Reduced the costs associated with the need to configure and maintain multiple IIMs.
  • Improved the ability to maintain audio synchronization across all inputs and connected relay cards.

6.1.0.151 – ATI – May 2024

  • Added the ability to activate groups of sirens that are not pre-defined in the ATI REACT CCU and provided a way to set the timing for both repeater and non repeater-based activations.
  • Enhanced the Siren Grouping feature, including siren activation.
  • Added support for group dictionary, including dynamic determination of siren groups based on configurations.
  • Implemented a sorting mechanism for siren activation, prioritizing groups with lower numbers, followed by individual sirens.
  • Optimized activation logic for sirens. Introduced dynamic removal of siren and group duplications.
  • Improved logging.
  • Upgraded TTS engine to latest version.

6.1.0.121 – American Signal – April 2024

  • Added support for redundant failover and geosiren targeting.
  • Provided an activation of sirens whose sound coverage area intersects with the area of the alert.
  • Deployed with 2 IIMs that work in tandem so that if the primary IIM fails to activate the sirens or is down, the secondary IIM takes over and performs the activation.

6.1.0.100 – Federal Signal – March 2024

An issue was fixed where the CapConService builder did not create the CapCon service.

IIM release support – March 2024

  • IIM versions prior to 6.0.X are no longer supported.
  • Java-based IIM devices are end of support and end of life as of March 31, 2024.
  • All IIM devices are now available on a .NET code base.