Requirements

This document describes the server requirements of Knovvu Virtual Translator solution.

Acronyms and Abbreviations

Key Considerations

1. Port Utilization:

   • The SIP Gateway utilizes two ports per call.
   • Speech Recognition (SR), Text-to-Speech (TTS), and Translation Services utilize one port per call. Each side of the communication alternates between listening and responding.

2. High Availability:

   • For high availability configurations, if only one SIP Gateway server is specified, it should be automatically scaled to two servers to ensure redundancy.

3. Language Support:

   • These requirements are applicable to languages supported by Knovvu Virtual Translator. If additional languages are needed, the requirements may be subject to revision.

4. External Translation Services:

   • For integration with external translation services like Azure or Google Translate, access addresses and ports must be preconfigured.

System Requirements

SIP Gateway Requirements

1. Operating System:
   • Windows Server 2012 R2 (64-bit) or newer.
2. Required Tools:
   • Visual Studio C++ 2017 Redistributable
   • Notepad++ (latest version)
   • Wireshark (latest version)
   • Snake Tail (latest version)

SR & TTS Requirements

• Platform Requirements:
  The system is designed to operate on both Openshift and Kubernetes platforms.

• Replication Settings:
  The minimum number of replicas for each component is predefined. Adjustments may be needed depending on the specific deployment topology.

• Product Requirements:
  Default settings for SR and TTS pods assume a single language model or voice per instance. Modifications should be based on specific client needs.

• Multiple Language Support:
  For deployments requiring more than one language, please consult with us for proper configuration and resource allocation.

• Performance Specifications:

  • SR: Performance may vary with the complexity of grammars, size of audio files, and application usage frequency.
  • TTS: Testing conducted with caching enabled (cache size of 5000) and average audio file duration of two seconds on machines with 4 CPU cores.

• Operating System Support:
  When Sestek is responsible for installing Kubernetes, we support CentOS versions 7 and 8, as well as Red Hat Enterprise Linux (RHEL) versions 7 and 8.

• Hardware Compliance:
  It is critical to meet the specified hardware requirements initially, as upgrading hardware post-deployment is not advisable and may lead to performance issues.

• Software Updates:
  Refrain from upgrading packages that have fixed versions from the installation, including container runtime and Kubernetes components.

• System Upgrades and Security:

  • Disable unattended upgrades.
  • Turn off firewalls for the virtual machines (VMs) provided.
  • Disable antivirus and malware protection software on the provided VMs.
  • Avoid unauthorized changes to major OS versions.
  • Set SELinux to permissive mode; enforcing mode may cause issues.
  • Ensure OS disks are set up for potential expansion using Logical Volume Manager (LVM).
  • Avoid unmounting OS disks or altering mount points

Database Compatibility and Configuration

• Supported Databases:
  Compatible with PostgreSQL versions 12, 13, and 14, as well as Microsoft SQL Server 2016 or newer.

• Database Naming:

  • SR: Default database name is "sr".
  • TTS: Default database name is "tts".
    Customization is possible to align with specific project requirements or organizational standards.

• Database Management:

  • Maintenance Tasks:
    Customers are responsible for routine database maintenance tasks, including periodic backups and replication, utilizing their own database management resources.
  • Access Permissions:
    Appropriate permissions must be granted to database users to ensure seamless connectivity and operation.

Network Requirements

• Bandwidth:
  • A minimum connection speed of 100 Mbps is required.
• External Access:
  • Address and port configuration for external services must be predefined.
• Monitoring Tools:
  • Wireshark for packet analysis and troubleshooting SIP-related issues.

Terms Glossary