Requirements

Assumptions

• SIP Gateway will use 2 ports for each call.
• SR-TTS-Translation will use 1 port at a time for each call. (The two sides wait, listen and respond to each other respectively.)
• In the production environment, if SIP Gateway High Availability is requested and the request points to only 1 SIP Gateway server, it should be automatically increased to 2.
• These requirements are valid if the languages to be supported within the scope of the project are Sestek languages. May be revised if other languages are added
• Access addresses and ports required for external translation services such as Azure or Google must be defined.

SIP Gateway Requirements

• Windows 2012 R2 64 Bit or newer
• Visual Studio C++ 2017 Redistributable
• Notepad ++ latest version
• Wireshark latest version
• Snake Tail latest version

Important Notes

• Requirements are defined for Openshift and Kubernetes Platforms.
• Replica values are specified as a minimum.
• If the calculation must be for more than one language, it is necessary to contact us.
• Product requirement field is calculated as default values of SR, and LMS pods. They can be rearranged based on client topology. It is assumed that there is only one language model for SR.
• Product requirement field is calculated as default values of TTS pods. They can rearrange based on customer topology. It is assumed that there is only one voice for TTS when values are calculated.
• SR requirements might change based on complexity of grammars or language model, size of audio files and frequency of usage the application.
• TTS tests are made when Cache is true and cache amount is 5000. Average audio file duration is 2 seconds. Also, tests are run in 4 core machines.
• In cases that Sestek installs the Kubernetes, CentOS 7/8 and RHEL 7/8 are supported.
• All hardware requirements should be met without fail, upgrading the hardware after a monitoring period would not be the correct path of action. The product may not perform properly, therefore, if the requested hardware is not provided, possible performance issues may arise. Upgrading after usage monitoring may prevent addressing the issue. The customer is responsible for providing all of the required hardware.
• Unattended upgrades should be disabled.
• Firewalls should be disabled for the provided VM's.
• Anti-virus and mallware software should be disabled for the provided VM's.
• Uninformed changes in OS major versions should be avoided.
• SELinux should be kept in permissive mode (Enforcing mode should be avoided).
• OS disks should be provided in a way that they can be enlarged using LVM.
• Unmounting OS disks or changing/switching mount connections should be avoided.
• Upgrading packages which have versions fixed during installation (Container runtime, kubernetes components) should be avoided.
• For managed test environments, minikube configurations are given just for the sake of minimum test requirements. For specific testing requirements please contact us.
• For unmaged test environments, worker node consists LB and NFS nodes.
• For unmanaged production environments, physical and network related availability and backup necessity of master and worker VM's should be provided by the client.
• Knovvu SR solution supports PostgreSQL. Database names are determined by each product. PostgreSQL instance for Core products are installed on the Kubernetes cluster.
• Wireshark should be mandatory if SR projects will have MRCP.
• Wireshark should be mandatory if TTS projects will have MRCP.
• Minimum connection speed should be 100mbit.