- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
This document outlines the hardware and software requirements for deploying the Knovvu Real Time Guidance (RTG) solution. To ensure optimal performance, all listed requirements must be met.
Acronyms and Abbreviations
DB: Database
VM: Virtual Machine
OS: Operating system
FQDN: Fully Qualified Domain Names
RTG: Real Time Guidance
CA: Conversational Analytics
Database Requirements
- The database can be named ConversationalAnalytics.
- It can be hosted on a central database or on a dedicated server.
- Supported database management systems:
- PostgreSQL version 13 or higher
- MS-SQL 2016 or later (Enterprise or Standard editions)
- The database language must be set to English.
- Collation:
- For English deployments: SQL_Latin1_General_CP1_CI_AS
- For Turkish or Arabic deployments: Turkish_CI_AS
- Features: Full Text Search must be enabled.
- Database User Roles:
- If the database is not clustered, the user must have the sysadmin role.
- For clustered databases where sysadmin permissions cannot be granted, the user must have the public server role.
- The db_owner role must be assigned to the database user.
- The user must have View Server State permission.
System Requirements
- The solution supports up to 10 concurrent agents for real-time analysis during testing.
- Customers are responsible for any third-party licenses, including database management systems and operating systems.
- The operating system must be up to date to ensure compatibility.
- If a service user is defined, all credentials across servers must be consistent.
- CA, Core, and the agent widget must be added to the whitelist of antivirus applications.
- Example paths to exclude from antivirus scanning:
- "C:\Program Files\Sestek\Falcon\CallRecorder"
- "D:\Sestek" (used by voice streaming applications)
- Example paths to exclude from antivirus scanning:
- When Sestek installs Kubernetes and the DevOps Terminal, the system supports CentOS 7/8 and RHEL 7/8.
- Port requirements:
- The port number for the Streamer and Online Analysis Server must be 3 times the number of concurrent calls.
- The solution must be deployed across three clusters:
- Core Cluster (including Speech Recognition)
- Knovvu Machine Learning (ML) Cluster
- Knovvu Analytics Cluster
- The license server must run on a Windows machine.
- vCPU Requirements:
- The minimum node size is 16 vCPUs.
- Total required resources can be distributed among nodes once the project starts.
- Wireshark is mandatory if the Knovvu RTG project involves a streamer.
- The minimum network connection speed should be 100Mb/s.
Communication Matrix
Source Cluster/Network | Source Service Name | Target Cluster/Network | Target Service Name | Port |
---|---|---|---|---|
Clients | Sestek Streamer | Knovvu Core cluster | Socket | 80 (TCP) |
Clients | Client | Knovvu CA cluster | Web server | 80 (TCP) |
Clients | Client | Knovvu Core cluster | Web server | 80 (TCP) |
Knovvu CA cluster | Knovvu CA cluster | Database server | MS SQL / PostGre database server | 1433 (TCP) |
Knovvu CA cluster | Knovvu CA cluster | Sestek License Server | Sestek License Service | 30113(TCP) |
Terms Glossary
Term | Definition |
---|---|
Node | A physical or virtual machine that runs the services required for the Knovvu Biometrics solution. |
Pod | A small, scalable unit of deployment in Kubernetes that contains one or more containers. |
VM | A virtual machine that can host Knovvu Biometrics services when the system is not running directly on physical hardware. |
Cluster | A set of nodes or VMs configured to work together to provide scalability and redundancy. |
vCPU | Virtual CPU assigned to the VM or container running Knovvu Biometrics services. |
vCPU Request | The minimum CPU capacity allocated to the service within a container to ensure a smooth operation. |
vCPU Limit | The maximum CPU capacity that a container can use. It ensures that the service does not overconsume resources, impacting other services on the node. |
Was this article helpful?