Mixer (mix)
Description
Prepares, packages, joins, and places call recording files based on system events. Placement is performed in a common storage (Local paths - recstore), from where recordings are then distributed to domain storages by the recmover role.
Made redundant and scaled in Active-Active mode.
Starts and monitors the rtx_mixer application process in the operating system, which actually performs media data processing.
Initiates the process of moving the recording to domain storages.
Requires the Message Broker to be configured.
Code |
|
Operation mode |
|
Redundancy mode |
|
Site types |
|
Layer |
|
Placement |
|
State preservation and recovery on restart |
|
Application |
|
Managed application |
|
Limitations
-
Creates a heavy CPU load during mixing. When sharing a server with other roles, the number of threads available to the role should be seriously limited; otherwise there is a risk of 100% CPU load on the server.
-
To avoid a negative impact on main processes, mixing is performed at reduced priority (nice=12).
-
The site must provide enough computing power for the role so that, on average during the day, all role instances have time to package all conversations held on the site.
-
If the mixer cannot place a task in storage (incorrectly configured folder or unavailable NFS server), the mixing process waits for it to appear, and tasks accumulate in the working directories of the nodes running mixer instances. The limit is the disk space in the partition with the /var/lib directory (of the container).
Parameters
| Name | Type | Default | Description |
|---|---|---|---|
|
|
required |
Name. May consist of Latin letters and digits and must start with a letter. |
|
|
required |
Role type. Possible values: |
|
|
empty |
Additional role options. Contains a JSON object or list. |
|
|
empty |
Role activity flag. When set to false, the role does not participate in validation and is not started. |
|
|
empty |
Limit on the number of CPU logical cores used. Default: 0 - unlimited. |
|
|
empty |
Default logging level set specifically for the role instance (microservice type). More |
|
|
|
Flag allowing parameter differences in roles of the same group. Default: false - not allowed. |
|
|
required |
Role identifier. Unique across the entire system, regardless of site or server. |
|
|
required |
Flag indicating whether the role is allocated to a separate node. |
|
required |
Configuration code of the call recording storage on the server (server.recstorepaths.key), which in turn contains an alias of the server directory for storing call recordings without division by domains. The key, alias, and path may differ from the target destination used in recmover. In addition, recmover can place recordings in domain storages based on domain settings (storages and recording rules). |
|
|
|
empty |
Alias of the server directory for placing mixer service files. |
|
|
Number of channels in the file after mixing.
|
|
|
|
|
Format into which the audio recording file is packaged after mixing. |
|
|
|
Maximum number of events the role can receive from all queues in one iteration. |
|
|
|
Audio stream sampling rate. |
|
|
|
Audio stream bitrate. The value must be a multiple of the 'samplerate' parameter. Otherwise, the nearest multiple is used. |
|
|
|
Debug flag. Allows disabling deletion of source per-channel RTP recordings from the media gateway immediately after mixing completes. |
Configuration example
Configuration management is performed in an application available to master domain administrators. The application hides the full configuration content, but it is still available through the API.
The configuration contains a section describing all instances of all roles. Parameters are defined for each specific role instance.
{
"name": "mix1",
"roletype": "mix",
"roleid": 11200,
"separate": false,
"recstorageid": "main4",
"channels": "2",
"encoding": "mp3",
"samplerate": "8000"
}