Skip to end of metadata
Go to start of metadata

Selective recording rules can be used to define when an extension should be recorded in a more complex way based on various CDR fields.

Currently, this feature is supported only in Cisco JTAPI based selective recording integrations including Cisco UCCX, Cisco UCCE, and Genesys.

Recording rule configuration

You can add / modify / delete recording rules under the Administration / Recording Rules menu.


The following table describes the available fields in the basic recording rule configuration:

Field Name


Auto-generated identifier


Name of the recording rule

DescriptionLonger description of the recording rule
Rule SectionsThe rule logic

Rule section

A recording rule consists of several rule sections. The sections are evaluated in sequence one after the other. The recorder engine will perform the first matching section's action, and the rest will not be evaluated.

Each section defines the desired action and various filters that will be evaluated in order to determine if the section matches a conversation or not. The logical relation between the filters is AND so that all of the filters should match the conversation (within a section).

If a section has no filters, then it will always be evaluated as matching. Such section can be used to define a default behavior, practically as the last section of a rule. If no section matches a conversation, then no action will be performed, that is the conversation will not be recorded.

The following table describes the available fields within a recording rule section:

Field Name


Auto-generated identifier.


Name of the section.


What should the system do when this section matches a conversation.

Possible actions:

  • Do not record
  • Record
CTI Triggered Recording

If the recording is not triggered automatically by the PBX, but the recorder has to initiate the recording, then this option has to be turned on.

Example: when a Cisco extension's recording mode is Selective.


Defines when this section should be performed.

The following CDR fields can be used in the filters:

  • Caller Party
  • Called Party
  • Any Party
  • Partition (Cisco JTAPI)
  • Genesys Field
    • Any Genesys field can be specified by typing the name of the field
    • Custom user data fields should be prefixed with "UserData.", for example: UserData.ShouldRecord
  • Cisco UCCE Field
    • Any UCCE field can be specified by typing the name of the field
  • Cisco UCCX Field
    • Any UCCX field can be specified by typing the name of the field


Matching patterns (the listbox next to the field):

  • DOS: DOS-style wildcard characters can be used
    • asterisk (*) matches any sequence of characters
    • question mark (?) matches any single character
  • Regular Expression
  • Simple