Automatic speech recognition rules for recorded conversations (asrrule)
Description
Rule for applying automatic recognition of a telephone conversation into text.
Applied after the conversation ends at the set time.
Works only when a connection to the recognition service is configured in the master domain (settings.record_asr_options).
In one telephone conversation, participants may belong to different domains.
The recognition decision process consists of
(1) Determining the call participants and their domains and preparing search parameters.
(2) Determining the recognition rule in the initiator’s domain.
(3) For a cross-domain call, determining the recognition rule in the called subscriber’s domain.
(4) Making the recognition decision based on a positive recording decision in at least one of the domains.
(5) Generating an event in each domain configured for recording and recognition.
By default, conversations are not sent for recognition.
Fields
{
"id": uuid,
"priority": int,
"dir": str,
"fromnumber": str,
"tonumber": str,
"crossdomain": str,
"asr": intbool,
"schedule": str,
"periods": array<object>,
"opts": {
"title": str,
"comment": str
}
"ext": {
"ct": date,
"lwt": date
}
}
| Specification | Description |
|---|---|
Field: |
Identifier. Can be specified at creation, otherwise generated by the system. |
Field: |
Priority. A lower value means higher priority. |
Field: |
Filter by call direction. |
Field: |
Call initiator number filter mask. |
Field: |
Called subscriber number filter mask. |
Field: |
Other domain filter mask. |
Field: |
Action determinant. |
Field: |
|
Field: |
Activity interval during the week. |
Field: |
|
Field: |
Arbitrary title |
Field: |
Arbitrary comment |
Field: |
Allows extending the compound with arbitrary keys and values |
Field: |
Object creation time |
Field: |
Time of last modification of the object |
Call direction filter options
| Value | Description |
|---|---|
|
The rule can be applied only to intra-domain calls where both parties are subscribers of the current domain |
|
The rule can be applied only to cross-domain calls where the called party is a subscriber of the current domain |
|
The rule can be applied only to cross-domain calls where the initiating party is a subscriber of the current domain |
|
The rule can be applied to all calls where at least one party is a subscriber of the current domain |
Filter operation modes
| Mode | Description |
|---|---|
|
The value being checked is passed through the filter character by character.
If one of the service characters must be specified as a target, it should be enclosed in square brackets, e.g. For example, |
|
The Pattern template is applied to the source value. Structure of the regex template value: For example,- value:
All standard regular expression rules can be used when forming Pattern templates. |
|
"The value being checked is an integer and falls within the specified range of numeric values. Structure of the dia template value: For example,- value: |
Work schedule
| Value | Description |
|---|---|
|
The rule is always available for application |
|
The rule is never available for application |
|
The rule is available for application only during working hours |
|
The rule is available for application only outside working hours |
|
The rule defines an individual availability schedule in the |
Weekly schedule list element
| Field | Value | Description |
|---|---|---|
|
|
Day of week when the segment starts ( |
|
|
Day of week when the segment ends ( |
|
|
Start time of the segment within the day, in minutes |
|
|
End time of the segment within the day, in minutes |