Сравнение версий

Ключ

  • Эта строка добавлена.
  • Эта строка удалена.
  • Изменено форматирование.

...

Раскрыть
titleUbuntu Server 22.04 installation
A Shared Block
shared-block-keyUbuntu Server 22.04 installation
панель
titleSelect language

панель
titleContinue without update

панель
titleKeyboard configuration


панель
titleВыбираем стандартную установку Ubuntu СерверSelect the standard Ubuntu Server installation


панель
titleSelect Eht: the interface for installing Ubuntu (it should have internet access).

панель
titleSet the IP address for internet access (DHCP cannot be used).

панель
titleProxy server cannot be used (if it is used in your project, please specify)

панель
titleDefault

панель
titleCreate partitions on the disk, using LVM

панель
titleBy default, two partitions are created: /boot and /, we keep /boot and delete /. First, unmount

панель
titleThen delete

панель
titleConfirm deletion

панель
titleLeave only /boot

панель
titleCreate partitions according to the dimensions specified in the table below

панель
title root size 30 Gb, mount point /

панель
title mnesia size 30 Gb, mount point /var/lib/ecss

панель
title log size 20 Gb, mount point /var/log

панель
titlemysql, size 30G, mount point - /var/lib/mysql

панель
title ecss_log, size 20 Gb, mount point  /var/log/ecss

панель
titleecss_db, size 100 Gb, mount point-  /var/lib/ecss-mysql

панель
titlehome, size 10 Gb, mount point -  /home

панель
titleglusterfs - for the cluster / for a single host - restfs, size - all remaining disk space, mount point - /var/lib/ecss/glusterfs - for the cluster, and /var/lib/ecss/restfs - for a single server

панель
titleobtained configuration

панель
titleConfirm

панель
titleCreate a user and a hostname, in ECSS10 the recommended hostname is ecss1/ecss2 (used for license integration), username (in the example abf / password at your discretion)

панель
titleWhen installing, select Free installation:

панель
titleWhen installing Ubuntu Linux, install openSSH for remote management

панель
titleConfirm

панель
titleWait for the message to appear - Restart now

панель
titleRemove the installation disk/flash drive and press Enter

 Ubuntu Linux Server has been installed.




Раскрыть
titleUbuntu Server 22.04 installation
A Shared Block
shared-block-keyUbuntu Server 22.04 installation
панель
titleSelect language

панель
titleContinue without update

панель
titleKeyboard configuration


панель
titleВыбираем стандартную установку Ubuntu СерверSelect the standard Ubuntu Server installation


панель
titleSelect Eht: the interface for installing Ubuntu (it should have internet access).

панель
titleSet the IP address for internet access (DHCP cannot be used).

панель
titleProxy server cannot be used (if it is used in your project, please specify)

панель
titleDefault

панель
titleCreate partitions on the disk, using LVM

панель
titleBy default, two partitions are created: /boot and /, we keep /boot and delete /. First, unmount

панель
titleThen delete

панель
titleConfirm deletion

панель
titleLeave only /boot

панель
titleCreate partitions according to the dimensions specified in the table below

панель
title root size 30 Gb, mount point /

панель
title mnesia size 30 Gb, mount point /var/lib/ecss

панель
title log size 20 Gb, mount point /var/log

панель
titlemysql, size 30G, mount point - /var/lib/mysql

панель
title ecss_log, size 20 Gb, mount point  /var/log/ecss

панель
titleecss_db, size 100 Gb, mount point-  /var/lib/ecss-mysql

панель
titlehome, size 10 Gb, mount point -  /home

панель
titleglusterfs - for the cluster / for a single host - restfs, size - all remaining disk space, mount point - /var/lib/ecss/glusterfs - for the cluster, and /var/lib/ecss/restfs - for a single server

панель
titleobtained configuration

панель
titleConfirm

панель
titleCreate a user and a hostname, in ECSS10 the recommended hostname is ecss1/ecss2 (used for license integration), username (in the example abf / password at your discretion)

панель
titleWhen installing, select Free installation:

панель
titleWhen installing Ubuntu Linux, install openSSH for remote management

панель
titleConfirm

панель
titleWait for the message to appear - Restart now

панель
titleRemove the installation disk/flash drive and press Enter

 Ubuntu Linux Server has been installed.





Якорь
option for storing information
option for storing information
Table 1 Table1 — An option for storing information in a file system on physical media for servers

1Operating system boot partition (created automatically)bootraid 1: hdd1, hdd2boot/bootext41 GBPrimary
2Operating system root partitionrootraid 1: hdd1, hdd2root/ext430 GBLogical
3Local database informationmnesiaraid 1: hdd1, hdd2mnesia/var/lib/ecssext410 GBLogical
4Distributed database for storing media resourcesglusterfsraid 1: hdd1, hdd2 или or hdd3glusterfs/var/lib/ecss/glusterfs*ext4Max GBLogical
5OS subsystem operation logslograid 1: hdd1, hdd2 или or hdd3log/var/logext420 GBLogical
6ECSS subsystem operation logsecss_lograid 1: hdd1, hdd2 или or hdd3ecss_log/var/log/ecssext420 GBLogical
7Databasesecss_dbraid 1: hdd1, hdd2 или or hdd3ecss_db/srv/ecss/ecss-postgres-bdr-ssw/ext4100–400 GB**Logical
8User fileshomeraid 1: hdd1, hdd2 или or hdd3home/homeext410 GBLogical

...

According to the technical specification, the following addresses are used in a given example (in brackets are differences for ecss2):

  • 10.0.10.11(1252)/24 — for management, VLAN 10;
  • 10.0.20.21(2252)/24 — core, VLAN 20;
  • 10.0.20.31(32)/24 — virtual addresses (vrrp) for VoIP;
  • 10.0.10.10 — virtual address (vrrp) for MySQL server;
  • 10.0.10.1 — gateway and dns for access to external network;
  • 10.0.20.1 — gateway to 10.0.3.0/24 subnet;
  • 10.136.16.211, 10.136.16.212 — NTP server addresses, which are accessed via 10.0.10.1 gateway.

...

Questions ecss-dns-envReplies for ecss1Ответы Answers for ecss2
[Primary broker] enter address ([Primary broker] Enter IP)10.0.10.51 (needs to be entered)10.0.10.51 (needs to be entered)
[Secondary broker] enter address ([Secondary broker] Enter IP)10.0.10.52 (needs to be entered)10.0.10.52 (needs to be entered)

...

Раскрыть
titleerror examples
панель
titleno access to slave

sudo ./postgresbdr_ssw.sh check
[sudo] password for abf: 
Sorry, try again.
[sudo] password for abf: 
Enter master ip please
Like 10.150.150.15
10.0.10.51
Enter slave ip please
10.0.10.52
Press enter with empty password
q - exit table view (if needed)
node table on the master using ecss_storekeeper_db

     node_sysid      |                                    node_local_dsn                                     | node_init_from_dsn 
---------------------+---------------------------------------------------------------------------------------+--------------------
 7569871659329171478 | host=10.0.10.51 port=5439 dbname=ecss_storekeeper_db user=postgres password=postgres1 | 
(1 row)

node table on the slave using ecss_storekeeper_db
psql: error: connection to server at "10.0.10.52", port 5439 failed: Connection refused
    Is the server running on that host and accepting TCP/IP connections?
connection table onthe master the master using по ecss_storekeeper_db
     conn_sysid      |                                       conn_dsn                                        
---------------------+---------------------------------------------------------------------------------------
 7569871659329171478 | host=10.0.10.51 port=5439 dbname=ecss_storekeeper_db user=postgres password=postgres1
(1 row)

connection table on the slave using ecss_storekeeper_db
psql: error: connection to server at "10.0.10.52", port 5439 failed: Connection refused
    Is the server running on that host and accepting TCP/IP connections?

панель
titleconnection mismatch error

sudo ./postgresbdr_ssw.sh check
Enter master ip please
Like 10.150.150.15
10.0.10.51
Enter slave ip please
10.0.10.52
Press enter with empty password
q - exit table view (if needed)
node table on the master using ecss_storekeeper_db

     node_sysid      |                                    node_local_dsn                                     | node_init_from_dsn 
---------------------+---------------------------------------------------------------------------------------+--------------------
 7569871659329171478 | host=10.0.10.51 port=5439 dbname=ecss_storekeeper_db user=postgres password=postgres1 | 
(1 row)

node table on the slave using ecss_storekeeper_db
connection table on the master using ecss_storekeeper_db
     conn_sysid      |                                       conn_dsn                                        
---------------------+---------------------------------------------------------------------------------------
 7569871659329171478 | host=10.0.10.51 port=5439 dbname=ecss_storekeeper_db user=postgres password=postgres1
(1 row)

connection table on the slave using ecss_storekeeper_db
     conn_sysid      |                                       conn_dsn                                        
---------------------+---------------------------------------------------------------------------------------
 7569499877813944343 | host=10.0.10.51 port=5439 dbname=ecss_storekeeper_db user=postgres password=postgres1
 7569514001040228374 | host=10.0.10.52 port=5439 dbname=ecss_storekeeper_db user=postgres password=postgres1
 7569871659329171478 | host=10.0.10.51 port=5439 dbname=ecss_storekeeper_db user=postgres password=postgres1
(3 rows)


...

ecss-user questionsReplies for ecss2Example
Do you want to use the default settings?No (default)

Do you want to disable daily apt package updates?

Yes (default)

How do you want to configure certificates?copy (needs to be entered)

Do you want to install certificates into the system?Yes (default)

Which method do you want to copy the certificates?ssh (needs to be entered)

Enter the hostname to connect to:

ecss1 (needs to be entered)

Enter the host port to connect to:22 (default)

Enter your login to connect: (for example: eltex)eltex (needs to be entered)


Before copying make sure, that the user from whom the copying will be performed is a member of the group ssw.

Which authorization method to use?password (needs to be selected)

Enter the password to connect: 

Enter the path to the certificates:

/etc/ecss/ssl (default)

 
ecss-node questionsReplies for ecss2Example

Якорь
Идентификатор ECSS-узла
Идентификатор ECSS-узла
ECSS Node ID in DNS format (cluster name configuring): (any unique name, in еру the example: abf.test)

abf.test (needs to be entered)

Подсказка

ECSS_ID format
It must begin and end with a Latin letter or number, while dots and dashes may be used in the body.

Без форматирования
[A-Za-z0-9][A-Za-z0-9.-][A-Za-z0-9]

Do you want to use the standard settings? 

No (needs to be selected)

Select the items you want to configure: 


ntp + cookie  (needs to be selected)

Enter external NTP servers separated by a space: 

ntp.ubuntu.com (default)

NTP: Do you want to use the settings for the cluster? 

Yes (default)

NTP: Installing Startum for a cluster: 

7 (default)

NTP specify local servers for synchronization separated by a space: (in the example ecss2 - 10.0.10.51) 

10.0.10.51 (needs to be entered)

NTP: Do you want to manually define the networks that should have access to NTP? 

Yes (default)

NTP: Enter networks that should have access to NTP separated by a space: (in the example: 10.0.10.0|255.255.255.0 10.0.20.0|255.255.255.0)

10.0.10.0|255.255.255.0 10.0.20.0|255.255.255.0 (needs to be entered)

Cookie for the core node: (specify a unique cookie for the core, in the example: ecss-core-example) 

Предупреждение

In the cluster configuration, the cookies must be the same for nodes of the same type


ecss-core-example (needs to be entered)

Cookie for ds node: (specify a unique cookie for the ds, in the example: ecss-ds-example)

Предупреждение

In the cluster configuration, the cookies must be the same for nodes of the same type

ecss-ds-example (needs to be entered)

Cookie for mediator node: (specify a unique cookie for the mediator, in the example: ecss-mediator-example)

Предупреждение

In the cluster configuration, the cookies must be the same for nodes of the same type

ecss-mediator-example (needs to be entered)

Cookie for mediator pa-sip: (specify a unique cookie for the pa-sip, in the example: ecss-pa-sip-example)

Предупреждение

In the cluster configuration, the cookies must be the same for nodes of the same type

ecss-pa-sip-example (needs to be entered)

Cookie for mycelium: (specify a unique cookie for the mycelium, in the example: ecss-mycelium-example)

Предупреждение

In the cluster configuration, the cookies must be the same for nodes of the same type

ecss-mycelium-example (needs to be entered)

Cookie for sorm: (specify a unique cookie for the sorm, in the example: ecss-sorm-example)

Предупреждение

In the cluster configuration, the cookies must be the same for nodes of the same type

ecss-sorm-example (needs to be entered)

  
ecss-user questionsReplies for ecss1Example

Maximum size of uncompressed dump in bytes.


8G (default)

Maximum size of compressed dump in bytes.2G (default)

The maximum size that the /var/lib/systemd/coredump directory can occupy is:

default (default)

Minimum amount of free disk space in bytes.

30G (default)

Save to a safe place and delete the file /etc/ecss/ssl/ecss10root.key!

Ok (default)

...

Раскрыть
titleExample of initial configuration via CoCon (CLI)

Adding media resources using the command-line interface (CLI)

A media resource is a description of the media server parameters required for operation.

Примечание

To use the media resource and establish connections, it is necessary to activate it in the media resource creation command: /system/media/resource/declare (parameter "is active"=true) or /system/media/resource/set (parameter "active"=true), if activation was not performed during creation. Activation can also be performed through the web interface, application - MSR network terminations (MSR-registrars).


Раскрыть
titledeclare

declare

The command to declare a media server connection to ECSS-10.

To operate in preconfigured mode, one can pre-register media resources with known information.

To do this, it is necessary to create a description of known media servers with all parameters specified, allowing to start working with the media server immediately after its registration.

The command to create a media server configuration:

Command path:

/system/media/resource/declare

Syntax:

declare <node> by_contact <contact> <zone> <site> <is active>

or

declare <node> by_iface <msr> <acc_id> <iface> <zone> <site> <is active>

Parameters:

<node> — core node name;

<contact> — contact uri of the declared media resource;

<zone> — logical service zone of the MSR;

<site> — MSR service network identifier;

<is active> — media resource activity status, true/false values;

<msr> — MSR name;

<acc_id> — resource identifier number;

<iface> — interface name.


Раскрыть
titleset

set

A command for changing media resource settings.

Command path:

/system/media/resource/set

Syntax:

set <node|*> <contact> <active|zone|site> <value>

Parameters:

<node|*> — node name;
<contact> — contact uri of the declared media resource;
<active|zone|site> — activation | zone | site;
<value> — parameter value.

Example:

Enable communication between the MSR and Core subsystems. To do this, enter the following commands:

Блок кода
titlein CoCon
/system/media/resource/set core1@ecss1 net.20@msr.ecss1 active true


Блок кода
titlein CoCon
/system/media/resource/set core1@ecss2 net.20@msr.ecss2  active true


Блок кода
titlein CoCon
/system/media/resource/set core1@ecss1 net.20@msr.ecss2  active true


Блок кода
titlein CoCon
/system/media/resource/set core1@ecss2 net.20@msr.ecss1  active true


Без форматирования
languagebash
/system/media/resource/set core1@ecss1 net.20@msr.ecss1 active true  
  Media resource:
┌─────────────┬──────────────────┬──────────┬───────┐
│    Node     │     Contact      │ Property │ Value │
├─────────────┼──────────────────┼──────────┼───────┤
│ core1@ecss1 │ net.20@msr.ecss1 │ active   │ true  │
└─────────────┴──────────────────┴──────────┴───────┘
/system/media/resource/set core1@ecss2 net.20@msr.ecss2 active true 
  Media resource:
┌─────────────┬──────────────────┬──────────┬───────┐
│    Node     │     Contact      │ Property │ Value │
├─────────────┼──────────────────┼──────────┼───────┤
│ core1@ecss2 │ net.20@msr.ecss2 │ active   │ true  │
└─────────────┴──────────────────┴──────────┴───────┘
/system/media/resource/set core1@ecss1 net.20@msr.ecss2 active true 
  Media resource:
┌─────────────┬──────────────────┬──────────┬───────┐
│    Node     │     Contact      │ Property │ Value │
├─────────────┼──────────────────┼──────────┼───────┤
│ core1@ecss1 │ net.20@msr.ecss2 │ active   │ true  │
└─────────────┴──────────────────┴──────────┴───────┘
/system/media/resource/set core1@ecss2 net.20@msr.ecss1 active true 
  Media resource:
┌─────────────┬──────────────────┬──────────┬───────┐
│    Node     │     Contact      │ Property │ Value │
├─────────────┼──────────────────┼──────────┼───────┤
│ core1@ecss2 │ net.20@msr.ecss1 │ active   │ true  │
└─────────────┴──────────────────┴──────────┴───────┘


Раскрыть
titleinfo

info

A command for viewing connection status information for a specific media resource.

Command path:

/system/media/resource/info

Syntax:

info <node>  <contact>

Parameters:

<contact> — contact uri of the declared media resource;
<node> — node name.

ПримерExample:

Блок кода
languagebash
/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:39:35            │
│r│ Cc-id           │ db21af              │
│r│ Address         │ 10.0.20.51:5700     │
│r│ Register time   │ 2025/12/02 16:43:07 │
│r│ Expired         │ 84                  │
│r│ Iface           │ net.20(10.0.20.51)  │
│ │ Active          │ true                │
│ │ Zone            │ default             │
│ │ Site            │ local               │
│r│ MSR version     │ 3.18.1.0.10         │
│r│ MSR load        │ 0                   │
│r│ MSR perf coef   │ 1.0                 │
└─┴─────────────────┴─────────────────────┘

Legend:
Column F - means Flag, values r - flag for readonly parameter


Раскрыть
titlelist

list
A command for viewing a list of media resources in the ECSS-10 system.

Command path:

/system/media/resource/list

Syntax:

list [active | all | register]

Parameters:

active — display only active media resources (default);
register — display only registered media resources;
short — display minimal information;
all — display all declared media resources.

By default, the command displays a list of registered media servers.

Example:

Блок кода
languagebash
/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.10 │       1.0 │    0 │ db21af │ connected │ 00:40:22  │ 10.0.20.51:5700 │ net.20 │ 10.0.20.51 │ true   │ default │ local │ net.20@msr.ecss1 │ registered │     156 │
│             │ msr.ecss2 │ 3.18.1.0.10 │       1.0 │    0 │ 263898 │ connected │ 00:40:22  │ 10.0.20.52:5700 │ net.20 │ 10.0.20.52 │ true   │ default │ local │ net.20@msr.ecss2 │ registered │     156 │
│ core1@ecss2 │ msr.ecss1 │ 3.18.1.0.10 │       1.0 │    0 │ db21af │ connected │ 00:41:11  │ 10.0.20.51:5700 │ net.20 │ 10.0.20.51 │ true   │ default │ local │ net.20@msr.ecss1 │ registered │     106 │
│             │ msr.ecss2 │ 3.18.1.0.10 │       1.0 │    0 │ 263898 │ connected │ 00:44:00  │ 10.0.20.52:5700 │ net.20 │ 10.0.20.52 │ true   │ default │ local │ net.20@msr.ecss2 │ registered │     177 │
└─────────────┴───────────┴─────────────┴───────────┴──────┴────────┴───────────┴───────────┴─────────────────┴────────┴────────────┴────────┴─────────┴───────┴──────────────────┴────────────┴─────────┘

Adding registrar control for MSR media manager in the Command Line Interface (CLI)


/system/media/registrar/ - regisrtrar control commands for the MSR media manager


Раскрыть
titleset

set

A command for changing common and individual parameters.

Command path:

/system/media/registrar/set

Syntax for setting common parameters:

set common <FIELD> <VALUE>

Parameters:

<FIELD> — name of the parameter being configured;

<VALUE> — value of the parameter being configured

Where:

  • common — the type of parameter being set;
  • <common parameter> — a common media registrar parameter for all nodes: registration-timeout;
  • private — the type of parameter being set;
  • <node name> — the name of the node on which the media registrarresides;
  • <private parameter> — a media registrar parameter that is set on <node name>: is-active, listen-interface, and listen-port.

List of parameters available for configuration:

  • is-active — enables or disables the registrar (false - deactivates the registrar, the registrar stops receiving SIP traffic);
  • listen-interface — the name of the interface the registrar uses;

  • listen-port — the port on which the registrar accepts registration requests (default 5000);

  • registration-timeout — re-registration timer, range from 60 to 86400.

In the general settings you can set the registration time; by default it is 60 seconds.

Example:
Set the registration time to 60 seconds:

Без форматирования
/system/media/registrar/set common registration-timeout 60
Common parameter registration-timeout set to 60.

Syntax for configuring individual parameters:

system/media/registrar/set private <CORE> <FIELD> <VALUE>

Parameters:

<CORE> — the core node for which the Registrar server is being configured;

<FIELD> — the name of the configurable parameter;

<VALUE> — the value of the configurable parameter.

Configurable parameters:

  • is-active — whether the Registrar server is active, true | false;
  • listen-ip — the IP address on which the Registrar server will accept connections (default 0.0.0.0);
  • listen-port — the network port on which the Registrar server will accept connections (default 5000).

Set the IP address for receiving connections from the media server:

Блок кода
titlein CoCon
/system/media/registrar/set private core1@ecss1 listen-ip 10.0.20.51


Блок кода
titlein CoCon
/system/media/registrar/set private core1@ecss2 listen-ip 10.0.20.52


Без форматирования
/system/media/registrar/set private core1@ecss1 listen-ip 10.0.20.51   
Private parameter listen-ip set to 10.0.20.51 at node core1@ecss1.

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


Раскрыть
titleinfo

info

Command for viewing the current Registrar server settings.

Command path:

/system/media/registrar/info


Без форматирования
/system/media/registrar/info
 Common parameters:
┌───────────────────────────┬───────┐
│         Parameter         │ Value │
├───────────────────────────┼───────┤
│ registration-timeout, sec │   180 │
└───────────────────────────┴───────┘
 Private parameters:
┌─────────────┬────────┬───────────┬────────────┬─────────────┐
│    Node     │ Status │ Is-active │ Listen-ip  │ Listen-port │
├─────────────┼────────┼───────────┼────────────┼─────────────┤
│ core1@ecss2 │ active │ true      │ 10.0.20.52 │        5000 │
│ core1@ecss1 │ active │ true      │ 10.0.20.51 │        5000 │
└─────────────┴────────┴───────────┴────────────┴─────────────┘

After all services are started, the nodes will take some time to establish communication. Once all nodes are loaded, the following information will be output when the system-status query is executed:

Без форматирования
languagebash
/system-status 
Checking...
┌─┬───────────────┬───────────────────────────┬───────────────────────────────┬─────────────────────┬───────┐
│ │     Node      │          Release          │         Erlang nodes          │    Mnesia nodes     │Uptime │
├─┼───────────────┼───────────────────────────┼───────────────────────────────┼─────────────────────┼───────┤
│ │core1@ecss1    │ecss-core-3.18.1.0.1656    │core1@ecss1,core1@ecss2        │not running          │43m 43s│
│ │core1@ecss2    │ecss-core-3.18.1.0.1656    │core1@ecss1,core1@ecss2        │not running          │47m 5s │
│ │ds1@ecss1      │ecss-ds-3.18.1.0.1656      │ds1@ecss1,ds1@ecss2            │ds1@ecss1,ds1@ecss2  │43m 43s│
│ │ds1@ecss2      │ecss-ds-3.18.1.0.1656      │ds1@ecss1,ds1@ecss2            │ds1@ecss1,ds1@ecss2  │47m 4s │
│ │md1@ecss1      │ecss-mediator-3.18.1.0.1656│md1@ecss1,md1@ecss2            │md1@ecss1,md1@ecss2  │43m 43s│
│ │md1@ecss2      │ecss-mediator-3.18.1.0.1656│md1@ecss1,md1@ecss2            │md1@ecss1,md1@ecss2  │47m 5s │
│ │mycelium1@ecss1│ecss-mycelium-3.18.1.0.1656│mycelium1@ecss1,mycelium1@ecss2│not running          │43m 43s│
│ │mycelium1@ecss2│ecss-mycelium-3.18.1.0.1656│mycelium1@ecss1,mycelium1@ecss2│not running          │47m 4s │
│ │sip1@ecss1     │ecss-pa-sip-3.18.1.0.1656  │sip1@ecss1,sip1@ecss2          │sip1@ecss1,sip1@ecss2│43m 43s│
│ │sip1@ecss2     │ecss-pa-sip-3.18.1.0.1656  │sip1@ecss1,sip1@ecss2          │sip1@ecss1,sip1@ecss2│47m 5s │
└─┴───────────────┴───────────────────────────┴───────────────────────────────┴─────────────────────┴───────┘

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.10 │ connected │ 00:42:49  │
│             │ msr.ecss2 │ 3.18.1.0.10 │ connected │ 00:42:48  │
│ core1@ecss2 │ msr.ecss1 │ 3.18.1.0.10 │ connected │ 00:43:38  │
│             │ msr.ecss2 │ 3.18.1.0.10 │ connected │ 00:46:27  │
└─────────────┴───────────┴─────────────┴───────────┴───────────┘

Alarms list on md1:
┌──────────────┬───────────────┬───────────────┬────────────────────┬────────────────────┬────────────────────┬────────────────────────────────────────────────────────────┐
│     Date     │   Severity    │   Location    │       Cause        │       Class        │      Instance      │                          Message                           │
├──────────────┼───────────────┼───────────────┼────────────────────┼────────────────────┼────────────────────┼────────────────────────────────────────────────────────────┤
└──────────────┴───────────────┴───────────────┴────────────────────┴────────────────────┴────────────────────┴────────────────────────────────────────────────────────────┘
Selected: 0
Total: 0

In the example above, the nodes have joined the cluster and the MSR have registered on the ecss-core node.

Creating and configuring a SIP IP address group (IP-set)

Configure the SIP adapter according to the specifications:

Блок кода
titlein CoCon
/cluster/adapter/sip1/sip/network/set ip_set test_set node-ip node = sip1@ecss1 ip = 10.0.20.31


Блок кода
titlein CoCon
/cluster/adapter/sip1/sip/network/set ip_set test_set node-ip node = sip1@ecss2 ip = 10.0.20.32


Блок кода
titlein CoCon
/cluster/adapter/sip1/sip/network/set ip_set test_set listen-ports list = [5060]


Без форматирования
languagebash
/cluster/adapter/sip1/sip/network/set ip_set test_set node-ip node = sip1@ecss1 ip = 10.0.20.31   
Property "ip_set" successfully changed from: 

   to
test_set: no ports set
test_set: sip1@ecss1 10.0.20.31
test_set: dscp 0.


/cluster/adapter/sip1/sip/network/set ip_set test_set node-ip node = sip1@ecss2 ip = 10.0.20.32
Property "ip_set" successfully changed from: 
test_set: no ports set
test_set: sip1@ecss1 10.0.20.31
test_set: dscp 0
   to
test_set: no ports set
test_set: sip1@ecss1 10.0.20.31
test_set: sip1@ecss2 10.0.20.32
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.31
test_set: sip1@ecss2 10.0.20.32
test_set: dscp 0
   to
test_set: 5060
test_set: sip1@ecss1 10.0.20.31
test_set: sip1@ecss2 10.0.20.32
test_set: dscp 0.

Creating a domain and connecting an IP-set

Create a Domain (virtual PBX) and assign it the SIP adapter settings group (IP set) created above:

Блок кода
titlein CoCon
/domain/declare test_domain --add-domain-admin-privileges --add-domain-user-privileges


Блок кода
titlein CoCon
/domain/test_domain/sip/network/set ip_set [test_set]


Блок кода
languagebash
/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"].

After creating a domain, the system administrator should grant access to the Domain (virtual PBX) operator to manage services. To do this, use the "test_domain" command to allow the Domain (virtual PBX) operator to manage all services:

Блок кода
titlein CoCon
/cluster/storage/ds1/ss/access-list add test_domain *


Без форматирования
languagebash
/cluster/storage/ds1/ss/access-list add test_domain *
Supplementary services successfully added in the domain test_domain.

To enable subscribers to apply a service package immediately after creation, it is necessary to configure a licensed service package application policy.

Create a license application policy named "new_sub"

Блок кода
languagebash
titlein CoCon
/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.

To set the name of the additional services package, use the following commands:

Блок кода
languagebash
titlein CoCon
/cluster/storage/ds1/licence/show-licence 1

The following information is important:

Без форматирования
languagebash
/cluster/storage/ds1/licence/show-licence 1
SSW ID                                                < Name SSW ID >
Description                                           Testing License Location 2.

. . .  

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

The service package name in this example is "ECSS-ADV".

Add the license service package named "ECSS-ADV" (that's how it's described in the license) to the created policy:

Блок кода
languagebash
titlein CoCon
/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.

The package has been added, but the policy is currently not active (cannot be applied to the subscriber). To activate the new_sub policy, run the following command:

Блок кода
languagebash
titlein CoCon
/domain/test_domain/ss/licence/politics/activate new_sub


Без форматирования
/domain/test_domain/ss/licence/politics/activate new_sub
Licence politic new_sub successfully activated.

Now we can use additional services when creating subscribers.

...