Alarm Services

Technical features

Explore the technical features of our alarm services. Click on each feature to read more.

Unified Alarmbridge API

Receive incoming alarm events that are transmitted in multiple analogue or digital protocols which are mapped to a unified event format and sent as a REST callback to your service. This allow a single point of integration to be used for multiple protocols.

Integrate with legacy alarm event protocol endpoints by calling a single REST API with a unified event format which is then mapped to the protocol specific for the device.

Heartbeat Service

The integrated heartbeat service can handle alarms and heartbeats by passing the events through to a receiving platform.

To reduce the amount of API callbacks between the platforms, the heartbeat-service may be used. This will terminate incoming heartbeat events and only trigger an alarm event REST callback in case an expected heartbeat request is not received per the configured thresholds.

Alarm Integration Flows​​

High level service flows for social care alarm integration let you save time by not having to dig into protocol specific event flows for social care alarm integration. Alarmbridge provides built-in functionality to acknowledge a received alarm and to clear an alarm event.

Voice Calling​

An alarm event may require a voice call to be established with the device that triggered the alarm event. Alarmbridge allows high level API functions to establish a voice call between the device and an ordinary phone system or by using the WebRTC gateway capabilities with a web browser application.

Hang up calls​

A protocol agnostic API is used to clear down an established voice call with a social care alarm. By design the call can’t just be hung up, instead a protocol specific message sequence has to be exchanged with the device before hanging up.

Real-time & Mediaservices​​

Alarmbridge natively integrates with the rest of voice and video capabilities provided by the iotcomms.io platform, such as SIP trunks to receive and place voice calls, and Mediaservice capabilities for advanced interactive voice services. An alarm event may also be used to trigger a video session.

Service Alarm Events​

Alarmbridge provides service alarm events in case of unforeseen service related issues such as access from unprovisioned devices or failure to deliver alarm events.

Alarm Protocols

IP BASED PROTOCOLS

Social Care Alarm Internet Protocol is originally a Swedish standard used for social care devices. It is an extension to the SIP protocol that originally was developed for Voice over IP (VoIP) applications. The alarm events are carried as an XML body in a SIP MESSAGE request. The use of SIP as base for the protocol makes it well suited for use in modern telecom networks to establish voice communication with the device.

This is a European standard for social care alarms which is derived from the SCAIP protocol which also use SIP as foundation. It is backward compatible with existing SCAIP implementations.

This is a British standard for social care alarms. It fulfils requirements for grouped livings. Similar to SCAIP and CENELEC TS 50134-9, the protocol transmits alarm events using the SIP MESSAGE method and is able to set up voice communication using SIP VoIP.

This is an IP based protocol developed by The Security Industry Association used to transmit alarm events from an alarm equipment to an alarm center.

ANALOGUE PROTOCOLS

This is a British standard for social care alarms. To transmit an alarm event the device dials a phone number and when it is connected it sends a string of DTMF tones to transmit the id of the device and the event type. The receiver can then signal back to the device to establish a voice connection and re-use the call for that purpose.
This is a proprietary protocol used by the alarm device manufacturer Tunstall. To transmit an alarm event the device dials a phone number and when it is connected it sends a string of DTMF tones or single frequency tones (STMF) to transmit the id of the device and the event type. The receiver can then signal back to the device to establish a voice connection and re-use the call for that purpose.
This is another proprietary protocol flavor used by the alarm device manufacturer Tunstall. To transmit an alarm event the device dials a phone number and when it is connected it sends a string of DTMF tones to transmit the id of the device and the event type. The receiver can then signal back to the device to establish a voice connection and re-use the call for that purpose.
This is a proprietary protocol used by the alarm device manufacturer Telealarm. To transmit an alarm event the device dials a phone number and when it is connected it sends a string of DTMF tones or FSK encoded modem data to transmit the id of the device and the event type. The receiver can then signal back to the device to establish a voice connection and re-use the call for that purpose.

This is a protocol used for a variety of alarm applications, for example elevator alarms and social care alarms. To transmit an alarm event the device dials a phone number and when it is connected it sends a string of DTMF tones to transmit the alarm event. The receiver can then signal back to the device to establish a voice connection and re-use the call for that purpose.

This standard details the specification for the “Ademco Contact ID” communication format, originally developed by the Ademco Group, a division of the Honeywell Solutions Group. It utilizes standard DTMF tones for transmission of the information.

Supported Telecare Devices

Alarmbridge supports Telecare devices from a range of vendors.
Support for equipment from other vendors can be added upon request.

Careium Telecare
SCAIP as a Function support Telecare devices from Climax
SCAIP as a Function support Telecare devices from Tunstall
SCAIP as a Function support Telecare devices from TeleAlarm
essence – Better life made possible
SCAIP as a Function support Telecare devices from Neat
Everon logo
5/5
Our customers experience reduced cost, improved time to market and increased quality
With iotcomms.io, we can move forward much faster than if we were to develop all the functions ourselves. Now we can effectively add more devices which also support the SCAIP protocol.
Mikael Hamström
Mikael HamströmCTO Phoniro Assa Abloy
iotcomms.io allows us to handle variations, whether it is various protocols or devices, in a unified way. With iotcomms.io we can reduce the complexity and move fast to the market.
Martin Strand
Martin StrandHead of Product Skyresponse
To become SCAIP compliant and move to a digital solution of our TeleAlarm devices, is an important step for us to secure that our users are future proofed.
Rutger Vercauteren
Rutger VercauterenSales Manager TeleAlarm

Get Started

Talk to us today or visit our Developer Area to learn more about our Alarmbridge API.

Developer Area

Talk to us today

Get in contact if you want to start building with our granular & feature rich communication APIs.
Contact Sales

Modern CPaaS built cloud-native from ground up – we run the operations for you so you can focus on your customers’ experience.

%
UPTIME

Built for mission critical alarm, voice & video services – delivering superior reliability, security and availability.

Built with serverless functions in AWS for unlimited scale, reach and global deployment – extend to new markets quick and easy.

Youtube Linkedin-in Envelope

Magnus Ladulåsgatan 13, 118 65 Stockholm, Sweden