...

This section describes steps of the initial ECSS configuration before checking basic functionality.

Terms and definitions

• Alias — set of data about the subscriber;
• Bridge — virtual gateway that connects virtual PBXs. The term "bridge" was introduced to create means of controlling connections between virtual PBX. Calls between virtual PBX of the same ECSS-10 system are routed within this system via bridge. At the same time, inter-station connecting lines are not involved. The bridge is presented in the form of two interfaces connected to each other. Each interface is declared in its own virtual PBX. For a bridge, as for a classic trunk, various types of restrictions can be set, for example, the number of channels, which gives a limit on the number of simultaneously established connections between virtual PBX and allows normalization of the load;
• Domain (virtual PBX) — collection consisting of many routing contexts, interfaces, and aliases. The closest equivalent is a description of the numbering and routing plan within the framework of a classical telephone exchange for traditional networks;
• Cluster — complex of elements of the same type that perform, from the system point of view, a single function. With their help, the computational topology of the system is described. In this system, the cluster element is a node. A cluster exists as long as it includes at least one node;
• Media resources — description of the media server parameters required to work with it;
• Media server (MSR) — component of the ECSS-10 system designed for speech and video information processing over the RTP protocol, organizing conferences, recording conversations, playing media files and various combinations of these modes. Media server resources are managed using the control channel mechanism (RFC 6230 Media Control Channel Framework, RFC 6231 IVR Control Package, RFC 6505 Mixer Control Package);
• Node — is Erlang virtual machine and an element of the ECSS-10 computing cluster. Nodes in ECSS-10 are typed according to the functionality performed on them. The same type of nodes are combined into clusters of the appropriate type. Example: the Core cluster consists of nodes that perform the function of the switching system core;
• IVR (Interactive Voice Response) — system of prerecorded voice messages that performs a routing function in call center or PBX, using information entered by the client on the telephone keypad using tone dialing;
• LDAP (Lightweight Directory Access Protocol) — application-level protocol for accessing the directory service;
• RADIUS — protocol providing a centralized method of authenticating users by accessing an external server. The RADIUS protocol is used for authentication, authorization, and accounting. The RADIUS server operates with a user database that contains authentication data for each user. Thus, the use of RADIUS protocol provides centralized management and additional protection when accessing network resources.

Prerequisites

Before starting configuring, make sure the following:

• operating system is installed;
• network is configured;
• necessary software is installed;
• necessary ECSS components are installed;
• NTP service is configured;
• Token is connected and operating;
• all ECSS subsystems are up and running;
• the correct passport and license are installed;
• if the system is in a cluster, then additionally:
  • keepalived configured and works correctly;
  • MySQL database replication works;
  • nodes are at work and "see" each other;
  • GlusterFS is configured and running.

Initial configuration order

First of all, perform general settings for the entire system:

...

It is recommended to perform the initial setup in the order given below.

Configuring clusters

Classification of clusters by roles:

...

• CLI — Command Line Interface (for a description of the commands for managing clusters, see /cluster/);
• Clusters application in the web configurator.

General commands for configuring cluster properties

These commands are the main ones for setting any cluster.

...

• <SOME_ROLE> — cluster role: adapter, bus, core, mediator, storage;
• <NAME_CLUSTER> — cluster name;
• <GROUP> — group of parameters;
• <NAME_NODE> — node name;
• <PROPERTY> — property name;
• <VALUE> — property value.

STORAGE cluster settings

The storage cluster performs a function of a distributed configuration data storage of the entire system. Also, a telephone call routing module is implemented within this subsystem.

Configuring via CLI (CoCon)

To change individual cluster settings, use the command:

...

admin@mycelium1@ecss1:/$ cluster/storage/ds1/ss/install ds1@ecss1 ss_fax_receiver.xml               
Successfully installed: /var/lib/ecss/ss/ss_fax_receiver.xml

Configuring cluster parameters via web interface

The Clusters application is used to view and change cluster properties, where a cluster with storage role should be selected.

To manage services in the web configurator, the Service Management (SS install) application is used.

Configuring MEDIATOR cluster parameters

The mediator cluster is designed to collect and export warnings and statistical information.

Configuring via CLI (CoCon)

To change individual cluster settings, use the command:

...

admin@ds1@ecss1:/$ ls -t /cluster/mediator/
|-/md1
  |-/alarms
  | |-*clear
  | |-*delete
  | |-*export
  | |-*generate-alarm
  | |-*list
  | |-*maskadd
  | |-*maskdel
  | |-*masklist
  | |-*maskmod
  | |-*masktrace
  | |-*res-cleanup
  | |-/notifiers
  |   |-/email
  |   | |-*clean
  |   | |-*info
  |   | |-*send_test_email
  |   | |-*set
  |   |-/jabber
  |     |-*clean
  |     |-*info
  |     |-*send_test_jabber
  |     |-*set
  |-/ap
  | |-*speaker-off
  | |-*status
  |-/properties
  | |-/cocon_http_terminal
  | | |-*clean
  | | |-*info
  | | |-*set
  | |-/rpss
  |   |-*clean
  |   |-*info
  |   |-*set
  |-/sip
  | |-/isup-cause-messages
  | | |-*clean
  | | |-*info
  | | |-*set
  | |-/sip-error-messages
  | | |-*clean
  | | |-*info
  | | |-*set
  | |-/sip-internal-messages
  | | |-*clean
  | | |-*info
  | | |-*set
  | |-/sip-status-messages
  |   |-*clean
  |   |-*info
  |   |-*set
  |-/snmp
  | |-/agent
  |   |-/properties
  |     |-*clean
  |     |-*info
  |     |-*set
  |-/statistics
    |-*add
    |-*addcolmap
    |-*delcolmap
    |-*delete
    |-*list
    |-*statmodinfo

Configuring cluster parameters via web interface

The Clusters application is used to view and change properties, where a cluster with mediator role should be selected. To configure the masking of warnings, the Alarm list application is used.

Configuring CORE cluster parameters

The core cluster implements the logic of managing telephone calls processing (Call Control functions), providing services and billing functionality provision.

Configuring via CLI (CoCon)

To change individual cluster settings, use the command:

...

• call notification service parameters;
• TTS subsystem for CDR collection.

Configuring cluster parameters via web interface

The Clusters application is used to view and change properties, where cluster with the core role should be selected. The CDR is configured in the CDR Manager application. 

Configuring PA_SIP cluster parameters

Configuring via CLI (CoCon)

To change individual cluster settings, use the command:

...

Configuring cluster parameters via web interface

SIP transport parameters can also be configured using the web configurator. To configure the interface, open the Clusters application, select the adapter and enter the transport parameters. 

Configuring a software media server

The procedure for configuring the software media server (MSR):

• configuring the media server file;
• starting the media server;
• adding media resources to ECSS-10:
  • by CLI commands (/system/media/resource/);
  • via web configurator application MSR registrars.

Creating and configuring domains (virtual PBX)

This step includes the process of creating virtual PBX, setting up call routing rules, trunks, subscribers, subscriber service rules.

Domain declaration 

Якорь
domain domain

It is necessary to create a domain for each of the projected domains. When creating, add the ECSS-10 administrator to the Administrators group, as well as to the Users group of this domain.

Virtual PBX configuration procedure (domain)

The entire infrastructure for providing telephone services based on ECSS-10, namely the configuration of connected gateways, subscriber data, numbering plan and routing rules, as well as access rights to operational management and support functions are described within a specific domain.

...

After creating domains, the necessary domain-level directories will be automatically created in the file system.

Configuring routing

Description of the call routing process in the ECSS-10 system is given in the section "Virtual PBX. Telephone call routing v2".

Creating routing contexts

In accordance with the project, it is necessary to create call routing contexts that will be used in the domain settings in the future.

...

Further, if it is defined in the project, it is necessary to prepare modification and adaptation contexts also for each domain. 

Applying routing contexts to system interfaces

Routing contexts must be assigned for the system:ivr and system:teleconference interfaces. Settings are made using CLI commands. The path of the commands is /domain/<DOMAIN>/system-iface/.

Adding and configuring user rights

Users are subjects who work with the system via СoСon or web configurator.

...

To differentiate rights, create the required number of users and assign rights and roles to each. For more information, see /cocon/ commands description. For convenience's sake, each user can configure the parameters of the CoCon shell using the global command /shell-options.

Configuring subscriber service limiting rules

To apply different subscriber level limitations, configure them for each domain.

...

• via the Command Line Interface, see commands:
  • /domain/<DOMAIN>/access-group — access group management commands;
  • /domain/<DOMAIN>/access-type — access type management commands;
  • /domain/<DOMAIN>/regime/ — maintenance mode management commands subscribers.
• via web configurator application Access manager.

Creating and configuring subscribers

In accordance with the project, create the required number of subscribers in the domains. It can be done using the CLI command  /domain/<DOMAIN>/sip/user/declare or using web configurator application Subscriber card.

...

Subscribers in the domain is an optional condition, there may be purely transit domains in the system, on which the appropriate rules for passing calls are configured.

Creating and configuring trunks

...

Then, if necessary, supplementary services are configured on the trunks.

Creating and configuring bridge interfaces

...

• via web configurator application Bridge manager.

Setting restrictions

For each domain, it is possible to set different kinds of restrictions within the licence.

...

• via command line interface, see /domain/<DOMAIN>/properties/restrictions/ — commands for managing virtual PBX restrictions;
• via web configurator application Domains (Domain Properties →> System Properties →> Restrictions).

IVR Scenarios

Additional IVR scenarios can be configured for each virtual PBX, if they are immediately provided by the project. Scripts are created in the web configurator application IVR editor. Scripts can also be managed using CLI commands. See /domain/<DOMAIN>/ivr/ — IVR script management commands.

...

• via Command Line Interface, see section /system/ivr/script/restrictions/ — management commands for IVR script restriction settings;
• via web configurator application IVR restrictions manager.

Configuring supplementary services

Use of supplementary service applications that expand the functionality is available as a part of the ECSS-10 ecosystem:

...

Contact technical support for consultation on configuring. 

Configuring ECSS-10 for productive systems

For productive systems, ECSS-10 configuring consists of the following steps:

Allocation of individual processor cores for MSR

In order to isolate the MSR media server from the rest of the system, it is necessary to allocate separate processor cores for it. To allocate individual processor cores, perform the following steps:

1. Open the file:

   Без форматирования
   /etc/default/grub

   bring the GRUB_CMDLINE_LINUX="" parameter to the following form:

   Без форматирования
   GRUB_CMDLINE_LINUX="isolcpus=8-11"

   This example isolates cores from 8 to11. It is also possible to list 1, 2, 4-6, etc.

2. Update the grub configuration. To do this, run the command:

   Без форматирования
   sudo update-grub

   
   

3. Restart the system. 

   If everything is done correctly, then after a reboot htop will show zero load on isolated cores.

Setting scaling_governor to performance mode

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors conservative ondemand userspace powersave performance

...

Running MSR on isolated CPU cores

For MSR to run on separate processor cores, it is necessary to bring the /etc/systemd/system/ecss-media-server.service.d/override.con file to the following format:

...

MSR configuring is described in more detail on the page Configuring the software media server.

Configuring use of specific processor cores for erlang-based services

In order for processor cores to be used correctly, it is necessary to adjust the startup parameters of erlang nodes on productive systems.

...