Update options

Using a single server for the SSD does not provide redundancy. Therefore, upgrading to a new version without interrupting traffic is not possible.
There are two ways to upgrade.

The first option is to stop traffic and update PostgreSQL and all ecss packages on the working SSD, then activate the service and start traffic. The advantage of this option is a simple upgrade process. The disadvantage is a longer traffic interruption.

The second option is to perform a complete fresh installation of the OS on a separate host (physical or virtual), and then install the SSD using temporary IP addresses. During the installation, you will also need to copy the databases (Mnesia + PostgreSQL) from the old host to the new one. Once the new SSD is installed, the temporary IP addresses are replaced with those of the old SSD (at this point, the old SSD is disabled) and the MSR files are configured. After this, the new SSD begins serving traffic. The advantage of this option is minimal traffic interruption. The disadvantage is a more complex and time-consuming update procedure.

Select the appropriate option.

/cluster/storage/ds1/licence/list-licence 

/cluster/storage/ds1/licence/list-licence
┌──┬───────────────────┬────────────┬──────┬───────────────────┬────────────────────┬────────────┐
│Id│Creation date(UTC) │   SSW ID   │Active│    Description    │Expiration date(UTC)│ Time left  │
├──┼───────────────────┼────────────┼──────┼───────────────────┼────────────────────┼────────────┤
│1 │31.10.2025 14:16:00│ECSS 010070 │*     │Eltex SC softswitc │31.12.2026 23:59:59 │224d 21h 31m│
│0 │                   │ECSS DEFAULT│      │Default licence    │                    │            │
└──┴───────────────────┴────────────┴──────┴───────────────────┴────────────────────┴────────────┘

/cluster/storage/ds1/licence/list-licence                  
┌──┬───────────────────┬────────────┬──────┬────────────────┬────────────────────┬────────────┐
│Id│Creation date(UTC) │   SSW ID   │Active│  Description   │Expiration date(UTC)│ Time left  │
├──┼───────────────────┼────────────┼──────┼────────────────┼────────────────────┼────────────┤
│1 │02.12.2025 13:51:39│ECSS2000000 │*     │ECSS ELM License│02.12.2026 13:51:39 │364d 11h 47m│
│0 │01.01.1990 00:00:00│ECSS DEFAULT│      │Default licence │                    │            │
└──┴───────────────────┴────────────┴──────┴────────────────┴────────────────────┴────────────┘

If you need the latest billing data, you need to finalize the current CDR and download the CDR files to a remote server:

/domain/test_domain/cdr/make_finalize_cdr 
Created file(s): cdr_20260522_11_51_16_1_c.csv

First option

1. Attention

   Perform a full backup
2. You need to mask all nodes on the server and disable node autostart:
   
   on ecss1

   sudo systemctl mask --now ecss-ds ecss-mycelium ecss-mediator ecss-core ecss-pa-sip ecss-sorm

   
   

   When the attached command is executed, a notification will be displayed.

   Warning: The unit file, source configuration file or drop-ins of ecss-ds.service changed on disk. Run 'systemctl daemon-reload' to reload units.
   Warning: The unit file, source configuration file or drop-ins of ecss-mycelium.service changed on disk. Run 'systemctl daemon-reload' to reload units.
   Warning: The unit file, source configuration file or drop-ins of ecss-mediator.service changed on disk. Run 'systemctl daemon-reload' to reload units.
   Warning: The unit file, source configuration file or drop-ins of ecss-core.service changed on disk. Run 'systemctl daemon-reload' to reload units.
   Warning: The unit file, source configuration file or drop-ins of ecss-pa-sip.service changed on disk. Run 'systemctl daemon-reload' to reload units.

   These messages are not errors. Continue with the procedure.

3. Update the ssw repository:
   
   on ecss1

   sudo sh -c "echo deb [arch=amd64]  http://archive.eltex.org/ssw/jammy/3.18 stable main extras external > /etc/apt/sources.list.d/eltex-ecss10-stable.list"

4. Perform package update:
   
   on ecss1

   sudo apt update

   
   

   If you see this system message:

   W: http://archive.eltex.org/ssw/jammy/3.18/dists/unstable/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

   Run the following command:

   on both hosts

   sudo cp /etc/apt/trusted.gpg /etc/apt/trusted.gpg.d

5. Updating PostgreSQL:
   
   1. Turn off the Docker container:
      
      on ecss2

      sudo docker compose -f /srv/ecss/ecss-postgres-bdr-ssw/docker-compose.container.yml down

      
      
      Example:

       sudo docker compose -f /srv/ecss/ecss-postgres-bdr-ssw/docker-compose.container.yml down
      [+] down 2/2
       ✔ Container ecss-postgres-bdr-ssw-postgres-container-1 Removed                                                                                                                           
       ✔ Network ecss-postgres-bdr-ssw_default                Removed 

   2. Remove the old deb package, since the upgrade option is not supported:
      
      on ecss2

      sudo apt remove ecss-postgres-bdr-ssw

      !!Important!!

      Run remove, not purge, because remove preserves the volumes directory with our database tables.

      
      
      Example:

      sudo apt remove ecss-postgres-bdr-ssw
      Reading package lists... Done
      . . .
      The following packages will be REMOVED:
        ecss-postgres-bdr-ssw
      . . .
      Do you want to continue? [y/n] y
      Deleting ecss-postgres-bdr-ssw (17.1.0.59+ssw) …

   3. Install a new deb package:
      
      on ecss2

      sudo apt install ecss-postgres-bdr-ssw 

      !!IMPORTANT!!

      During installation, you will be asked the same questions as during the initial installation:

      The answers must exactly match those specified in the procedure, otherwise an attempt will be made to create a new database and the installation will fail.

      Question	Reply	Example
      The current IP address of the network interface.	10.0.10.41 (select)
      Install on a cluster? Select <Yes> if the package is installed on a cluster node.	No (select)

      
      
      If the installation is successful, at the stage of raising replication we will see:

      sudo apt install ecss-postgres-bdr-ssw
      . . .
      ==================
       Create databases 
      ==================
      Database ecss_storekeeper_db already exists, skipping...
      Database web_conf already exists, skipping...
      Extension btree_gist already exists, skipping...
      Extension bdr already exists, skipping...
      
      ===================================
       Creating Postgres Exporter Schema 
      ===================================
      Node IP: localhost
      psql:/srv/ecss/ecss-postgres-bdr-ssw/schema.sql:1: NOTICE:  schema "postgres_exporter" already exists, skipping
      CREATE SCHEMA
      GRANT
      CREATE FUNCTION
      CREATE VIEW
      GRANT
      CREATE FUNCTION
      CREATE VIEW
      GRANT
      psql:/srv/ecss/ecss-postgres-bdr-ssw/schema.sql:28: NOTICE:  extension "pg_stat_statements" already exists, skipping
      CREATE EXTENSION
      CREATE FUNCTION
      CREATE VIEW
      GRANT
      . . .
      =======================================================
      =======================================================
       ecss-postgres-bdr-ssw successfully installed/updated! 
      =======================================================
      =======================================================
      
      
      ┏┓┏┓┏┓┏┳┓┏┓┳┓┏┓┏┓  ┳┓┳┓┳┓  ┏┓┏┓┓ ┏
      ┃┃┃┃┗┓ ┃ ┃┓┣┫┣ ┗┓  ┣┫┃┃┣┫  ┗┓┗┓┃┃┃
      ┣┛┗┛┗┛ ┻ ┗┛┛┗┗┛┗┛  ┻┛┻┛┛┗  ┗┛┗┛┗┻┛

   4. After installation, check that the new image has been pulled in and Docker has started by running the command:
      
      on ecss2

      sudo docker ps

      
      
      example:

      sudo docker ps
      CONTAINER ID   IMAGE                                           COMMAND                  CREATED              STATUS              PORTS                                         NAMES
      bf73743d3e09   git.eltex.loc:4567/ecss/ecss-postgresbdr:3.18   "/docker-entrypoint.…"   About a minute ago   Up About a minute   0.0.0.0:5439->5432/tcp, [::]:5439->5432/tcp   ecss-postgres-bdr-ssw-postgres-container-1

6. Updating the ecss-dns-env package:
   
   on ecss1

   sudo apt install ecss-dns-env

   
   After the update, you need to update the configuration by running the command. The answers to the questions are similar to the installation procedure:
   on ecss1

   sudo dpkg-reconfigure ecss-dns-env

7. Update the ecss-user package:
   

   When updating, you need to apply new configuration files (confirm with -Y).

   
   
   on ecss1

   sudo apt install ecss-user

8. Update the ecss-utils package:
   
   on ecss1

   sudo apt install ecss-utils

9. In case of using ELM licensing

   Install the License Provider package:

   on ecss2

   sudo apt install ecss-license-provider

   When installing the ecss-license-provider package the following questions will be asked:

   Questions	Answers	Examples
   License Provider listen ip:	0.0.0.0 (default value)
   License Provider listen port:	4321 (default value)
   Log level:	info (default value), possible options: debug, error, info
   License Provider cluster key:	specify a unique name ecss-lm-cluster (default value) Managers with the same names will attempt to form a cluster for mutual redundancy.
   What services should be restarted?	ecss-license-provider.service (default value)

   The data is saved to the /etc/ecss/ecss-license-provider/config.env file:

   ECSS_LM_HOST=0.0.0.0
   ECSS_LM_PORT=4321
   ECSS_LM_LOG_LEVEL=info
   RELEASE_COOKIE=ecss-abf-lm-cluster

   Configuring License Provider (LP)

   The ecss-license-provider service uses two configuration files: /etc/ecss/ecss-license-provider/config.env and /etc/ecss/ecss-license-provider/config.yaml.

   The information is saved to the config.env file when the ecss-license-provider is installed.

   The config.yaml file contains general settings for connecting to the ELM server and information about licenses: what licenses to take, where to take them from, and where to send them, all this information should be configured manually.

   information in the file after installation

   elm_addresses: []
   licenses: []
   ecss_nodes: []

   To fill out these fields, open the ecss-elm-adapter configuration file used in the version 3.17 /etc/ecss/ecss-elm-adapter/config.env:
   

   on ecss2

   cat /etc/ecss/ecss-elm-adapter/config.env 
   ELM_HOST=elm.eltex-co.ru
   ELM_PORT=8099
   ECSS_PRODUCT_ID=ECSS2000000
   ECSS_LICENSE_KEY=ssw987654
   LOG_LEVEL=info
   LICENCE_FAIL_TIMER_SECONDS=10
   LICENCE_PULL_TIMER_SECONDS=360

   
   

   In the elm_addresses field, you must specify a list of ELM servers to which you want to connect to obtain licenses. First address in the list is used as the main one. Additional lines contain backup addresses.
   Example:
   - "elm.eltex-co.ru:8099"
   - "192.168.111.22:8099"
   - "elm-3.eltex.loc:8099"
   
   Then licenses in the licenses field are specified.

   • The id can be anything, as long as it is unique for each license. It only affects the license address on the License Provider itself (e.g., 0, 1, 2, 3).
   • kind. For SSW, only SSW (in uppercase) is supported.
   • type is set to elm if this license is to be requested from the ELM server. If you need to use an SSW file-based license, set the type to ecss_license.
     • For the elm type, you must specify the license_key and product_id fields to identify the license.
     • For the ecss_license type, specify the license field, which contains the static license key.

   license_key = ECSS_LICENSE_KEY and product_id = ECSS_PRODUCT_ID parameters must match the data previously uploaded to the ELM server.

   ecss_nodes block.

   You must specify the details of the services that will receive the license. A service is defined by three parameters:

   • id - the service identifier. In the case of SSW, this must match the ECSS_ID of the SSW being licensed.
   • kind - the type of service being licensed. As with the licenses block, the SSW and AUP types are supported. For SSW, only the SSW type is supported.
   • license_id - the identifier of the license that will be sent to this service. It corresponds to the license identifiers from the licenses block

   Two SSWs with different ECSS_IDs cannot receive the same license; a configuration with such an assignment will be marked as invalid.
   Additionally, two SSWs with identical ECSS_IDs cannot simultaneously obtain the same license from a single License Provider; therefore, it is extremely important to set your ECSS_ID correctly and ensure it is unique, at least within the scope of the License Provider being used.

   ECSS_ID format.
   It must begin and end with a Latin letter or a digit; periods and dashes may be used within the string.

   [A-Za-z0-9][A-Za-z0-9.-][A-Za-z0-9]

   Example of a config.yaml file based on data from the file

   elm_addresses:
    - "elm.eltex-co.ru:8099"
   licenses:
    - id: 0
      kind: SSW
      type: elm
      license_key: "ssw987654"
      product_id: "ECSS2000000"
   ecss_nodes:
    - id: eltex1.test
      kind: ssw
      license_id: 0

   Restart the ecss-license-provider.service service to up date the configuration from the /etc/ecss/ecss-license-provider/config.yaml file via the following command:

   on both hosts if there is a cluster

   sudo systemctl restart ecss-license-provider.service

10. Update the ecss-node package:
    
    on ecss1

    sudo apt install ecss-node

    During installation, you will be prompted to configure the settings required to generate the configuration files; examples of possible answers are provided below.

    ecss-node questions	Answers for ecss1	Example
    Cookies for the core node:	ecss-core (default value) It is recommended to replace this with a unique value
    Cookies for the ds node:	ecss-ds (default value) It is recommended to replace this with a unique value
    Cookies for the mediator node:	ecss-mediator (default value) It is recommended to replace this with a unique value
    Cookies for the pa-sip node:	ecss-pa-sip (default value) It is recommended to replace this with a unique value
    Cookies for the mycelium node:	ecss-mycelium (default value) It is recommended to replace this with a unique value
    Use the current version of the configuration file?	No (default value)
    When updating, you must apply the new configuration files (confirm with -Y).

11. Enable the nodes.
    Enable the SSW services using the following commands: 
    
    on ecss1

    sudo systemctl unmask ecss-ds ecss-mycelium ecss-mediator ecss-core ecss-pa-sip ecss-sorm

    
    
    on ecss1

    sudo systemctl enable ecss-ds ecss-mycelium ecss-mediator ecss-core ecss-pa-sip ecss-sorm

12. Starting SSW on ecss1. Start the following services:
    ecss-mycelium
    
    on ecss1

    sudo systemctl start ecss-mycelium

    ecss-ds
    
    on ecss1

    sudo systemctl start ecss-ds

    ecss-core
    
    on ecss1

    sudo systemctl start ecss-core

    ecss-mediator
    
    on ecss1

    sudo systemctl start ecss-mediator

    
    

    Do not start PA-SIP yet

13. Check the status of services by running the system-status command in CoCon:
    
    performed in CoCon

    /system-status 
    Checking...
    ┌─┬───────────────┬────────────────────────┬───────────────┬────────────┬──────┐
    │ │     Node      │        Release         │ Erlang nodes  │Mnesia nodes│Uptime│
    ├─┼───────────────┼────────────────────────┼───────────────┼────────────┼──────┤
    │ │core1@ecss1    │ecss-core-3.18.0.271    │core1@ecss1    │not running │14m 4s│
    │ │ds1@ecss1      │ecss-ds-3.18.0.271      │ds1@ecss1      │ds1@ecss1   │14m 4s│
    │ │md1@ecss1      │ecss-mediator-3.18.0.271│md1@ecss1      │md1@ecss1   │14m 4s│
    │ │mycelium1@ecss1│ecss-mycelium-3.18.0.271│mycelium1@ecss1│not running │14m 4s│
    │ │sorm1@ecss1    │ecss-sorm-3.18.0.271    │sorm1@ecss1    │not running │14m 5s│
    └─┴───────────────┴────────────────────────┴───────────────┴────────────┴──────┘
    
    All services are started.
    
      Active media resource selected list specific:
    ┌─────────────┬───────────┬────────────┬───────────┬───────────┐
    │    Node     │    MSR    │    MSR     │ Cc-status │ Cc-uptime │
    │             │           │  version   │           │           │
    ├─────────────┼───────────┼────────────┼───────────┼───────────┤
    │ core1@ecss1 │ msr.ecss1 │ 3.17.1.1.7 │ connected │ 00:43:03  │
    └─────────────┴───────────┴────────────┴───────────┴───────────┘

14. Licensing modes.
    
    If a file-based license is used

    If a file-based license is used

    No additional actions are required.

    /cluster/storage/ds1/licence/list-licence
    ┌──┬───────────────────┬────────────────┬──────┬────────────────────────────────────────────┬────────────────────┬────────────┐
    │Id│Creation date(UTC) │     SSW ID     │Active│                Description                 │Expiration date(UTC)│ Time left  │
    ├──┼───────────────────┼────────────────┼──────┼────────────────────────────────────────────┼────────────────────┼────────────┤
    │1 │31.10.2025 14:16:00│ECSS 010070     │*     │Eltex SC softswitch                         │31.12.2026 23:59:59 │224d 21h 31m│
    │0 │                   │ECSS DEFAULT    │      │Default licence                             │                    │            │
    └──┴───────────────────┴────────────────┴──────┴────────────────────────────────────────────┴────────────────────┴────────────┘

15. If the ELM licensing is used

    Configure the SSW connection to the License Provider using the following command in CoCon (in this example, the License Provider is installed in the ecss1 host, hosts' IPadd is 10.0.10.41. The default port value from the/etc/ecss/ecss-license-provider/config.env file is 4321)

    performed in CoCon

    /system/licence/manager/set --hosts [https://10.0.10.41:4321]

    After execution, check the connection status with the following command:

    performed in CoCon

    /system/licence/manager/show-status
    ┌───────────────────────┬───────┬─────┐
    │         Host          │Current│Alive│
    ├───────────────────────┼───────┼─────┤
    │https://10.0.10.41:4321│*      │true │
    └───────────────────────┴───────┴─────┘

    Teh host should have a status of alive=true and be “current.”  

    • Current - indicates which host the SSW is connected to. If there is a connection, * is displayed; if not, nothing is displayed.
    • Alive - displays the host’s availability status (healthcheck).

    Connecting to the License Manager

    A lack of connection to the License Provider or ELM is equivalent to a lack of access to the token, which will lead to critical failures and a transition to emergency mode; after a certain period, if the connection is not restored, the system will switch to the Default license.

    This behavior applies only when operating in ELM mode.

    If the status for one of the License Provider hosts is shown as “current,” you can send a request to upload the license to the SSW using the following command:

    performed in CoCon

    /cluster/storage/ds1/licence/request

    type=elm

    /cluster/storage/ds1/licence/request      
    Licence received      
    [*******                                                               ] 6s 2ms   
    Success: Licence parameters applied

    type=elm

    /cluster/storage/ds1/licence/list-licence 
    ┌──┬───────────────────┬────────────┬──────┬────────────────┬────────────────────┬────────────────────┬─────────┐
    │Id│Creation date(UTC) │   SSW ID   │Active│  Description   │Comm. Exp. Date(UTC)│Expiration date(UTC)│Time left│
    ├──┼───────────────────┼────────────┼──────┼────────────────┼────────────────────┼────────────────────┼─────────┤
    │1 │14.04.2026 11:18:34│ECSS2000000 │*     │ECSS ELM License│09.04.2027 16:26:34 │06.06.2026 10:49:12 │1d 6h 59m│
    │0 │01.01.1990 00:00:00│ECSS DEFAULT│      │Default licence │                    │                    │         │
    └──┴───────────────────┴────────────┴──────┴────────────────┴────────────────────┴────────────────────┴─────────┘

    
    

16. Updating the ecss-restfs package.
    

    Accept all new configuration files by choosing Y.

    
    
    on ecss1

    sudo apt install ecss-restfs

17. Updating the ecss-media-server package.
    

    The Media Server analyzes the configuration in the files located in the /etc/ecss/ecss-media-server/ directory. Version 3.17 introduces a new feature for managing codec priorities. If, for any reason, multiple files contain a codec section that lists the same codec more than once, a conflict will occur after the update, and the Media Server will not function.

    Therefore, there should be no conflicts regarding codec priorities in the configuration files of a single Media Server (there should be only one entry for one codec, and it should not be repeated in other files). The decision regarding which specific files need to be configured is left to the discretion of the system administrator.

    Perform an update:
    

    Accept all new configuration files by choosing Y.

    
    
    on ecss1

    sudo apt install ecss-media-server

    Update the configuration:
    
    on ecss1

    sudo dpkg-reconfigure ecss-media-server

18. Updating the ecss-media-resources package
    on ecss1

    sudo apt install ecss-media-resources

19. Updating the ecss-web-conf package
    
    on ecss1

    sudo apt install ecss-web-conf

20. Updating optional service packages

    Updating the ecss-teleconference-ui package.

    on ecss1

    sudo apt install ecss-teleconference-ui

    Updating the ecss-crm-server package.

    on ecss1

    sudo apt install ecss-crm-server

    Updating the ecss-cc-ui package.

    on ecss1

    sudo apt install ecss-cc-ui

    Updating the ecss-call-api package.

    on ecss1

    sudo apt install ecss-call-api

    Updating the ecss-peeper-client package.

    on ecss1

    sudo apt install ecss-peeper-client

21. Launch ecss-pa-sip:
    
    on ecss1

    sudo systemctl start ecss-pa-sip

    Check the status of services by running the /system-status command:
    
    performed in CoCon

    /system-status 
    Checking...
    ┌─┬───────────────┬────────────────────────┬───────────────┬────────────┬───────┐
    │ │     Node      │        Release         │ Erlang nodes  │Mnesia nodes│Uptime │
    ├─┼───────────────┼────────────────────────┼───────────────┼────────────┼───────┤
    │ │core1@ecss1    │ecss-core-3.18.0.271    │core1@ecss1    │not running │54m 27s│
    │ │ds1@ecss1      │ecss-ds-3.18.0.271      │ds1@ecss1      │ds1@ecss1   │54m 27s│
    │ │md1@ecss1      │ecss-mediator-3.18.0.271│md1@ecss1      │md1@ecss1   │54m 27s│
    │ │mycelium1@ecss1│ecss-mycelium-3.18.0.271│mycelium1@ecss1│not running │54m 27s│
    │ │sip1@ecss1     │ecss-pa-sip-3.18.0.271  │sip1@ecss1     │sip1@ecss1  │54m 27s│
    │ │sorm1@ecss1    │ecss-sorm-3.18.0.271    │sorm1@ecss1    │not running │54m 27s│
    └─┴───────────────┴────────────────────────┴───────────────┴────────────┴───────┘
    
    All services are started.
    
      Active media resource selected list specific:
    ┌─────────────┬───────────┬──────────┬───────────┬───────────┐
    │    Node     │    MSR    │   MSR    │ Cc-status │ Cc-uptime │
    │             │           │ version  │           │           │
    ├─────────────┼───────────┼──────────┼───────────┼───────────┤
    │ core1@ecss1 │ msr.ecss1 │ 3.18.0.7 │ connected │ 00:01:17  │
    └─────────────┴───────────┴──────────┴───────────┴───────────┘

    Verify that active registrations have been migrated to the updated host. To do this, check the registered subscribers on SSW. Execute the following command in CoCon:
    performed in CoCon

    /domain/test_domain/sip/user/registered sip *            
    450 make users list ...
    [**********************************************************************] 28mks    
    450 users information read ...
    [**********************************************************************] 1ms      
    Executed on the sip1@ecss1
    ┌───────────────┐
    │ elements: 436 │
    └───────────────┘

22. After the update is complete, verify that all SSW services are functioning properly.

Second option

Initial data
Use temporary IP addresses during installation (10.0.10.51/10.0.20.51 in the example). In the final steps, the temporary addresses will be replaced with the actual IP addresses for SSW version 3.17 (10.0.10.41/10.0.20.41 in the example).

Installing the OS

sudo nano /etc/netplan/ecss_netplan.yaml

# Netplan for the ecss1 host of the software switch
# Please note that there must be at least two spaces in every line and section (except for the network section).

network:
  version: 2 # netplan version
  renderer: networkd # netplan configuration renderer
  ethernets: # Section describing Ethernet interfaces
    enp0s3: # Name of the virtual machine’s interface to the Internet
        dhcp4: no # Disable dynamic IP address assignment on interfaces
        dhcp6: no
        addresses: [192.168.56.51/24]
    enp0s8: # Name of the interface for SSW
        dhcp4: no # Disable dynamic IP address assignment on interfaces
        dhcp6: no
  vlans:
    net.10: # Management interface
        id: 10
        link: enp0s3
        addresses: [10.0.10.51/24]
    net.20: # VoIP interface
        id: 20
        link: enp0s8
        addresses: [10.0.20.51/24]

sudo netplan apply

sudo nano /etc/hostname 

127.0.0.1   localhost # Local loopback address, used by some ECSS services
10.0.10.51  ecss1 # Host address

"Optimization" of the operating system

Set the OS settings to performance mode

Use the cpufrequtils utility.

sudo apt install cpufrequtils

By default, after installing Ubuntu, the “ondemand” mode is used (CPU performance is adjusted based on application requests, which saves power but reduces performance):

cat /etc/init.d/cpufrequtils | grep GOVERNOR=

The system output shows that the default mode after installation is “ondemand”:

GOVERNOR="ondemand"

To set the performance mode, in the /etc/init.d/cpufrequtils file, replace ondemand with performance

sudo sed -i 's/GOVERNOR="ondemand"/GOVERNOR="performance"/g' /etc/init.d/cpufrequtils

Restart the utility:

sudo /etc/init.d/cpufrequtils restart 

Then run the following command:

sudo systemctl daemon-reload

Disable SWAP

The Ubuntu SSW server operates in real time, so all necessary data must be stored in RAM; using a swap file (/swap.img) can increase the processing time for SSW ECSS10 application calls, which is unacceptable. Disable swap.
Execute the following three commands one by one:

Disable Swap:

sudo swapoff -a

Delete the swap.img file.

sudo rm /swap.img

Comment out the line — /swap.img none swap sw 0 0 — in the /etc/fstab file by running the sudo nano /etc/fstab command

or change it to # /swap.img none swap sw 0 0

or delete this string (/swap.img none swap sw 0 0)

sudo nano /etc/fstab

To verify, run the free -h command:

free -h

Swap size equals 0, which means it's disabled

free -h
              total        used        free      shared  buff/cache   available
Mem:           3,9G        110M        3,2G        820K        535M        3,5G
Swap:            0B          0B          0B

Setting the timezone

During the installation of Ubuntu 22, you are not prompted to set a time zone (the default is UTC). You must set it manually (to ensure the billing system, scheduled tasks, etc., function correctly), for example:

sudo timedatectl set-timezone Asia/Novosibirsk

Improving the performance of high-load servers

You can improve the performance of high-load servers by increasing the open file limit.

To set the open file limit, do the following:

Check the current limit using the command:

ulimit -a

The output:

eltex@ecss1:~$ ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 15515
max locked memory       (kbytes, -l) 65536
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 15515
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

This limit (open files 1024) is not enough for normal operation of high-load servers.

Set the open file limit for each user:

sudo sed -i  '55i\*                soft    nproc           65536\n*                hard    nproc           131072\n*                soft    nofile          65536\n*                hard    nofile          131072\nroot             -       memlock         unlimited' /etc/security/limits.conf

Updating operating system software

1. To install the ECSS-10 system, you must add the Eltex repository::
   
   on a new ssw

   sudo sh -c "echo 'deb [arch=amd64] http://archive.eltex.org/ssw/jammy/3.18 stable main extras external' > /etc/apt/sources.list.d/eltex-ecss10-stable.list"

   Next, import the key using the following command::

   on a new ssw

   sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 33CB2B750F8BB6A5

   Before the installation, update the OS:

   on a new ssw

   sudo apt update

   If you see the following system message::

   W: http://archive.eltex.org/ssw/jammy/3.18/dists/stable/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

   Run the following command:

   on a new ssw

   sudo cp /etc/apt/trusted.gpg /etc/apt/trusted.gpg.d

   on a new ssw

   sudo apt upgrade

   
   
   

Installing and configuring the software

  ┌ ECSS software version. It is currently listed as 3 in the certification application.. 

  | We will not change it until the next certification or
  │ the release of a fundamentally new version of the system.
  │
  │     ┌ System Release version. The common version for all components included in a specific release. 

  |     | We change it centrally when
  │     │ we decide to release a new version. Releases are typically not compatible with one another.
┌─┴┐ ┌──┴─┐
ECSS.SysRel.SubMaj.SubMin
            └──┬─┘ └──┬─┘
               │      └ Subsystem minor version. The subsystem minor version is set by the subsystem developer. 

               |        The minor version
               │        is updated when a patch is added. As a rule, minor versions within a single major version 
               │        are compatible with each other and differ only within specific patches.
               │
               └ Subsystem major version. The major version is set by the subsystem developer. 

                 The subsystem’s major version must be changed when significant changes are made to the subsystem.

Install all the offered packages:

sudo apt install ntp ntpdate tcpdump vlan dnsmasq aptitude atop ethtool htop iotop mc minicom mtr-tiny nmap pptpd pv screen ssh tftpd vim sngrep tshark cpanminus gnuplot libgraph-easy-perl debconf-utils wget rsync ncdu

sudo apt install ntp tcpdump vlan dnsmasq

sudo apt install aptitude atop ethtool htop mc screen ssh tftpd sngrep tshark gnuplot libgraph-easy-perl debconf-utils iotop ncdu

Configuring the ecss-dns-env package

Execute the following command:

sudo apt install -y ecss-dns-env

The configurator will prompt you to select the sections to configure based on the questions below. Select a broker. (For example, 10.0.10.51).

sudo dpkg-reconfigure ecss-dns-env

Installing Postgres

sudo install -m 0755 -d /etc/apt/keyrings

sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc

sudo chmod a+r /etc/apt/keyrings/docker.asc

sudo sh -c "echo 'deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu   jammy stable' >> /etc/apt/sources.list.d/docker.list"

sudo apt update && sudo apt upgrade

Installing the ecss-postgres-bdr-ssw package

Install the ecss-postgres-bdr-ssw package:

sudo apt install ecss-postgres-bdr-ssw

When configuring the ecss-postgres-bdr-ssw package, the following questions will be asked:

. . .
==================
 Create databases 
==================
CREATE DATABASE
CREATE DATABASE
CREATE EXTENSION
CREATE EXTENSION
===================================
 Creating Postgres Exporter Schema 
===================================
Node IP: localhost
CREATE SCHEMA
GRANT
CREATE FUNCTION
CREATE VIEW
GRANT
CREATE FUNCTION
CREATE VIEW
GRANT
CREATE EXTENSION
CREATE FUNCTION
CREATE VIEW
GRANT
=======================================================
=======================================================
 ecss-postgres-bdr-ssw successfully installed/updated! 
=======================================================
=======================================================
┏┓┏┓┏┓┏┳┓┏┓┳┓┏┓┏┓  ┳┓┳┓┳┓  ┏┓┏┓┓ ┏
┃┃┃┃┗┓ ┃ ┃┓┣┫┣ ┗┓  ┣┫┃┃┣┫  ┗┓┗┓┃┃┃
┣┛┗┛┗┛ ┻ ┗┛┛┗┗┛┗┛  ┻┛┻┛┛┗  ┗┛┗┛┗┻┛

sudo apt install ecss-license-provider

ECSS_LM_HOST=0.0.0.0
ECSS_LM_PORT=4321
ECSS_LM_LOG_LEVEL=info
RELEASE_COOKIE=ecss-abf-lm-cluster

elm_addresses: []
licenses: []
ecss_nodes: []

cat /etc/ecss/ecss-elm-adapter/config.env 
ELM_HOST=elm.eltex-co.ru
ELM_PORT=8099
ECSS_PRODUCT_ID=ECSS2000000
ECSS_LICENSE_KEY=ssw987654
LOG_LEVEL=info
LICENCE_FAIL_TIMER_SECONDS=10
LICENCE_PULL_TIMER_SECONDS=360

[A-Za-z0-9][A-Za-z0-9.-][A-Za-z0-9]

elm_addresses:
 - "elm.eltex-co.ru:8099"
licenses:
 - id: 0
   kind: SSW
   type: elm
   license_key: "ssw987654"
   product_id: "ECSS2000000"
ecss_nodes:
 - id: test.update
   kind: ssw
   license_id: 0

sudo systemctl restart ecss-license-provider.service

Installing ecss-node

Installing the required ecss-node package includes the installation and initial configuration of the core subsystems.

To install the ecss-node package, run the following command:

sudo apt install -y ecss-node

During installation, a user named ssw is created, under whose account all ecss* services are run. The necessary directories are created, DNS configuration is performed, and SSL certificates are configured.

During installation, you will be prompted to configure the parameters needed to generate the configuration files; examples of responses are provided below.

[A-Za-z0-9][A-Za-z0-9.-][A-Za-z0-9]

To check the NTP synchronization status, use the `ntpq -p` command. If you use the additional `-n` option, the IP address will be displayed instead of the server name:

ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*185.125.190.56  17.253.28.253    2 u   45   64    1   83.893   +0.470   2.177

Stop the following services::

sudo systemctl stop ecss-core ecss-pa-sip ecss-ds ecss-mediator ecss-mycelium

Create a backup for oasys (Copy Mnesia database from old to new ecss1), run the following commands:

cd /var/lib/ecss/oasys/

sudo rsync -a <Your_user>@<IP_add_of_an_old_server>:/var/lib/ecss/oasys/Mnesia.ds1@ecss1/ Mnesia.ds1@ecss1/

sudo rsync -a <Your_user>@<IP_add_of_an_old_server>:/var/lib/ecss/oasys/Mnesia.md1@ecss1/ Mnesia.md1@ecss1/

cd ~

Restart the SSW services:

sudo systemctl restart ecss-core ecss-pa-sip ecss-ds ecss-mediator ecss-mycelium

To check the status of the services, run the system-status command in CoCon:

/system-status 
Checking...
┌─┬───────────────┬─────────────────────────┬───────────────┬────────────┬──────┐
│ │     Node      │         Release         │ Erlang nodes  │Mnesia nodes│Uptime│
├─┼───────────────┼─────────────────────────┼───────────────┼────────────┼──────┤
│ │core1@ecss1    │ecss-core-3.18.0.271     │core1@ecss1    │not running │3m 55s│
│ │ds1@ecss1      │ecss-ds-3.18.0.271       │ds1@ecss1      │ds1@ecss1   │4m 40s│
│ │md1@ecss1      │ecss-mediator-3.18.0.271 │md1@ecss1      │md1@ecss1   │3m 50s│
│ │mycelium1@ecss1│ecss-mycelium-3.18.0.271 │mycelium1@ecss1│not running │5m 28s│
│ │sip1@ecss1     │ecss-pa-sip-3.18.0.271   │sip1@ecss1     │sip1@ecss1  │3m 45s│
│ │sorm1@ecss1    │ecss-sorm-3.18.0.271     │sorm1@ecss1    │not running │1m 55s│
└─┴───────────────┴─────────────────────────┴───────────────┴────────────┴──────┘

Licensing modes.

File-based licensing

/cluster/storage/ds1/licence/list-licence
┌──┬───────────────────┬────────────────┬──────┬────────────────────────────────────────────┬────────────────────┬────────────┐
│Id│Creation date(UTC) │     SSW ID     │Active│                Description                 │Expiration date(UTC)│ Time left  │
├──┼───────────────────┼────────────────┼──────┼────────────────────────────────────────────┼────────────────────┼────────────┤
│1 │31.10.2025 14:16:00│ECSS 010070     │*     │Eltex SC softswitch                         │31.12.2026 23:59:59 │224d 21h 31m│
│0 │                   │ECSS DEFAULT    │      │Default licence                             │                    │            │
└──┴───────────────────┴────────────────┴──────┴────────────────────────────────────────────┴────────────────────┴────────────┘

ELM service licensing

/system/licence/manager/set --hosts [https://10.0.10.51:4321]

/system/licence/manager/show-status
┌───────────────────────┬───────┬─────┐
│         Host          │Current│Alive│
├───────────────────────┼───────┼─────┤
│https://10.0.10.51:4321│*      │true │
└───────────────────────┴───────┴─────┘

/cluster/storage/ds1/licence/request

/cluster/storage/ds1/licence/request      
Licence received      
[*******                                                               ] 6s 2ms   
Success: Licence parameters applied

/cluster/storage/ds1/licence/list-licence 
┌──┬───────────────────┬────────────┬──────┬────────────────┬────────────────────┬────────────────────┬─────────┐
│Id│Creation date(UTC) │   SSW ID   │Active│  Description   │Comm. Exp. Date(UTC)│Expiration date(UTC)│Time left│
├──┼───────────────────┼────────────┼──────┼────────────────┼────────────────────┼────────────────────┼─────────┤
│1 │14.04.2026 11:18:34│ECSS2000000 │*     │ECSS ELM License│09.04.2027 16:26:34 │06.06.2026 10:49:12 │1d 6h 59m│
│0 │01.01.1990 00:00:00│ECSS DEFAULT│      │Default licence │                    │                    │         │
└──┴───────────────────┴────────────┴──────┴────────────────┴────────────────────┴────────────────────┴─────────┘

Installing ecss-restfs, ecss-media-server, ecss-web-conf packages

Next, install the ecss-restf package, followed by ecss-media-server, ecss-media-resources, ecss-web-conf, and others in any order:

ecss-restfs

sudo apt install -y ecss-restfs

Installing ecss-restfs.  

When installing the ecss-restfs package, you will be prompted to specify configuration options. The answers to these questions are provided below.

After installing the ecss-restfs package, check for the presence of the voice guide’s WAV files in the /var/lib/ecss/restfs/system/sounds/ directory using the command:

ll /var/lib/ecss/restfs/system/sounds/

The presence of WAV files in the directory specified above indicates that the ecss-restfs package was installed correctly

sudo apt --fix-broken install 

ll /var/lib/ecss/restfs/system/sounds/

Next, you need to make sure that these files are accessible from outside. To do so, run the following command: Installing ecss-restfs.

wget http://ecss1:9990/system/sounds/ai_you.wav

wget http://ecss1:9990/system/sounds/ai_you.wav
--2026-04-18 17:43:29--  http://ecss1:9990/system/sounds/ai_you.wav
Resolving ecss1 (ecss1)... 127.0.1.1, 10.0.10.51
Connecting to ecss1 (ecss1)|127.0.1.1|:9990... connected.
HTTP request sent, awaiting response... 200 OK
Length: 11670 (11K) [audio/x-wav]
Saving to: ‘ai_you.wav’

ai_you.wav                                  100%[========================================================================================>]  11,40K  --.-KB/s    in 0s      

2026-04-18 17:43:29 (301 MB/s) - ‘ai_you.wav’ saved [11670/11670]

You can delete the test file

rm ai_you.wav

Transfer the call recordings from the old server to the new one by running the following command:

sudo rsync -a <your_user>@<IP_add_of_an_old_ecss1>:/var/lib/ecss/restfs/domain/ /var/lib/ecss/restfs/domain/

abf@ecss1:/var/lib/ecss/restfs/domain$ ls -la /var/lib/ecss/restfs/domain
8 total
drwxr-xr-x 2 www-data www-data 4096 apr 22 18:21 .
drwxr-xr-x 7 www-data www-data 4096 may 28 15:07 ..

abf@ecss1:/var/lib/ecss/restfs/domain$ sudo rsync -a abf@10.0.10.10:/var/lib/ecss/restfs/domain/ /var/lib/ecss/restfs/domain/

abf@ecss1:/var/lib/ecss/restfs/domain$ ls -la test_domain/records/2026_05_28
610 total
drwxrwxrwx 2 www-data www-data  4096 may 28 14:56 .
drwxrwxrwx 3 www-data www-data  4096 may 28 14:27 ..
-rw-r--r-- 1 www-data www-data 71892 may 28 14:27 2026-05-28_14-27-02_t_42009-42007.pcm
-rw-rw-rw- 1 www-data www-data    86 may 28 14:27 2026-05-28_14-27-02_t_42009-42007.pcm.meta
-rw-r--r-- 1 www-data www-data 71892 may 28 14:31 2026-05-28_14-31-19_o_42007-42009.pcm
-rw-rw-rw- 1 www-data www-data    86 may 28 14:31 2026-05-28_14-31-19_o_42007-42009.pcm.meta
-rw-r--r-- 1 www-data www-data 63904 may 28 14:55 2026-05-28_14-55-24_o_42007-42009.pcm
-rw-rw-rw- 1 www-data www-data    86 may 28 14:55 2026-05-28_14-55-24_o_42007-42009.pcm.meta
-rw-r--r-- 1 www-data www-data 39940 may 28 14:55 2026-05-28_14-55-31_o_42007-42009.pcm
-rw-rw-rw- 1 www-data www-data    86 may 28 14:55 2026-05-28_14-55-31_o_42007-42009.pcm.meta
-rw-r--r-- 1 www-data www-data 15976 may 28 14:55 2026-05-28_14-55-37_o_42007-42009.pcm
-rw-rw-rw- 1 www-data www-data    86 may 28 14:55 2026-05-28_14-55-37_o_42007-42009.pcm.meta
-rw-r--r-- 1 www-data www-data 79880 may 28 14:55 2026-05-28_14-55-48_o_42007-42009.pcm
-rw-rw-rw- 1 www-data www-data    86 may 28 14:55 2026-05-28_14-55-48_o_42007-42009.pcm.meta
-rw-r--r-- 1 www-data www-data 55916 may 28 14:56 2026-05-28_14-55-59_o_42007-42009.pcm
-rw-rw-rw- 1 www-data www-data    86 may 28 14:55 2026-05-28_14-55-59_o_42007-42009.pcm.meta
-rw-r--r-- 1 www-data www-data 47928 may 28 14:56 2026-05-28_14-56-04_o_42007-42009.pcm
-rw-rw-rw- 1 www-data www-data    86 may 28 14:56 2026-05-28_14-56-04_o_42007-42009.pcm.meta
-rw-r--r-- 1 www-data www-data 31952 may 28 14:56 2026-05-28_14-56-28_t_42009-42007.pcm
-rw-rw-rw- 1 www-data www-data    86 may 28 14:56 2026-05-28_14-56-28_t_42009-42007.pcm.meta
-rw-r--r-- 1 www-data www-data 31952 may 28 14:56 2026-05-28_14-56-37_t_42009-42007.pcm
-rw-rw-rw- 1 www-data www-data    86 may 28 14:56 2026-05-28_14-56-37_t_42009-42007.pcm.meta
-rw-r--r-- 1 www-data www-data 95856 may 28 14:56 2026-05-28_14-56-42_t_42009-42007.pcm
-rw-rw-rw- 1 www-data www-data    86 may 28 14:56 2026-05-28_14-56-42_t_42009-42007.pcm.meta

ecss-media-server

sudo apt install -y ecss-media-server

For the media server (ecss-media-server/MSR), you can perform the initial setup by writing the parameters to a configuration file, 
to do this, you need to configure transport bind-addr, mcc bind-address:
Specify the IP address of the old SSW version 3.17 (10.0.20.41 in the example).

After generating the default configurations, run the following check:

cat /etc/ecss/ecss-media-server/config.xml

Inside is the configuration for msr: config.xml; in the conf.d directory is the default.xml configuration.

Essentially, default.xml is an extension of config.xml that defines the accounts section. This is done to ensure that this configuration remains unchanged after package updates.

<?xml version="1.0" encoding="utf-8"?>
<config date="09:24:23 03.12.2025">
  <general log-level="3" log-rotate="yes" max-calls="2148" max-vid-calls="100" max-in-group="512" load-sensor="media" load-delta="10" calls-delta="100" spool-dir-size="100M" log-name="msr.log" log-path="/var/log/ecss/media-server" use-srtp="disabled" enable-ice-transport="no" ice-update="no" aggressive-ice="yes" stun-server="" suspicious-mode="no"/>
  <transport bind-addr="10.0.20.41" port="5040" transport="udp+tcp"/>
  <!-- By default configured public TURN-server -->
  <turn-server use-turn="no" host="numb.viagenie.ca" user="webrtc@live.com" password="muazkh"/>
  <media mixer-clock-rate="8000" use-vad="no" cng-level="0" jb-size="60" rtcp-timeout="0" rtp-timeout="350" udp-src-check="no" cn-multiplier="3" port-start="12000" port-range="4496" tias-in-sdp="no" thread-cnt="2" vid-enc-threads="2" vid-dec-threads="2" video-conf-layout="evenly" keyframe-interval="1000" vid-decode-delay="100" silent-codec-switch="yes" silence-threshold="-30" dtmf-flash-disable="no" video-dscp="0" other-dscp="0" dummy-video-src="/usr/share/ecss-media-server/video/dummy_video.yuv" video-enc-width="640" video-enc-height="360" finalsilence="1000" rtcp-stat-dump="yes" dtmf-tg-fpc-loop="10" dtmf-tg-fit="1" dtmf-tg-fot="2" dtmf-tg-volume="12288"/>
  <codec pcma="1" pcmu="2" ilbc="0" gsm="0" g722="3" g726="0" g729="0" speex="0" l16="0" g7221="0" opus="0" h264="1" h263-1998="2" t38="1" tel-event-pt="0"/>
  <accounts>
    <!-- <dynamic msr_name="msr.name"
            realm="sip:127.0.0.1:5000"
            dtmf_mode="rfc+inband+info"
            auth_name="user"
            auth_password="password" /> -->
  </accounts>
  <pbyte>
    <mcc bind-addr="10.0.20.41" port="5700"/>
  </pbyte>
  <conf_dir path="/etc/ecss/ecss-media-server/conf.d"/>
  <metrics enable="yes" use-pushgateway="yes" pushgateway-addr="127.0.0.1:9091" push-interval="5" port="8100" msr_name="msr2"/>
  <rtp>
    <auto addr-v4=""/>
  </rtp>
</config>

By default, after installation, ECSS-10 enables only the following codecs: pcma, pcmu, g722, h264, h263-1998, and t38. The rest have a status of 0 (disabled). If you want to enable the remaining codecs, use the nano editor to change the priority from 0 to the desired priority number (the priority level must not be duplicated for the audio/video/fax service).
sudo nano /etc/ecss/ecss-media-server/config.xml

Take a look at the accounts section (the default.xml file):

cat /etc/ecss/ecss-media-server/conf.d/default.xml

Check the correctness of the data.

<?xml version="1.0"?>
<config>
    <accounts>
        <dynamic msr_name="msr.ecss1" realm="sip:10.0.20.41:5000" dtmf_mode="rfc+inband+info" auth_name="user" auth_password="password">
            <via dynamic-ifaces="no">
                <iface name="net.20" ip="10.0.20.41"/>
            </via>
        </dynamic>
    </accounts>
</config>

It specifies the current settings used to register the MSR on the core.

The main parameters here are msr_name and realm:

• msr_name — a parameter that defines the name of the MSR. (it is recommended to specify the MSR name and the host it belongs to, for example, msr.ecss1);
• realm — specifies the address for registration on the core. The default entry point is port 5000, address 127.0.0.1.

After modifying the /etc/ecss/ecss-media-server/config.xml and /etc/ecss/ecss-media-server/conf.d/default.xml configuration files, you should restart the ecss-media-server service for the changes to take effect using the following command:

sudo systemctl restart ecss-media-server

ecss-web-conf

sudo apt install ecss-web-conf

The web configurator makes system management more intuitive and convenient. Installing the web configurator is not required, but it is recommended.
Additionally, installing the ecss-web-conf package automatically installs the ecss-subscriber-portal-ui package. The ECSS-10 system’s “Subscriber Portal” application allows system subscribers to independently manage services, view information on completed calls and active conferences, and configure their own IVR scripts for incoming calls.

Check whether you can connect to the web interface at http://10.0.10.51; the username and password are admin/password. Not all features will be available at this time, but the web interface should work, and you should be able to log in successfully.

Disabling SSW version 3.17

To disable the old SSW version 3.17, run the following commands:
Stopping services

sudo systemctl mask --now ecss-ds ecss-mycelium ecss-mediator ecss-core ecss-pa-sip ecss-sorm

Copying the Postgres database

Copy the Postgres database from the old ecss1 server by running the following command:

sudo tar -Pcvf /tmp/postgres.tar /srv/ecss/ecss-postgres-bdr-ssw/volumes/

Copy postgres.tar to the new server by running the following command:

 scp /tmp/postgres.tar <your_user>@<IP_address_of_a_new_ecss1>:/tmp/postgres.tar

Stop the Postgres database Docker with the following command:

sudo docker compose -f /srv/ecss/ecss-postgres-bdr-ssw/docker-compose.container.yml stop

Clear the /srv/ecss/ecss-postgres-bdr-ssw/volumes subdirectory:

sudo rm -R /srv/ecss/ecss-postgres-bdr-ssw/volumes/*

Extract the Postgres database on the new ecss1 server.

sudo tar xvf /tmp/postgres.tar -C / 

Start the Postgres database Docker with the following command:

sudo docker compose -f /srv/ecss/ecss-postgres-bdr-ssw/docker-compose.container.yml start

Replacing IP addresses on the old ecss1

Change the 10.0.10.41/10.0.20.41 IP addresses to the ones that aren't used in the network (10.0.10.61/10.0.20.61, for example):

sudo nano /etc/netplan/ecss.yaml

network:
  version: 2
  renderer: networkd
  ethernets:
    enp0s3: # Name of a virtual machine interface connected to internet
        dhcp4: yes
        dhcp6: no
    enp0s8: # Name of an interface for SSW
        dhcp4: no # Disable dynamic IP address assignment on the interfaces
        dhcp6: no
        addresses: [192.168.56.41/24]
  vlans:
    net.10: # Management interface
        id: 10
        link: enp0s8
        addresses: [10.0.10.41/24]
        nameservers:
          addresses: [127.0.0.1, 8.8.8.8] # Addresses of DNS servers
    net.20: # Interface for VoIP
        id: 20
        link: enp0s8
        addresses: [10.0.20.41/24]
        routes:
        - to: 10.0.20.128/25
          via: 10.0.20.35

network:
  version: 2
  renderer: networkd
  ethernets:
    enp0s3: # Name of a virtual machine interface connected to internet
        dhcp4: yes
        dhcp6: no
    enp0s8: # Name of an interface for SSW
        dhcp4: no # Disable dynamic IP address assignment on the interfaces
        dhcp6: no
        addresses: [192.168.56.61/24]
  vlans:
    net.10: # Management interface
        id: 10
        link: enp0s8
        addresses: [10.0.10.61/24]
        nameservers:
          addresses: [127.0.0.1, 8.8.8.8] # Addresses of DNS servers
    net.20: # Interface for VoIP
        id: 20
        link: enp0s8
        addresses: [10.0.20.61/24]
        routes:
        - to: 10.0.20.128/25
          via: 10.0.20.35

sudo netplan apply

Switching the new SSW to operational IP addresses

Once the operational IP addresses have been removed from the old SSW, you can assign them to the new SSW. Run the following command:

sudo nano /etc/netplan/ecss.yaml

Change the IP addresses 10.0.10.51/10.0.20.51 to those used on the network for the SSW (in the example, 10.0.10.41/10.0.20.41):

network:
  version: 2
  renderer: networkd
  ethernets:
    enp0s3: # Name of a virtual machine interface connected to internet
        dhcp4: yes
        dhcp6: no
    enp0s8: # Name of an interface for SSW
        dhcp4: no # Disable dynamic IP address assignment on the interfaces
        dhcp6: no
        addresses: [192.168.56.51/24]
  vlans:
    net.10: # Management interface
        id: 10
        link: enp0s8
        addresses: [10.0.10.51/24]
        nameservers:
          addresses: [127.0.0.1, 8.8.8.8] # Addresses of DNS servers
    net.20: # Interface for VoIP
        id: 20
        link: enp0s8
        addresses: [10.0.20.51/24]
        routes:
        - to: 10.0.20.128/25
          via: 10.0.20.35

network:
  version: 2
  renderer: networkd
  ethernets:
    enp0s3: # Name of a virtual machine interface connected to internet
        dhcp4: yes
        dhcp6: no
    enp0s8: # Name of an interface for SSW
        dhcp4: no # Disable dynamic IP address assignment on the interfaces
        dhcp6: no
        addresses: [192.168.56.41/24]
  vlans:
    net.10: # Management interface
        id: 10
        link: enp0s8
        addresses: [10.0.10.41/24]
        nameservers:
          addresses: [127.0.0.1, 8.8.8.8] # Addresses of DNS servers
    net.20: # Interface for VoIP
        id: 20
        link: enp0s8
        addresses: [10.0.20.41/24]
        routes:
        - to: 10.0.20.128/25
          via: 10.0.20.35

sudo netplan apply

Update an IP address in the /etc/hosts file:

sudo nano /etc/hosts

Update an IP address in the /etc/dnsmasq.d/ecss-broker file:

sudo dpkg-reconfigure ecss-dns-env

/system/licence/manager/set --hosts [https://10.0.10.41:4321]

sudo systemctl restart ecss-ds ecss-mycelium ecss-mediator ecss-core ecss-pa-sip ecss-media-server

After the update is complete, verify that all SSW services are functioning properly.