Mixer (mix)
Description
Provides preparation, packaging, linking and posting of call recording files based on system events. Placement is done in a shared repository (Localpaths - recstore), from where records are then distributed to domain repositories by the role recmover.
Reserved and scaled in mode Active-Active.
Organizes the startup and monitoring of the rtx_mixer application process in the operating system, which actually performs media processing.
Initiates the process of moving the record to domain stores.
Code |
|
Mode of operation |
|
Backup mode |
|
Types of sites |
|
Layer |
|
Placement |
|
Saving and restoring state on reboot |
|
appendix |
|
Managed application |
|
Limitations
-
Creates a dense CPU load at the time the mixdown is performed. When sharing a server with other roles, you should seriously limit the number of threads that can be used by a role, otherwise there is a risk of 100% CPU utilization on the server.
-
Mixing is performed in a process with minimum priority.
-
It is necessary to provide such an amount of processing power for a role on the site that, on an average day, all instances of the role have time to pack all conversations taking place on the site.
Parameters
| Name | Type | Default | Description |
|---|---|---|---|
|
|
required |
Name. May consist of Latin letters and numbers, must begin with a letter. |
|
|
required |
Role Type. Possible values: |
|
|
required |
The alias of the server network interface on which the roles will interact internally with each other. |
|
|
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. |
|
|
required |
Role ID. Unique for the entire system, regardless of the site or server. |
|
|
required |
An indication that the role has been allocated to a separate node. |
|
required |
A directory alias on the server for storing conversation recordings. |
|
|
|
empty |
Directory alias of the directory on the server to host the mixer service files. |
|
|
The number of channels in the file after mixing.
|
|
|
|
|
The format in which the audio recording file will be packaged after mixing. |
|
|
|
The maximum number of events that a role can receive from all queues in a single iteration. |
|
|
|
Sampling Frequency. |
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.
{
"name": "mix1",
"roletype": "mix",
"iface": "eth0",
"roleid": 11200,
"separate": false,
"recstorageid": "main4",
"channels": "2",
"encoding": "mp3",
"samplerate": "8000"
}