Alarmbridge Connect Service - Plug & Play GW Configuration

The Alarmbridge Connect Gateway enables a seamless transition from analog to IP-based alarm communication, for example for group living schemes and other critical applications. Based on the reliable Grandstream HT801 Analog Telephone Adapter (ATA), the Gateway bridges legacy alarm control units with modern Alarm Receiving Centers (ARCs) using protocols such as NOW-IP and SCAIP.

Unlike generic VoIP services, which often introduce instability due to signal processing, firmware inconsistencies, or routing across multiple networks, the Alarmbridge Connect Gateway avoids these risks by establishing a direct and managed connection to the Alarmbridge Service. It is not the IP network itself that causes unreliability in alarm transmissions, but rather the various intermediaries—VoIP providers, their firmware, and routing paths—that distort or delay DTMF tones critical to analog alarm communication. The Gateway bypasses these intermediaries entirely, maintaining reliable tone transmission, low latency, and controlled firmware updates specifically optimized for alarm traffic.

The Gateway fully replaces the existing public telephony service by serving as the communication link between the analog alarm control unit and modern IP-based alarm platforms. Installation is as simple as connecting the Gateway to the Internet via an Ethernet cable, plugging in the power supply, and moving the telephone plug from the PSTN wall socket into the Gateway’s phone port.

Thanks to its plug-and-play design, the Gateway can be deployed with minimal technical intervention. It connects directly to existing analog alarm systems and automatically retrieves its configuration from the cloud. This eliminates the need for on-site programming while ensuring secure, remotely managed operation.

Once installed and provisioned, the Gateway securely transmits alarm events over IP networks, supporting encrypted delivery and continuous connectivity monitoring. This ensures both compliance with evolving communication standards and uninterrupted protection for residents.

Alarmbridge Connect Service provides a built-in device provisioning function that automatically configures Grandstream-based Alarmbridge Connect Gateways and keeps their settings up to date. This eliminates the need for manual programming and ensures the devices are securely and consistently managed across deployments.

Provisioning Steps

1. Configure API Access Key

   

   Ensure that an API access key is configured for the tenant. This key will be used by the gateway to authenticate with the Alarmbridge Connect Service when fetching its configuration.

   Link to Access Key Configuration

2. Download Bootstrap Configuration File

   
   Each gateway must be provided with the service URL and the authentication key. To simplify this step, a tenant-specific bootstrap configuration file can be downloaded from the Device Provisioning page. Save this file locally for use when setting up the Alarmbridge Connect Gateway.

   Link to Devices Management

3. Provision the Gateway Device in the iotcomms.io Platform

   
   Before installation, register the gateway in the iotcomms.io platform to generate its SIP credentials and configuration data. This step ensures the device receives the correct settings from the provisioning service.

   Click the Create Device button to set up a new device.

   The following information is provisioned for each device:

   • Authentication Type

     Set to *SIP Digest*

   • Device ID

     This is used as the calling party number. If migrating from PSTN, reuse the existing PSTN phone number.

   • Device Type

     Set to *Alarmbridge Connect*

   • MAC Address

     Unique to each device and found on the device label. This links the device to its configuration.

   • Description

     Optional field for labeling (e.g., installation address).

   • Configure Service Data

     Enable this option to define protocol-related settings.

   • Service Data Object

     Used to specify the analog protocol (e.g., TT92 or TTNew). Example:

     {
         "alarmBridge": {
             "alarmProtocol": "tt92"
         }
     }
     

   When using TTNew, set the value of alarmProtocol accordingly.

   To streamline MAC address entry, the provisioning UI includes a scan function that uses the laptop camera. Press the scan button to start scanning. This will pop up a request to give permission to use the camera that must be accepted first. Then hold the device label in front of the camera to auto-fill the MAC address field.

   

   Once all data is entered, press the Create button to save the configuration. The gateway is now provisioned and ready to be configured using the downloaded bootstrap file.

   Link to Devices Management

Once the Alarmbridge Connect Device has been created, the next step is to configure the physical Gateway unit. This is done by using the previously downloaded bootstrap configuration file.

Configuration Steps

1. Connect the Gateway to the Network and Power

   • Plug the Ethernet cable into the WAN port of the Gateway and connect it to the site’s router.

   • Connect the power adapter and switch on the device.

2. Apply the Bootstrap Configuration

   • Access the Grandstream web configuration interface by entering the device’s local IP address in a browser.

   • Navigate to the configuration upload section.

   • Upload the tenant-specific bootstrap configuration file downloaded during the service provisioning step.

   • Save and apply the settings. The device will reboot and retrieve its full configuration from the cloud.

3. Connect to the Alarm System

   • Disconnect the existing telephone cable from the PSTN socket and plug it into the Gateway’s FXS port.

   • This connects the alarm control unit to the Alarmbridge Connect Gateway, replacing the PSTN connection.

4. Automatic Configuration and Synchronization

   • Upon reboot, the Gateway will authenticate using the token and MAC address, then pull the correct SIP credentials and configuration from the provisioning service.

   • No further local changes are needed; all updates and settings are managed remotely.

This plug-and-play process ensures a quick, repeatable setup across multiple sites while maintaining a secure, centrally managed infrastructure for alarm communication.

The Devices Management page provides a list of all provisioned devices. It includes a column named Config Downloaded, where you can verify when a device last retrieved its configuration. After the first reboot following provisioning, this timestamp should update. If it does not, it may indicate a networking issue or that the bootstrap configuration was not successfully applied.

The Status column displays the SIP registration state of the device. A green circle confirms that the device is registered and connected successfully.

If configuration is not downloaded or the device does not register, log in to the device’s web interface and review the Status page for any error messages or diagnostic information.

To streamline large-scale deployments of Alarmbridge Connect Gateway devices, several methods can be used to reduce manual effort and increase efficiency:

• Factory Preloading of Bootstrap Configuration: When purchasing Grandstream gateway devices in volume, it is possible to have the tenant-specific bootstrap configuration file pre-loaded at the factory. This eliminates the need to unpack each device individually to manually upload the configuration, significantly reducing deployment time.

• Local TFTP Distribution via DHCP Option 66: An alternative approach is to host the bootstrap configuration on a local TFTP server and direct the gateways to retrieve it automatically. This can be achieved by configuring DHCP Option 66 to point devices to the TFTP server, as described in the Grandstream documentation. This method allows devices to auto-configure immediately upon being connected to the network.

• Bulk Provisioning via CSV Import: The iotcomms.io Device Provisioning page includes an "Import Devices" feature that allows administrators to upload a CSV file containing the configuration details for multiple devices. This bulk upload automatically registers all specified devices, assigns MAC addresses, and populates configuration fields, greatly accelerating the provisioning process.

These strategies enable efficient rollout of a large number of gateways, minimizing on-site tasks and enabling scalable, reliable installations across multiple locations.