Feature availability

Sinch Contact Pro cloud has features that are not available out-of-the-box in on-premise environments.

The following outlines the features and the reasons they are not included:

  • Features dependent on AWS:

    • mobile client

      Mobile client feature (now a Beta version available in cloud) relies on the AWS SNS for pushing notifications. Once mobile client is officially released, we'll see whether the feature can also be made available to on-premises customers.

    • cloud attachments

      Cloud attachments rely on AWS services and can't be implemented in on-premise systems. We use S3 bucket and create signed links to the bucket. In addition, we have link.cc.sinch.com reserved for short links and AWS database and Lambda functions to handle short links.

    • storing call recordings/attachments to S3

      Sinch Contact Pro cloud uses Amazon S3 service for storing call recordings and email attachments. This is to avoid storing business data on a local drive, as Amazon does not recommend it for long-term storage. The recommendation is to use other storage options or build replication of S3 if required. Technically it's possible to make connection from a local data center to the AWS S3 service. However, we don't support this and have no documented instructions for it.

    • call metadata file, also called Call Trace Record (CTR)

      This is generated only in S3 storage and can't be implemented in on-premise systems.

  • Other features not available at the moment:

    • AI and Sinch Contact Pro

      Once AI is officially released in cloud, we'll see whether the feature can also be made available to on-premises customers.

    • oData service

      We'll see whether the feature can also be made available to on-premises customers later.If you'd like to know more about this, please create a ticket.

  • Available via partners: IDP authentication

    IDP-based Single Sign-On (SSO) logging method is in general possible to implement but requires integrator work. We haven't documented authentication methods due to the variety of IDP providers. Fully supporting on-premise customers in this would require expertise in all these different providers. Therefore, we rely on our partners to implement IDP-based authentication for on-premise systems. If you'd like to explore this option with the help of our partner, please create a ticket, and we'll connect you with them.