...
| Step | Documentation section | Result | Note | ||||||
|---|---|---|---|---|---|---|---|---|---|
| 1. Checking the hardware requirements for the system | |||||||||
| 1.1 The latest software versions of internal devices and server controllers (BIOS, RAID, iDRAC, iLO, etc.) are installed | See the documentation for the server that is used | ||||||||
| 1.2 The presence of at least a dual-core CPU in the system | Development of the system project | Defined by the system project | |||||||
| 1.3 The presence of at least 8 GB of RAM in the system | Development of the system project | Defined by the project depending on the required load. For test purposes, a reduction of up to 4 GB is allowed | |||||||
| 1.4 Enough disk space | Creating disk partitions | ||||||||
| 1.5 Partitioning done correctly | Creating disk partitions | ||||||||
| 1.6 SWAP file is NOT used in the system | |||||||||
| 2. Checking the software requirements for the system | |||||||||
2.1 The correct version and bit depth of the operating system are set (Ubuntu Server 18.04.x LTS 64bit) | Ubuntu Server 18.04 x64 | ||||||||
| 2.2 The correct hostname is set: ecss1 or ecss2 | When using redundancy | ||||||||
| 2.3 Current updates are installed in the system | |||||||||
| 2.4 The recommended software is installed in the system | |||||||||
| 2.5 The ECSS-10 repository has been added to the system and is accessible | System update | ||||||||
| 2.6 The network interfaces are configured correctly: | |||||||||
| - addresses of network interfaces are static and do not change dynamically via DHCP | Configuring network interfaces | ||||||||
| - the keepalived service (VRRP) is configured and running | When using redundancy | ||||||||
| - IPv6 support is enabled at least on lo interfaces | Example:
| ||||||||
| 2.7 The eToken/RuToken key is connected to the USB port of the server: | Checking Token operation | ||||||||
| - The eToken/RuToken key has been defined in the system (lsusb) | |||||||||
| - Checking the eToken/RuToken key | Checking Token operation | ||||||||
| 2.8 Checking network availability between ecss1 and ecss2 hosts: | When using redundancy | ||||||||
| - ping delay between hosts does not exceed 100 ms | It is necessary to minimize traffic delays between hosts as much as possible | ||||||||
| - no packet loss during data exchange between hosts | The ping command is run for a few minutes, after which the statistics are removed by a combination of keys:
Example:
| ||||||||
| - hosts are accessible to each other by DNS name (as written in /etc/hosts/ and in accordance with the license) | Checking ping from ecss1 to ecss2 and vice versa | ||||||||
| - key authentication between hosts is configured | Generate ssh key and transfer it to another server:
Similarly from ecss2 to ecss1 | ||||||||
| 2.9 Time synchronization with the NTP server is running on the server: | Time synchronization on servers | Check the status:
| |||||||
| - the correct time zone is set | Check:
| ||||||||
| - time synchronization in orphan mode or synchronization with a single NTP is configured on ecss1 and ecss2 hosts | Time synchronization on servers | When using redundancy | |||||||
| 2.10. Glusterfs-server of the recommended version is installed: | Configuring RestFS | Software version 3.13.2 and later | |||||||
| 3. Checking the correctness of the ECSS-10 installation | |||||||||
| 3.1 Installation of system component packages was completed successfully without errors: |
| ||||||||
| - ecss-mysql | |||||||||
| - ecss-node | |||||||||
| - ecss-media-resources | ecss-media-resources installation | ||||||||
| - ecss-media-server | |||||||||
| - ecss-restfs | |||||||||
| - ecss-user | |||||||||
| - ecss-web-conf | |||||||||
| - ecss-dns-env | DNS | ||||||||
| - additional optional packages according to the project | Additional packages optional installation | ||||||||
| 4. Checking the performance of the ECSS-10 system | |||||||||
| 4.1 Checking the installed ECSS-10 license: | System start and activation | ||||||||
| - pcscd service is operating | Software Installation and Token Connection |
| |||||||
| - the correct passport is installed in the system | System start and activation | CoCon command:
| |||||||
| - the current license is installed in the system | System start and activation | CoCon command:
| |||||||
| 4.2 The dnsmasq service is up and running: | |||||||||
| - if the system is redundant, the correct primary addresses are registered in the dnsmasq configuration.broker.ecss and secondary.broker.ecss | Cluster system installation features | Note that the content is the same on both servers.
| |||||||
| - addresses are available by DNS name | DNS |
| |||||||
| 4.3 Listen interfaces for the epmd service are registered on ecss1 and ecss2 hosts | Configuring listen interface for epmd service |
| |||||||
| 4.4 MySQL Database server is up and running: |
| ||||||||
| - it is possible to connect to the MySQL server by DNS name |
| ||||||||
| - when using redundancy, database replication is started and working correctly | MySQL master-master replication deployment scheme using keepalive |
On both servers:
| |||||||
| - mysql port should listen on 0.0.0.0. |
| ||||||||
| 4.5 The cluster name is registered in the system with redundancy (not undefined) | Cluster system installation features |
| |||||||
4.6 ecss services are up and running (in the running state):
| Checking the status of services | Examples:
The status should show "active"
Same for the is-active key:
| |||||||
| - The CoCon "system-status" command outputs an empty Alarms list | |||||||||
| 4.7 The MSR media server is configured and connected to ECSS-10: | Configuring a software media server | ||||||||
| - configuring the MSR to connect to ECSS-10 | Configuring the MSR configuration file | From shell servers:
| |||||||
| - MSR is declared in system media resources | CoCon:
If the system is redundant, check if it is connected to both cores. | ||||||||
| - MSR is configured on the ecss2 host in the same way | When using redundancy | ||||||||
| 4.8 Restfs is configured and accessible from the ECSS-10 server: | |||||||||
| - RestFS is available for recording and downloading media files | From shell servers:
| ||||||||
| 4.9 The TTS service (text to voice message conversion) is configured and running: | If tts is selected when installing ecss-restfs | ||||||||
| - The service returns the voice file after converting from text | From shell servers:
where: | ||||||||
| 4.10 Users, their rights and roles are configured | CLI:
Web - "User manager" | ||||||||
| 4.11 Subscriber service restriction rules are configured | CLI:
Web - "User manager" | ||||||||
| 5. Checking the correctness of the domain configuration in ECSS-10 | CLI:
Web - "Domains" | ||||||||
| 5.1 SIP transport (ip-set) is configured in the domain | |||||||||
| - Addresses (node_ip) and ports (listen_port) are set in accordance with the project | CLI
Web - "Clusters" | ||||||||
| - node_ip addresses are assigned on both nodes of the SIP adapter ecss1 and ecss2 | When using redundancy
Web - "Clusters" | ||||||||
| - node_ip addresses match the addresses of the reserved interfaces configured in keepalived | When using redundancy
Web - "Clusters" | ||||||||
| - ipset is set on the domain | CLI
Web - "Domains" | ||||||||
| 5.2 The necessary services have been added to the domain: | |||||||||
| - installation into the service system has been performed | CLI:
Web - "SS install" | ||||||||
| - the domain is added to the services to the access-list | View services installed in domains:
To add services on a domain:
Web - "SS install" | ||||||||
| - CDR collection system is configured (if necessary) | CLI:
Web - "CDR manager" | ||||||||
| 5.3 The routing context has been configured: | Virtual PBX. Telephone calls routing | CLI:
Web - "Routing manager" | |||||||
| - the necessary trunks are configured | If necessary.
Web - "Trunk manager" | ||||||||
| - the necessary bridges are configured | If necessary.
Web - "Bridge manager" | ||||||||
| - routes are processed both in enblock set and overlap modes | CLI:
Web - "Routing manager" | ||||||||
| 5.4 Correct settings of the SIP subscriber(s) have been made: | Virtual PBX. Connecting and configuring SIP subscribers | CLI:
| |||||||
| - subscribers have been created | CLI:
Web - "Subscriber card" | ||||||||
| - a reliable SIP login/password have been installed |
or filter (from shell):
| ||||||||
| - trusted ip is installed | If SIP registration is required without authorization
Web - "Subscriber card" | ||||||||
| - the subscriber has the correct routing context installed | CLI:
or
(select the preferred) Web - "Subscriber card" | ||||||||
| - the correct terminal type is set (basic/smart) | CLI:
(or basic) Web - "Subscriber card" | ||||||||
| - the subscriber has the necessary services activated | CLI:
Web - "Subscriber card" | ||||||||
| 5.5 Setting routing contexts for system interfaces: |
| ||||||||
| - system:ivr is configured | If it is necessary to use the IVR service. In most cases, only the routing context is written:
| ||||||||
| - system:teleconference is configured | If it is necessary to use the Teleconference service. In most cases, only the routing context is written:
|
...