Features & Protocols
Features overview
- Serverless Functions
Serverless functions with mission critical availability design help you save time and money on costly infrastructure deployments and service operation.
- Unified 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 the call.
- 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.
- Authentication Schemes
Incoming alarm events are authenticated against provisioned devices using appropriate authentication scheme for the protocol used for access.
- 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.
IP BASED PROTOCOLS
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.
ANALOGUE PROTOCOLS
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.
More to Explore
Serverless functions built upon AWS public cloud for unlimited scale, reach & global deployment – extend to new markets quick and easy
cPaaS that you can trust for
mission-critical installations – our platform delivers superior availability, reliability & performance
Built upon microservices with strongest possible security in mind – 24/7 support and redundant environment keeps you fully secure