Initial data

According to the technical specification, it is required to determine the hardware platform.

Example of drafting hardware requirements

After determining the requirements of the project, create a preliminary network map.

An example of components allocation in the address space for a single node:

Connecting to network

The topology of connecting the server to the network to ensure redundancy is recommended to be done using 2 switches.

Figure 1 — Network connection diagram

Option 1. Active-backup

The switches are connected in erps ring.

All 4 physical network interfaces are connected into 1 aggregated link (bond). Server port aggregation is configured in active-backup mode, i.e. there is always only 1 network interface in operation. Server network interfaces are connected in pairs in switches, on which port aggregation (port-channel) is also configured in active-backup mode.

For example, eth0 and eth1 are connected in the first switch, and eth2 and eth3 are connected in the second.

Option 2. LACP

The switches are connected in a stack. The stack must logically operate as a single switch, capable of providing port aggregation between different physical switches in LACP mode. MES-3124 with specialized firmware can be an example. 

All 4 physical network interfaces are connected into 1 aggregated link (bond). Server port aggregation is configured in 802.3ad mode. Network cards aggregated groups with same rate and duplex are created. With such a combination, the transmission uses all channels in active aggregation according to the IEEE 802.3ad standard. The choice on which interface to send a packet is determined by policy. By default, it is XOR policy, also xmit_hash policy can be used. For more information, see Netplan section. 

Requirements:

• Ethtool support in driver to obtain information about speed and duplex on each network interface;
• IEEE802.3ad standard support on switch. 

Server network interfaces are also included in pairs in switches, on which port aggregation (port-channel) is configured in LACP mode. For example, eth0 and eth1 are included to first switch (port-channel 1), and eth2 and eth3 — to the second (port-channel 2).

Installation of ECSS-10 on one server

Installation of ECSS-10 consists of two main parts:

1. Preparation: installation of Ubuntu 22.04, Ubuntu packets updating, OS "optimization", installation of additional software packages, preparation of network interfaces, /etc/hosts, ssh-keygen
2. Installation of ECSS-10 

Preparation

This section describes the operating system installation, as well as required and optional packages. ECSS-10 version 3.18 runs on Ubuntu 22.04.

Preliminary requirements:

• Installation media with the operating system distribution;
• A prepared server with an updated BIOS, ILP (if available), and a connected network for internet access;
• Setting the installation media (USB flash drive or CD/DVD) as the first boot priority in the BIOS;
• Sufficient disk space and memory as specified in the design.

OS installation

To install the OS, do the following:

• After booting from the installation media, select "Install Ubuntu Server"
• Select the system language and keyboard layout
• Configure the network interface to connect to the Internet
• Create disk partitions according to Table 1
• Configure server and user names
• Install OpenSSH server
• Reboot the successfully installed OS

An option for storing information in a file system on physical media for servers

The system requires at least 256 GB of free space.

It is neccessary to configure "hostname" parameter on the system servers.

It is recommended to specify the same username (anything except ssw) on all servers in the system. The ECSS-10 license is linked to the eToken/ruToken key and the computer hostname. The system user ssw is created when installing the ecss-user package.

Configuring network

Install the software switch according to the parameters specified in the technical specification. In this example, it is assumed that the required operating system is already installed. 

It is recommended to split traffic used for different purposes. For example, management traffic and VoIP traffic. To do this, 2 or more VLANs are created. In the minimum case and with a small load, one VLAN can be enough. Hovewer, it will cause inconvenience in the future at traffic dump and its analysis. According to the technical specification, host IP adresses, gateways, DNS, routing and other parameters are configured on VLAN. 
According to the technical specification, the following addresses are used in a given example:

• 10.0.10.41/24 — for management, vlan 10;
• 10.0.20.41/24 — for VoIP.

There is an address structure inside the server platform and internal addresses are used for interaction between subsystems (nodes) in the cluster. For example, the internal address for a cluster on one server is 127.0.0.1, while the kernel (ecss-core) interacts with the multimedia data processing server (ecss-media-server). Their interaction takes place using the same address, but each software part has its own transport port: ecss-core — 5000, ecss-msr — 5040.

A single address for accessing the MySQL database is defined for all cluster nodes, for example, the ecss-mysql address 127.0.0.1. Thus, the uniformity condition is fulfilled, in which all cluster nodes have completely identical data about the current state of the dynamic components of the software switch (for example, call history).

Preparing system network interfaces

According to the technical specification, the system has 4 network interfaces. Information about their status can be viewed using the ifconfig or ip a command:

First, the network interfaces are configured. Ubuntu18 uses the netplan utility to configure.

This utility is meant for configuring the network and then uploading it to the system using the network manager networkd or NetworkManager.

sudo nano /etc/netplan/ecss_netplan.yaml

In the configurations for each host, first of all, declare the ethernets section, which describes existing in the system Ethernet interfaces that will be used in the future. It is important to disable the use of dynamic address allocation (DHCP) for each interface.

Optionally, gateways for communication with the outside world and DNS server addresses are defined, as well as IP addresses for each interface.

Example of configuring ecss-netplan.yaml file for active-backup connection option:

# Netplan for the ecss1 host of the software switch
# Pay attention to the mandatory presence of at least two spaces in each line and section (except for the network section line)

network:
  version: 2 # netplan version
  renderer: networkd # netplan configuration executor
  ethernets: # Ethernet interfaces description section
     enp0s3: # Name of the VM interface to the internet
        dhcp4: no # Disabling dynamic distribution of IP address on the interfaces
        dhcp6: no
        addresses: [192.168.56.41/24]
     enp0s8: # interface name for SSW
        dhcp4: no #  Disabling dynamic distribution of IP address on the interfaces
        dhcp6: no
  vlans:
    net.10: # Management interface
        id: 10
        link: enp0s3
        addresses: [10.0.10.41/24]
   net.20: # interface for VoIP
      id: 20
      link: enp0s8
      addresses: [10.0.20.41/24]

The following bond settings are required for the ECSS server to run correctly:

mode: active-backup - specifies the operating mode in which one link is selected as active, while the others remain in backup;
primary-reselect-policy: failure - specifies that a new active link should be selected only when the current active link fails. This avoids unnecessary switching;
gratuitous-arp: 5 - when the active link changes, five gratuitous ARP requests are sent to the switch to update its switching table. This facilitates faster switching;
all-slaves-active: true - forces incoming frames to be accepted on the backup interfaces. This ensures that traffic balancing on the MES does not interfere with operation. Data flows to the server from all links, and the server sends data only from the active link;
mii-monitor-interval: 100 - enables link monitoring via the MII interface and specifies a polling interval of 100 ms;
up-delay: 1000 - specifies that a connected interface should not be considered immediately available for operation, but rather a one-second delay should be applied after the interface has been connected. This is necessary to avoid unnecessary switching when the port repeatedly switches between the "on" and "off" states.

Apply parameters with the command:

sudo netplan apply

It is neccessary to configure "hostname" parameter on the system servers.

It is recommended to specify the same username (anything except ssw) on all servers in the system. The ECSS-10 license is linked to the eToken/ruToken key and the computer hostname. The system user ssw is created when installing the ecss-user package.

Specify hostname: ecss1 in file /etc/hostname:

sudo nano /etc/hostname 

Specify real IP address and host name (for example 10.0.20.41 ecss1) in file /etc/hosts:

127.0.0.1   localhost # Local loopback address, used by some ecss services
10.0.20.41  ecss1 # Host address

Optimization of the operating system

Set OS settings to performance mode

Use cpufrequtils utility.

sudo apt install cpufrequtils

By default, after installation, Ubuntu uses the "ondemand" mode (CPU performance is based on application requests, saving power, but lower performance):

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

In the system output message, the default operating mode after installation is "ondemand":

GOVERNOR="ondemand"

Set the efficiency/performance mode - replace the value "ondemand" with "performance" in the file /etc/init.d/cpufrequtils.

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 command:

sudo systemctl daemon-reload

Disable SWAP

The Ubuntu SSW server operates in real time, so all necessary data must be in RAM. Using a swap file (/swap.img) can increase the processing time of ECSS10 SSW application calls, which is unacceptable. Disable swap.

Run three commands in sequence:

Disable swap:

sudo swapoff -a

Delete swap.img file.

sudo rm /swap.img

Comment out the line "/swap.img none swap sw 0 0" in the "/etc/fstab" file – change it to "# /swap.img none swap sw 0 0"

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

sudo nano /etc/fstab

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda2 during curtin installation
/dev/disk/by-uuid/731728e2-4d6b-499a-afea-9362fd6726b2 / ext4 defaults 0 1

To check, run the command free -h:

free -h

Swap size is 0 – that is, it is 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 time zone

When installing Ubuntu 22, it is not prompted to set a time zone (UTC is the default). One should set it manually (for the rating system, scheduled tasks, etc.) to function correctly. For example:

sudo timedatectl set-timezone Asia/Novosibirsk

Improving the performance of high-load servers

It is possible to improve the performance of high-load servers by increasing the open file limit.

To set the open file limit, follow these steps:

Check the current limit with the command:

ulimit -a

Result:

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 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

Operating system software update

Add the ELTEX repository to install the ECSS-10 system:

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 with the following command:

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

Before starting the installation, update the OS:

sudo apt update
sudo apt upgrade

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.

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

sudo apt upgrade

Software installation and configuration

  ┌ ECSS software version. Currently, it is listed as version 3 in the certification application.

  | It is not changed until the next certification or
  │ the release of a fundamentally new version of the system.
  │
  │     ┌ System Release Version. This is the common version for all components included in a specific release. 

  |     | It is changed centrally
  │     │ when decided to launch a new release. Releases are usually not compatible with each other.
┌─┴┐ ┌──┴─┐
ECSS.SysRel.SubMaj.SubMin
            └──┬─┘ └──┬─┘
               │      └ Subsystem minor version. The minor version of a subsystem is set by the subsystem developer.

               |        The minor version 
               │        is changed when a patch is added. Minor versions within a single major version are generally  
               │        compatible with each other and differ within specific patches.
               │
               └ Subsystem major version. The major version is set by the subsystem developer. 

                 The major version of a subsystem must be updated when significant changes are made to the subsystem.

Install all the proposed 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

sudo apt install -y ntp tcpdump vlan dnsmasq

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

Configuring ecss-dns-env package

Run the following command:

sudo apt install -y ecss-dns-env

The installer will suggest selecting sections for configuration, do not select anything, just press Enter.

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 ecss-postgres-bdr-ssw package

sudo apt install -y ecss-postgres-bdr-ssw

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

=======================================================
=======================================================
 ecss-postgres-bdr-ssw successfully installed/updated! 
=======================================================
=======================================================


┏┓┏┓┏┓┏┳┓┏┓┳┓┏┓┏┓  ┳┓┳┓┳┓  ┏┓┏┓┓ ┏
┃┃┃┃┗┓ ┃ ┃┓┣┫┣ ┗┓  ┣┫┃┃┣┫  ┗┓┗┓┃┃┃
┣┛┗┛┗┛ ┻ ┗┛┛┗┗┛┗┛  ┻┛┻┛┛┗  ┗┛┗┛┗┻┛

Installing ecss-node

Installation of the required ecss-node package includes installation and initial configuration of the main subsystems.

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

sudo apt install -y ecss-node

During package installation, the ssw user is created, under which all ecss* services are launched. The necessary directories are created, DNS is configured, and SSL certificates are configured.

Installing on ecss1 server

During installation, it will be prompted to configure the parameters necessary for generating configuration files. Examples of replies are below.

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

Check the status of services with the following command:

systemctl is-active ecss-core ecss-pa-sip ecss-ds ecss-mediator ecss-mycelium

If the status is "active", continue; if the status is "inactive", run the command "sudo systemctl restart ecss-<package name>"

systemctl is-active ecss-core ecss-pa-sip ecss-ds ecss-mediator ecss-mycelium
active
active
active
active
active

To view information about the NTP synchronization status, the command "ntpq -p" is used. If the additional key "–n" is used, 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

License installation

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

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

sudo nano /etc/ecss/ecss-license-provider/config.yaml

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

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

elm_addresses:
 - "elm.eltex-co.ru:8099"
 - "192.168.111.22:8099"
 - "elm-3.eltex.loc:8099"
licenses:
 - id: 0
   kind: SSW
   type: elm
   license_key: "ssw1test"
   product_id: "ECSS1000001"
 - id: 1
   kind: ssw
   type: ecss_license
   license: "af615ebb92d381125ff"
ecss_nodes:
 - id: abf.test
   kind: ssw
   license_id: 0

sudo systemctl restart ecss-license-provider.service

sudo nano /etc/ecss/ecss-license-provider/config.yaml

elm_addresses:
 - "elm.eltex-co.ru:8099"
 - "192.168.111.22:8099"
 - "elm-3.eltex.loc:8099"
licenses:
 - id: 0
   kind: SSW
   type: elm
   license_key: "ssw1test"
   product_id: "ECSS1000001"
 - id: 1
   kind: ssw
   type: ecss_license
   license: "af615ebb92d381125ff"
 - id: 2
   kind: SSW
   type: elm
   license_key: "ssw2test"
   product_id: "ECSS1000002"
ecss_nodes:
 - id: 1.test
   kind: ssw
   license_id: 0
 - id: 2.test
   kind: ssw
   license_id: 1
 - id: 3.test
   kind: ssw
   license_id: 2

elm_addresses:
 - "elm.eltex-co.ru:8099"
 - "192.168.111.22:8099"
 - "elm-3.eltex.loc:8099"
licenses:
 - id: 0
   kind: SSW
   type: elm
   license_key: "ssw1test"
   product_id: "ECSS1000001"
 - id: 1
   kind: ssw
   type: ecss_license
   license: "af615ebb92d381125ff"
 - id: 2
   kind: SSW
   type: elm
   license_key: "ssw2test"
   product_id: "ECSS1000002"
 - id: 3
   kind: SSW
   type: elm
   license_key: "ssw3test"
   product_id: "ECSS1000003"
ecss_nodes:
 - id: 1.test
   kind: ssw
   license_id: 0
 - id: 2.test
   kind: ssw
   license_id: 1
 - id: 3.test
   kind: ssw
   license_id: 2
 - id: abf.test
   kind: ssw
   license_id: 3

sudo systemctl restart ecss-license-provider.service

/system/clusters/set [ecss1]

/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/request      
Waiting for licence...
[*******                                                               ] 6s       
┌─┬─────────────────────────────────────────────────────┬─────────┬────────────────────────────────────────┐
│A│                     Description                     │Old Value│               New Value                │
├─┼─────────────────────────────────────────────────────┼─────────┼────────────────────────────────────────┤
│^│Support for reservation of call-processes            │false    │true                                    │
│^│Maximum call duration (in seconds)                   │60       │2678400                                 │
│^│Maximum number of simultaneous calls                 │5        │10000                                   │
│^│Elph                                                 │         │                                        │
│^│ total count of members of the one Elph group        │10       │100                                     │
│^│Subscribers limit                                    │10       │500000                                  │
│^│Virtual subscribers limit                            │infinity │1000                                    │
│^│Add-on conferences                                   │         │                                        │
│^│ total count                                         │30       │1000                                    │
│^│Add-on conferences                                   │         │                                        │
│^│ members of the one add-on conference                │16       │300                                     │
│^│Chat rooms                                           │         │                                        │
│^│ total count                                         │30       │100                                     │
│^│Chat rooms                                           │         │                                        │
│^│ members of the one chatroom                         │16       │300                                     │
│^│Meet Me                                              │         │                                        │
│^│ total count                                         │0        │100                                     │
│^│Meet Me                                              │         │                                        │
│^│ members of the one Meet Me conference               │0        │300                                     │
│^│SORM                                                 │         │                                        │
│^│ enabled                                             │false    │true                                    │
│+│ channels on SORM mediator                           │         │64                                      │
│^│Sorm extractor                                       │none     │mfi                                     │
│^│Support antifraud system                             │none     │custom                                  │
│+│Call center                                          │         │                                        │
│+│ operator's capability for look at calls in queue    │         │true                                    │
│+│ operator's capability for use Intervension SS       │         │true                                    │
│^│Call center                                          │         │                                        │
│^│ active agents                                       │0        │1000                                    │
│^│Call center                                          │         │                                        │
│^│ active supervisors                                  │0        │100                                     │
│^│Teleconference                                       │         │                                        │
│^│ channels                                            │3        │2000                                    │
│^│Teleconference                                       │         │                                        │
│^│ max members of one teleconference                   │0        │200                                     │
│^│Teleconference                                       │         │                                        │
│^│ active count                                        │0        │32                                      │
│^│TSMN system                                          │         │                                        │
│^│ concurrent calls (active)                           │0        │50                                      │
│^│TSMN system                                          │         │                                        │
│^│ concurrent calls (backup)                           │0        │50                                      │
│^│TSMN system                                          │         │                                        │
│^│ backup mode                                         │none     │"backup"                                │
│^│Total count of simultaneous records voice calls      │0        │200                                     │
│+│IVR                                                  │         │                                        │
│+│ customization enabled                               │         │true                                    │
│+│ Automatic Speech Recognition (ASR) subsystem enabled│         │true                                    │
│^│Channels on dialer outgoing calls                    │2        │5                                       │
│+│Supplementary Services licence package(s)            │         │                                        │
│+│ name                                                │         │'ECSS-ADV'                              │
│+│ limit                                               │         │10000                                   │
│+│ description                                         │         │"Additional services of 4 and 5 levels" │
│+│ SS list                                             │         │[1,2,3,4,5]                             │
│+│ name                                                │         │'ECSS-BAS'                              │
│+│ limit                                               │         │10000                                   │
│+│ description                                         │         │"Basic services of 1 and 2 levels"      │
│+│ SS list                                             │         │[1,2]                                   │
│+│ name                                                │         │'ECSS-BAS+'                             │
│+│ limit                                               │         │10000                                   │
│+│ description                                         │         │"Expansion of basic services of 3 level"│
│+│ SS list                                             │         │[1,2,3]                                 │
│^│GEO backup                                           │         │                                        │
│^│ enabled                                             │false    │true                                    │
│^│SIGTRAN                                              │         │                                        │
│^│ SEP                                                 │false    │true                                    │
│^│ STP                                                 │false    │true                                    │
└─┴─────────────────────────────────────────────────────┴─────────┴────────────────────────────────────────┘
Legend:
    '^' - Changed;
    '-' - Deleted;
    '+' - New.


[request] You are trying to add a license that is different from the current one by the pa
          rameters in the table (other values will remain unchanged).
Licence received      o ?> yes
[*******                                                               ] 1m 15s   
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 │12.03.2026 18:40:00│ECSS 010070 │*     │ECSS TPM License│13.03.2027 06:59:59 │14.03.2026 10:44:05 │1d 6h 59m│
│0 │01.01.1990 00:00:00│ECSS DEFAULT│      │Default licence │                    │                    │         │
└──┴───────────────────┴────────────┴──────┴────────────────┴────────────────────┴────────────────────┴─────────┘

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

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

Perform configuration for the Sip adapter by running the following command:

sudo systemctl edit ecss-pa-sip.service

Add the following data to the configuration file:

[Service]
LimitNOFILE=65536

Reload the configuration

sudo systemctl daemon-reload

Update the configuration file by rebooting the server:

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

Next, the ecss-restf packages are installed, followed by ecss-media-server, ecss-media-resources, ecss-web-conf and others in any order:

ecss-restfs

ecss-restfs package

sudo apt install -y ecss-restfs

Installing ecss-restfs. During installation, you'll be asked a series of questions to create the necessary configuration files. The installer will also prompt you to install and configure the Text2speech package from Yandex.

After installing the ecss-restfs package, check for the presence of auto-informer wav files in the /var/lib/ecss/restfs/system/sounds/ directory using the command:

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

The presence of about 140 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/

Check the accessibility of these files from the outside. To do this, execute the command on the host ecss1 one by one:

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

wget http://ecss1:9990/system/sounds/ai_you.wav
--2023-12-18 17:43:29--  http://ecss1:9990/system/sounds/ai_you.wav
Resolving ecss1 (ecss1)... 127.0.1.1, 10.0.10.11
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      

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

verification files can be deleted

rm ai_you.wav

ecss-media-server

sudo apt install -y ecss-media-server

For the media server (ecss-media-server/MSR), initial configuration is possible by writing parameters to a configuration file. To do this, configure transport bind-addr,mcc bind-addres:

After creating the default configurations, perform a check: 

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

The msr configuration is located inside: config.xml, and the default.xml configuration is in the conf.d directory.

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 activates only the following codecs: pcma, pcmu, g722, h264, h263-1998, and t38. The rest have a status of 0 = off. If you want to activate other codecs, use the nano editor to change the priority from 0 to a priority number (the priority level should not be repeated for the audio/video/fax service).
sudo nano /etc/ecss/ecss-media-server/config.xml

Consider the accounts section (default.xml file):

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

Check the data for correctness.

<?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 msr on core.

The main parameters here are msr_name and realm:

• msr_name — defines the name of the msr (it is recommended to specify msr. name and the host it belongs to, for example, msr.ecss1);
• realm — defines the address for registering with the core. The default entry point is port 5000, address is 127.0.0.1.

After changing the configuration files /etc/ecss/ecss-media-server/config.xml and /etc/ecss/ecss-media-server/conf.d/default.xml, restart the ecss-media-server 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 optional, but recommended.

Installing the ecss-web-conf package also automatically installs the ecss-subscriber-portal-ui package. The ECSS-10 Subscriber Portal application allows subscribers to independently manage services, view information on completed calls and active conferences, and configure their own IVR scripts for incoming calls.

Check the connectivity of the web interface http://10.0.20.41, user/password: admin/password. Not all functions are available at the moment, but the web interface should be working and the login successful.

Security configuration. SSH

Configure the SSH server:

sudo nano /etc/ssh/sshd_config

Specify the port and address to which the server can be accessed in the configuration file:

Restart ssh:

sudo systemctl restart ssh.service

Adding services

Installing all services specified in the license:

/cluster/storage/ds1/ss/install ds1@ecss1 ss_*

Result:

/cluster/storage/ds1/ss/install ds1@ecss1 ss_*
Successfully installed: /var/lib/ecss/ss/ss_dnd.xml
Successfully installed: /var/lib/ecss/ss/ss_clir.xml
. . .
Successfully installed: /var/lib/ecss/ss/ss_chunt.xml

Example of a primary system configuration using web configurator

Initial data

• System installation is complete;
• System is ready for further configuring;
• Interfaces are running.

It is recommended to use the latest available browser versions. Recommended browsers: Opera, Chrome.

To start configuring the system, go to the web configurator: http://<Ipadd SSW>.

To determine and register in the system, the following are planned:

• Subscribers with numbers 42001, 42002 , 42003, 42004 ,42005, 42006, 42007, 42008, 42009, 42010;
• Trunk towards the gateway.

Preparation for work

Figure 1 — Log in to the web configurator (authorization window)

In the authorization window, enter the values defined during the installation of the web configurator.

After logging in, the main workspace with application icons will be visible, as well as status bar with available options, in particular:

• 1 — log out of the system;
• 2 — domain selection;
• 3 — language selection.

Figure 2 — View of the web configurator workspace

Creating an operator account

After authorization, in order to increase security during the operation of the software switch, it is recommended to create accounts for operators, as well as to change the password for the admin user.

To create a new operator account, use User manager application:

Figure 3 — Application view "User Manager"

Click the "Add" button . In the window that opens, define a new account, for this:

1. In the "Name" field, enter the login of the account, for example, "test";
2. In the "Password" field and "Confirmation" field enter the password for the user, for example "testpassword";
3. Define level of access rights for the user by selecting current permissions or using roles, for example ecss-user.

Figure 4 — Operator account creation dialog box

Figure 5 — Application view with created operator account

To change the password, click the edit button next to the user name. In the dialog box that opens, enter:

1. Old password (for the admin user, the default password is password);
2. New password;
3. Confirm new password.

Figure 6 — Edit user dialog box

Adding media resources

To begin working with the media server immediately after its registration, it is necessary to activate the MSR network interfaces. The web configurator application "MSR registrars" is used to configure media resources.

Figure 7 — MSR registrars

Set the IP address for receiving connections from the media server, changing the value 0.0.0.0 to the actual MSR addresses:

Figure 8 — Setting the IP address of the MSR

Creating IP-set (sip transport) and assigning it to a domain

To configure an interface, open the Clusters application.

Figure 9 — Clusters application view

To create a new IP address group (IP-set), select the SIP adapter cluster "sip1" and click on the Cluster Properties button (or double-click on the cluster icon with left mouse button).

In the dialog box that appears, go to the Transport tab. Next, click on Add button. New group will appear. To edit the fields, double-click the one you need:

1. Rename an address group (IP-set), for example "test_set";
2. Specify the port on which the domain will be accessed, for example 5060;
3. Expand newly created group by clicking on the black triangle to the left of the group name;
4. Define the address for the SIP adapter node, according to the configuration example. For example specify 10.0.20.41:

Figure 12 — Clusters/Transport application view

Click Save to apply the settings.

Creating a domain

Domain is a virtual PBX within our SSW. We can create as many of virtual PBXs as needed for a project.

To create a domain, log in to the Domains application. In the window that opens, create a domain:

1. Click the Add domain button:

Figure 11 — Adding domain to the system

2. The following settings are available in the dialog box that opens:

• Name — individual name of the virtual PBX;
• Service profile (SS profile) — system profile of additional services. This profile will be copiedwith the same name to newly created domain and all services from this profile will be automatically allowed access via access-list;
• IVR profile (IVR profile) — the IVR profile specified in the IVR Constraints Editor application.

Enter the domain name, for example "test_domain";

3. Click Ok:

Figure 12 — Domain declare

4. Click the Updatebutton.

Created domain will be displayed in the current configuration:

Figure 13 — Displaying created domain

To edit current domain, it must be selected in the system. To switch to a domain, use the domain selection option (see point 2 in the figure View of the web configurator workspace).

After selecting the domain, according to the current system configuration, all applications will be available:

Figure 14 — Displaying applications in current system configuration

To link an address group to a domain, return to the "Domain" app, select the domain, and go to the settings by clicking the "Domain Properties" button or double-clicking the domain.

In the list settings, open the "SIP" branch, then "SIP Transport," then select the newly created address group in the IP set field. Click "Save" to apply the settings.

Figure 15 — SIP transport settings

Select the required services for the created domain that will be used (for example, for a subscriber domain, trunk services are not required, and vice versa for a transit domain. There is no need to specify services for the subscriber).

Figure 16 — After creating a new domain, there are no services

1. Select the "SS Install" application;
2. Select the "SS installed" column (services specified in the SSW license);
3. Select the services required for the specified domain.

Save configuration.

Figure 17 — Selection of services for subscribers/trunks of the new domain

Figure 18 — List of services now available to subscribers of the new domain

Creating subscribers

The Subscriber card application is used to create and edit subscriber parameters in the system.

Figure 19 — Subscriber card application view

It is possible to create SIP subscribers and virtual subscribers in the application.

For users with a physical termination, the functionality of the SIP subscriber is used, while the virtual subscriber is used when functionality without physical endings is needed. For example, the number for accessing the ivr script.

To create new subscribers, click on the Add button.

In the dialog box that opens, specify the following parameters:

• Context — routing context, select the one that you created, for example "test_name";
• Interface name — number or group of numbers that is assigned to the subscriber, for example {42001-42010} or abcd;
• Interface group — the name of a group that unites several subscribers, for example "sip";
• Alias as user — setting that binds entity number, alias and user with the same name, in the example the setting is activated;
• Authorization — procedure for verifying the authenticity of the user's rights to access data, in the example always is used.
• Login — use WHATEVER.
• Password — can be set or used generated by the system.

↓

Figure 20 — Example of identifying subscribers in a domain

Figure 21 — Example of adding services for a subscriber

Creating and applying routing contexts for a domain

Routing is responsible for finding the number and then addressing the call. At least one routing context must be configured for the system to operate correctly.

Routing is configured in Routing Manager application.

Figure 22 — Routing manager application view

Example of creating a context and a few rules in it:

1. In the left part of the window in the Context section click the Create context button ;

2. In the dialog box that opens, indicate the name of the context;

3. Click Ok button;

4. Click Save context ;

Create 4 rules in this context:

• rule1 — rule for accessing TAU-72 trunk;
• rule2 — local routing rule for numbers 42001-42005;
• rule3 — rule for entering the ivr;
• rule4 — exception rule.

To create a new rule, select the created context and click Create rule. In the window that appears, enter name of the rule. Then save the newly created rules.

Figure 23 — Creating routing context rule

Figure 24 — Defining rules

At the moment, the trunk that can be referred in a rule is not defined, however it is possible to specify the numbers by which the selection will be made.

Go to the lower part of the screen by clicking on the rule1, where the areas for editing the routing context are located. It is conditionally defined in the example that selection for entering the trunk will be carried out based on the characteristics of the called subscriber number (CDPN), and the numbers in the trunk should start with digit 4.

Functionally, the routing context is divided into three parts:

• Condition — section defining the expressions for selection according to the proposed criteria;
• Action — section that converts the signs of numbers to a specific value;
• Result — section that completes the routing and determines its result.

rule1: To access the trunk, edit each part correctly:

• In the conditions section, go to the CDPN tab. Enter the phone numbers that are assigned to the trunk in the Number field. For example, to define numbers from 42006 to 42007, enter condition 420(6-7);
• In the actions section, go to the CDPN tab. Enter a mask to change the number in the Number field. For example, to add number 4 before the number, fill in the field with the following expression 4{1,2,3,4,5};
• Click Save rule and Save Context buttons to apply changes.

To configure the result field, the trunk must be defined in the system, so return to configuring this rule a little later.

Configure remaining rules in the same way.

For rule2:

• In CDPN tab in conditions section, enter phone numbers that are behind the trunk in "Number" field. For example, to define numbers from 42001 to 42005, enter condition 420(1-5);
• In the result section, define the result as local (e. local routing);
• Click Save rule and Save Context buttons to apply changes.

For rule 3, assume that subscribers with numbers 108, 109 and 110 get into the informant ivr script before calling further.

• In CGPN tab in conditions section, enter the phone numbers for which the selection will be in the field "Number", for example 420(10.08-09).
• Click Save rule and Save Context buttons to apply changes.

To configure the result field, ivr script must be defined in the system, so return to configuring this rule later.

For rule 4, define an exception rule — this is a rule that works in case any other rules fail.

• By default, this rule is created in the system in default_routing context. The % symbol is written to the called number in the conditions, and the result is local routing, however, it is recommended to create this rule at the end if assigning to the subscriber a context other than default_routing.

Figure 25 — Example of configuring routing context 

Creating trunk 

To create and edit trunk parameters in the system, use the Trunk manager application.

Figure 26 — Trunk Manager application view

To define a trunk in the system, click on the Trunk declare button, define parameters in the dialog box that opens:

• Name — assign trunk name by which it can be identified in the system;
• Context — apply previously created test_name routing context;
• Group — select the interface group created when defining 'test.group' subscribers;
• IP address group (IPSet) — 'ipset1' address group created on the domain;
• Registration — if trunk is used, then enable this parameter, it is not used in the example;
• Host [:port] — destination IP address of the trunk — 10.0.3.100;
• Listen port — transport port where traffic from the trunk will be listened to, corresponds to the port assigned to the IP address group.

Figure 27 — Creating a trunk

Creating IVR script 

To create IVR, use the IVR editor application. 

To create a script, click on the Add  button, select script type (in this case there is a script for incoming calls), specify the name of the script in the dialog box, for example "test_ivr".

After creating the script, a flowchart will appear in the main editor window.

In figures below is shown an example of making a script that plays a pre-recorded phrase to the caller when triggered, and then continues the call.

• Info —  block that plays messages until the user responds. A tone generator is used as a recorded phrase:

Figure 29 — View of the IVR workspace with the Info block settings

• Dial — block that makes a call to a given number. To continue the call, apply the predefined CDPN variable:

Figure 30 — View of the IVR workspace

Completing routing configuration

To complete routing, open Routing manager application and in rules rule1 and rule3 adjust the corresponding routing results, and follow the steps below:

• rule1: select the "external" sub-item in the Result section. In the Value field of the Directions table add the trunk created earlier, then save the rule .
• rule3: select the "ivr" sub-item in the Result section. In the script field add the previously created ivr script, then save the rule and the context .

Figure 31 — Type of routing context

Initial system configuration via the command-line interface (CLI)

ssh admin@localhost -p 8023

/system/media/resource/declare core1@ecss1 contact net.20@msr.ecss1 default local true

/system/media/resource/declare core1@ecss1 contact net.20@msr.ecss1 default local true
  Declared media resources
┌─────────────┬───────────────────────┬────────┬─────────┬───────┐
│    Node     │        Contact        │ Active │   Zone  │  Site │
├─────────────┼───────────────────────┼────────┼─────────┼───────┤
│ core1@ecss1 │ net.20@msr.ecss1      │ true   │ default │ local │
└─────────────┴───────────────────────┴────────┴─────────┴───────┘

/system/media/resource/info core1@ecss1 net.20@msr.ecss1
  Media resource specific for node core1@ecss1:
┌─┬─────────────────┬─────────────────────┐
│F│    Parameter    │        Value        │
├─┼─────────────────┼─────────────────────┤
│r│ Contact         │ net.20@msr.ecss1    │
│r│ Status          │ registered          │
│r│ Cc-status       │ connected           │
│r│ Cc-status uptime│ 00:16:48            │
│r│ Cc-id           │ cb6599              │
│r│ Address         │ 10.0.20.41:5700     │
│r│ Register time   │ 2025/12/03 09:40:25 │
│r│ Expired         │ 131                 │
│r│ Iface           │ net.20(10.0.20.41)  │
│ │ Active          │ true                │
│ │ Zone            │ default             │
│ │ Site            │ local               │
│r│ MSR version     │ 3.18.1.0.12         │
│r│ MSR load        │ 0                   │
│r│ MSR perf coef   │ 1.0                 │
└─┴─────────────────┴─────────────────────┘
Legend:
Column F - means Flag, values r - flag for readonly parameter

/system/media/resource/list all                      
  All media resource selected list specific:
┌─────────────┬───────────┬──────────────┬───────────┬──────┬────────┬───────────┬───────────┬─────────────────┬────────┬────────────┬────────┬─────────┬───────┬──────────────────┬────────────┬─────────┐
│    Node     │    MSR    │     MSR      │    MSR    │ MSR  │ Cc-id  │ Cc-status │ Cc-uptime │   Cc-address    │ Iface  │   Iface    │ Active │  Zone   │ Site  │     Contact      │   Status   │ Expired │
│             │           │   version    │ perf coef │ load │        │           │           │                 │  name  │    addr    │        │         │       │                  │            │         │
├─────────────┼───────────┼──────────────┼───────────┼──────┼────────┼───────────┼───────────┼─────────────────┼────────┼────────────┼────────┼─────────┼───────┼──────────────────┼────────────┼─────────┤
│ core1@ecss1 │ msr.ecss1 │ 3.18.1.0.12  │       1.0 │    0 │ 54faa9 │ connected │ 00:54:48  │ 10.0.20.41:5700 │ net.20 │ 10.0.20.41 │ true   │ default │ local │ net.20@msr.ecss1 │ registered │     129 │
└─────────────┴───────────┴──────────────┴───────────┴──────┴────────┴───────────┴───────────┴─────────────────┴────────┴────────────┴────────┴─────────┴───────┴──────────────────┴────────────┴─────────┘

/system/media/registrar/set common registration-timeout 60
Common parameter registration-timeout set to 60.

/system/media/registrar/set private core1@ecss1 listen-ip 10.0.20.41

/system/media/registrar/set private core1@ecss1 listen-ip 10.0.20.41   
Private parameter listen-ip set to 10.0.20.41 at node core1@ecss1.

/system/media/registrar/info
 Common parameters:
┌───────────────────────────┬───────┐
│         Parameter         │ Value │
├───────────────────────────┼───────┤
│ registration-timeout, sec │   180 │
└───────────────────────────┴───────┘
 Private parameters:
┌─────────────┬─────────┬───────────┬────────────┬─────────────┐
│    Node     │ Status  │ Is-active │ Listen-ip  │ Listen-port │
├─────────────┼─────────┼───────────┼────────────┼─────────────┤
│ core1@ecss1 │ active  │ true      │ 10.0.20.41 │        5000 │
└─────────────┴─────────┴───────────┴────────────┴─────────────┘

/system-status   
Checking...
┌─┬───────────────┬───────────────────────────┬────────────────┬──────────────┬──────┐
│ │     Node      │          Release          │  Erlang nodes  │ Mnesia nodes │Uptime│
├─┼───────────────┼───────────────────────────┼────────────────┼──────────────┼──────┤
│ │core1@ecss1    │ecss-core-3.18.1.0.1657    │core1@ecss1     │not running   │1h 23m│
│ │ds1@ecss1      │ecss-ds-3.18.1.0.1657      │ds1@ecss1       │ds1@ecss1     │1h 23m│
│ │md1@ecss1      │ecss-mediator-3.18.1.0.1657│md1@ecss1       │md1@ecss1     │1h 23m│
│ │mycelium1@ecss1│ecss-mycelium-3.18.1.0.1657│mycelium1@ecss1 │not running   │1h 23m│
│ │sip1@ecss1     │ecss-pa-sip-3.18.1.0.1657  │sip1@ecss1      │sip1@ecss1    │1h 23m│
└─┴───────────────┴───────────────────────────┴────────────────┴──────────────┴──────┘

All services are started.

  Active media resource selected list specific:
┌─────────────┬───────────┬──────────────┬───────────┬───────────┐
│    Node     │    MSR    │     MSR      │ Cc-status │ Cc-uptime │
│             │           │   version    │           │           │
├─────────────┼───────────┼──────────────┼───────────┼───────────┤
│ core1@ecss1 │ msr.ecss1 │ 3.18.1.0.12  │ connected │ 00:04:15  │
└─────────────┴───────────┴──────────────┴───────────┴───────────┘

/cluster/adapter/sip1/sip/network/set ip_set test_set node-ip node = sip1@ecss1 ip = 10.0.20.41

/cluster/adapter/sip1/sip/network/set ip_set test_set listen-ports list = [5060]

/cluster/adapter/sip1/sip/network/set ip_set test_set node-ip node = sip1@ecss1 ip = 10.0.20.41
        
Property "ip_set" successfully changed from: 
    
        to
test_set: no ports set
test_set: sip1@ecss1 10.0.20.41
test_set: dscp 0.

/cluster/adapter/sip1/sip/network/set ip_set test_set listen-ports list = [5060]
Property "ip_set" successfully changed from:
test_set: no ports set
test_set: sip1@ecss1 10.0.20.41
test_set: dscp 0
        to
test_set: 5060
test_set: sip1@ecss1 10.0.20.41
test_set: dscp 0

/domain/declare test_domain --add-domain-admin-privileges --add-domain-user-privileges

/domain/test_domain/sip/network/set ip_set [test_set]

/domain/declare test_domain --add-domain-admin-privileges --add-domain-user-privileges
New domain test_domain is declared


/domain/test_domain/sip/network/set ip_set [test_set]
Property "ip_set" successfully changed from: 
[]
   to
["test_set"].

/cluster/storage/ds1/ss/access-list add test_domain *

/cluster/storage/ds1/ss/access-list add test_domain *
Supplementary services successfully added in the domain test_domain.

/domain/test_domain/ss/licence/politics/declare new_sub "Set when creating a subscriber"

/domain/test_domain/ss/licence/politics/declare new_sub "Set when creating a subscriber"
Licence politic new_sub successfully declared.

/cluster/storage/ds1/licence/show-licence 1

/cluster/storage/ds1/licence/show-licence 1
SSW ID                                                < Name SSW ID >
Description                                           ECSS ELM License

. . .  

Supplementary Services licence package(s)             
 name                                                 'ECSS-ADV'
 limit                                                600000
 description                                          "The whole package of services"
 SS list                                              [1,2,3,4,5]
                                                      
. . .  

/domain/test_domain/ss/licence/politics/package-add new_sub ECSS-ADV 

/domain/test_domain/ss/licence/politics/package-add new_sub ECSS-ADV 
Licence packages ["ECSS-ADV"] successfully added to politic new_sub.

/domain/test_domain/ss/licence/politics/activate new_sub

/domain/test_domain/ss/licence/politics/activate new_sub
Licence politic new_sub successfully activated.