Single Server Hardware Requirements
Following are the minimum hardware requirements for setting up the HC solution for early field trial (EFT) on a non-redundant single server.
| Item | HC media routing | RASA Chatbot | Superset Reporting | Voice Switch | Secure SIP SBC |
|---|---|---|---|---|---|
| vCPU | 4 | 4 | 4 | 2 | 2 |
| RAM | 8 GB | 4 GB | 4 GB | 4 | 2 |
| Hard Disk | 100 GB | 100 GB | 100 GB | 40 | 2 |
The voice servers are only required if you wish to run the solution also as a call center.
Software Requirements
- Operating System: Ubuntu 22.04 LTS
- Docker Community Edition 18+
- Docker Compose 1.26 or above
- Git Client 1.8+
- Mandatory Linux utilities:
wgetcurl
Developer Tools installed on the Linux host. (optional)
yum group install "development tools"
7. SQL Server 2019 or MYSQL 8.0
TLS Certificate Requirements
- Certificates from a valid signing authority or Domain signed certificate are required for HTTPS protocol support. For applying for certificates, see Configure SSL Certificate
System Access Requirements
- Administrative privileges (root) on the host machine are required to proceed with the installation.
System Configuration Requirements
- Set up an FQDN to access HC Solution that should be resolved to the IP address of the host.
Port Utilization
For Product Installation
The ports mentioned in this section must be open to installing the product.
Source Host | Destination Host / Docker Container | Source Port | Destination Port | Communication Protocol | Scope | Description | |
|---|---|---|---|---|---|---|---|
| 2 | HC Host | Expertflow Container Registry | any | 9242 | TCP | public | to clone the images from GitLab registry |
| 1 | HC Host | ExpertFlow GitLab | any | 443 | HTTPS | public | to clone skeleton project from Gitlab |
For Product connectivity with internal and external components
Ports mentioned in this section should be open for the mentioned product connectivity with different internal and external components.
Source Host | Destination Host / Docker Container | Source Port | Destination Port | Communication Protocol | Scope | Description | |
|---|---|---|---|---|---|---|---|
| HC | HC Gateway | any | 443 | HTTPS | public | To access the HC component publicly.
| |
| 2 | HC | MS SQL Server | any | 1433 | TCP | private | MS SQL Server for Reporting |
Time Synchronization
Communication between HC Solution, client applications, and external databases carry timestamps. If the system dates and times are not synchronized the system can produce unpredictable results. Therefore, please make every effort to adhere to the following time synchronization guidelines:
HC Solution, client applications external database should have their Time Zone and time configured properly according to the geographic region and synchronized. To configure the time zone, please see the instructions from the hardware or software manufacturer of the NTP server. Client applications and HC solutions should be synchronized to the second. This synchronization should be maintained continuously and validated on a regular basis. For security reasons, Network Time Protocol (NTP) V 4.1+ is recommended.
Add Comment