Cloud Hosting

Honeywell officially supports running VoiceCheck in a Cloud environment. The Honeywell testing environment is the Microsoft Azure platform for Cloud hosting.

Other environments can be used so long as it meets the expected requirements. Honeywell cannot account for all variables and unknowns with other Cloud environments, but this a list of best practices. Should an issue be encountered due to these unknowns, Honeywell will provide best effort support to determine if the problem relates to our solution or the environment and help to pin point the cause.

For more information on Azure, refer to the Azure documentation.

Set up the Cloud Environment

Machine Requirements

When planning a Cloud installation, Honeywell recommends following the server requirements for local hosting with an additional margin to allow for Cloud latency. Consult with Technical Support or Professional Services for further questions regarding Cloud system specifications.

Sample Configuration

The following example is provided for an operation which might see 150-600 operator shift start size.

  • Quad Core CPU
  • Minimum 16GB RAM
  • Minimum 60 GB storage space
  • Microsoft Windows Server 2019 OS
  • Database
    • Microsoft SQL Server 2019 database has been tested. The database is installed on a separate server and is not included in the machine requirements above.

Ports

The following ports must be opened by the Network/Cloud Management team:

  • 9090 bi-directional
  • 9091 bi-directional
  • 9443 bi-directional
  • 21050 outbound
  • 9070 bi-directional
  • 9071 bi-directional

More information on these ports can be found here.

General Information

  • Honeywell does not recommend leaving VoiceCheck as an public-facing Internet accessible application.
  • Talkman devices cannot be configured to directly utilize a VPN connection.
  • File transfers, may take longer in a cloud environment than in a local installation.

Contact Support Regarding Known Issues

Contact Technical Support for information regarding the following known issues.

  • Azure high latency storage block issues with log files
  • An Azure SQL managed database instance that is not supported