Explore the technical features of our alarm services and read about different alarm protocols further down.
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.
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.
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.
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.
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.
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 care alarm signaling 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 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.
Modern CPaaS built cloud-native from ground up – we run the operations for you so you can focus on your customers’ experience.
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.