Some embedded communications applications need to work over a wide range of devices – including mobile phones, PCs, mobile radios, desk-phones and even legacy pagers. Sectors such as hospitals evolve operational systems only slowly – and may have an “if it isn’t broken, don’t fix it” mindset.
Support for industry-specific protocols
Some applications will be based on event “triggers”, such as alarms or industrial controls.
- In many instances the underlying systems may be legacy installations that will not be replaced as part of the transformation project (perhaps a fire alarm, or building management system).
- In other cases, there may be specific standard applied – for example the Social Care Alarm Internet Protocol, SCAIP for telecare monitoring in Europe.
Customised interaction flows
The normal metaphor and user-interaction model of a “phone call” or an SMS message, with a ring-tone or busy signals, may not be applicable. The platform needs to be able to support one-way voice (eg for audio announcements), one-way video / one-way audio (for example, for a video doorbell), perhaps push-to-talk, listen-only, group-calling or various other options.
Support for application-specific triggers
Towards an embedded CPaaS market
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.
Magnus Ladulåsgatan 13, 118 65 Stockholm, Sweden