A telecare solution that uses digital interfaces instead of analogue signals has many advantages, including increased flexibility, reliability, and functionality. It also allows for multiple sensors to be connected to the telecare unit.
To make this digital transition, it’s important to comply with standards such as SCAIP (Social Care Alarm Internet Protocol). Unfortunately, many alarm devices and platforms don’t meet this standard, which can be a costly and time-consuming issue. But don’t worry, we have a solution to help you add SCAIP support quickly and efficiently without slowing down your time to market.
Contact us to discover how you can add SCAIP support to your solution!
With your service, we can move forward much faster than if we were to develop all the functions ourselves. No we can effectively add more devices, which also support the SCAIP protocol.
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.
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.
Become SCAIP compliant with iotcomms.io
We make it easy for alarm solution providers to comply to the SCAIP standard through integration with a cloud service. With iotcomms.io you can add SCAIP support to:
- Care Devices
- Alarm Receiving Platforms
- IoT Devices
Make your alarm platform SCAIP compliant
With iotcomms.io you can connect SCAIP-enabled devices to an alarm receiving platform or contact center solution that lacks support for the SCAIP standard.
iotcomms.io receives the SCAIP message from the device and convert the signaling to standard HTTP messaging
iotcomms.io delivers the alarm event to the alarm platform through a REST API
iotcomms.io can also bridge from SCAIP to other alarm protocols supported by the alarm platform
Make your IoT & care devices SCAIP compliant
With iotcomms.io you can connect digital devices lacking SCAIP support to a SCAIP compliant alarm receiving platform.
Integrate to iotcomms.io via a REST API and call our Alarmbridge API to trigger the alarm event
iotcomms.io converts the alarm event to a SCAIP message and send it to the SCAIP compliant receiving platform
The alarm event may also trigger a voice between your device and a phone system
The shift from analog to digital telecare
When telecare devices started to be used in the 1960’s, analogue protocols and the fixed network was the only and obvious choice. Since then, the telecommunication network has continuously evolved and both mobile networks and fiber networks have more and more taken over the role of communication.
In many markets, the analogue care devices are still dominant causing problems such as call failures, reliability issues and lack of functionality and security. Digitalization of the telecare market provides devices and systems that are always connected allowing sensors and care devices to continuously share information with a receiving platform, which leads to improved monitoring of devices.
SCAIP – a key building block for digital migration
To migrate successfully, compliance with the SCAIP/CENELEC TS 50134-9 standard is a key building block. However, adding support for this standard is expensive and time-consuming, which can slow down time to market.
Currently, many devices like smart assistants, IoT, and care devices, along with alarm receiving and contact centers, do not meet the SCAIP standard. This poses a challenge for migration.
Why iotcomms.io?
Read these interviews to find out how two of our customers became SCAIP compliant with iotcomms.io.
FAQ
What is SCAIP SS 91100:2014?
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.
What is CENELEC TS 50134-9?
CENELEC TS 50134-9 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.
Where can I find information about the use cases you support?
We have written a number of blog posts about different use case scenarios that iotcomms.io support. Don’t hesitate to contact us if your specific use case is not presented.
Where can I find information about integration and APIs?
- You can find a high-level view of the integration service here →
- You can explore our APIs and documentation here →
How much does it cost?
We offer competitive pay-as-you-go pricing based on the following parameters:
- Number of alarm events
- Number of heartbeat messages
- Number of connected devices
- Support plan
Contact us for an initial discussion and pricing indication for your specific use case.
How do I get started?
Contact us for a quick discussion around your use case, and we can setup a test account and trial after that.
Supported Telecare Devices
iotcomms.io supports a wide range of device manufacturers and can connect to receiving platforms through a variety of protocols. Support for equipment from other vendors can be added upon request.
Contact us to discover how you can add SCAIP support to your solution!
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.
Magnus Ladulåsgatan 13, 118 65 Stockholm, Sweden