Meet (meet)

Table of Contents

Description
Parameters
Configuration example
See also

Description

Starts the videoconferencing server Era Meet.

Reserved in mode Active-Passive.

Forms collections/classes: meet/Rooms, meet/Users, meet/RoomSessions, meet/UserSessions, meet/Messages, meet/records, meet/Feedbacks. Allows their further modification in the direction of extending the composition of properties and variants of values of enumerated fields.

Creates classes in the domain center for use by the server Era Meet.

Table 1. System Characteristics

Code	`meet`
Mode of operation	`Service`
Backup mode	`Active-Passive`
Types of sites	`Any`
Layer	`Service`
Placement	`Internal`
Saving and restoring state on reboot	`Yes`
appendix	`era_meet`

Parameters

Description of columns in the table

Table 2. Parameters
Name	Type	Default	Description
`name`	`str`	required	Name. May consist of Latin letters and numbers, must begin with a letter.
`roletype`	`str`	required	Role Type. Possible values: `"meet"`.
`iface`	`str`	required	The alias of the server network interface on which the roles will interact internally with each other.
`ext`	`json`	empty	Additional role options. Contains a json object or list.
`enabled`	`bool`	empty	Role activity flag. When set to false, the role does not participate in validation and is not started.
`roleid`	`int`	required	Role ID. Unique for the entire system, regardless of the site or server. Cannot be changed. Integer from `1` to `9999`.
`separate`	`bool`	required	An indication that the role has been allocated to a separate node.
`group`	`int`	required	Group Number. As part of horizontal scaling, a role can be divided into multiple groups on a site, with only one instance active in each group and the rest reserved. Responsibilities between groups are shared across domain sets. Together, all groups maintain a complete domain set. All roles in the same group must have the same responsibility. Integer from `1` to `9999999`.
`order`	`int`	required	The order of a role instance within a group. Defines in what order the flow in the mode will take place Active-Passive.
`include_domains`	`array<str>`	empty	A list of domain names served by this group. Any domain of any level can be specified. Specifying a domain causes its subdomain tree to be served on this group and not on other role groups, excluding only those branches mentioned in other groups. Collectively, all role groups on a site serve a complete domain tree.
`listeniface`	`str`	node_iface	The alias of the network interface on which the Era Meet server listener will be started. Default: the alias of the network interface of the node that runs the server.
`announcediface`	`str`	node_iface	The alias of the network interface that is accessible from the outside. Default: the alias of the network interface of the node that runs the server.
`port`	`int`	required	Local port on which the server listener will be started Era Meet.
`license_path`	`str`	required	Alias to the file containing the license for the server Era Meet.
`monitoring_enabled`	`bool`	`true`	Every second preparation of the current report, about the Warkers and rooms with logging and providing on the link /monitoring/<report_password>
`cert_domain`	`str`	required	The domain to which the certificate was issued.
`certdir`	`str`	empty	Alias of the directory on the server for storing certificates (files fullchain.pem and privkey.pem), in case it is necessary to specify the chain of certificates up to the CA (Certification Authority) it should be placed at the end of the certificate file.
`turn_iface`	`str`	node_iface	The alias of the network interface that is accessible from the outside. Default: the alias of the network interface of the node that runs the server.
`turn_port`	`int`	empty	Local port on which the coturn listener will be started. Default: 0 - listener is not raised.
`turn_port_tls`	`int`	empty	Local TLS port for coturn. Default: 0 - listener is not up.
`turn_certdir`	`str`	empty	Alias of the directory on the server for storing certificates (files fullchain.pem and privkey.pem), for the turn service. In case it is necessary to specify the chain of certificates up to the CA (Certification Authority) it should be placed at the end of the certificate file.
`listeniface_http`	`str`	empty	Alicase of the network interface on which the server listener will run Era Meet (http).
`port_http`	`int`	empty	Local port (http) on which the server listener will be launched Era Meet.

Configuration example

The configuration is managed in an application available to master domain administrators. The application hides the full content of the configuration, but it is nevertheless accessible via the API.

The configuration contains a section to describe all instances of all roles. Parameters are defined for each specific role instance.

Example node

{
  "name": "meet1",
  "roletype": "meet",
  "iface": "eth0",
  "group": 11420,
  "order": 1,
  "roleid": 11420,
  "separate": true,
  "listeniface": "eth0",
  "port": 4123,
  "cert_domain": "my.host.ru",
  "certdir": "alias://paths/meet_certdir",
  "license_path": "alias://paths/meet_license",
  "monitoring_enabled": true,
  "report_password": "reppass",
  "default_domain": "td1",
  "log_level": 3
}

Meet (meet)

Description

Parameters

Configuration example

See also