Versions Compared

Old Version 1

changes.mady.by.user Kiss, Mate

Saved on

compared with

New Version 2

changes.mady.by.user Zszugyi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

CUCM configuration for selective recording

The Verba JTAPI user must have the Standard CTI Allow Recording group membership.

The extension configuration is detailed in the Adding a new extension for recording in Cisco UCM.
The Recording Option at the Directory Number has to be set to Selective (Step 4b), and the Phone Device has to be added to the Verba JTAPI user as Controlled Device.(Step 8)

Verba configuration for selective recording

The Recording Mode of the Extension has to be set to full.

Recording rule configuration

...

Field Name

Description

ID
Auto-generated identifier.

Name

Name of the section.

Action

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.

Filters

Defines when this section should be performed.

The following CDR fields information can be used in the filters:

  • Caller Party
    • The phone number, UPN, or other unique user ID of the calling party.
  • Called Party
    • The phone number, UPN, or other unique user ID of the called party.
  • Any Party
    • The phone number, UPN, or other unique user ID of any of the call parties. In case of meetings, it applies to all meeting participants.
  • Partition (Cisco JTAPI)
    • The partition ID of the Cisco partition.
  • Genesys Field
    • Any Genesys metadata template field can be specified by typing the name set as a filter by specifying the Property ID of the field.
    • Custom user data fields should be prefixed with "UserData.", for example: UserData.ShouldRecord
  • Cisco UCCE Field
    • Any UCCE metadata template field can be specified by typing the name set as a filter by specifying the Property ID of the field.
  • Cisco UCCX Field
    • Any UCCX UCCX metadata template field can be set as a filter by specifying the Property ID of the field.

  • Microsoft Teams Field

    • Any Microsoft Teams metadata template field can be set as a filter by specifying the Property ID of the field.

  • Nimbus Field

    • Any Nimbus metadata template field can be specified by typing the name of the fieldset as a filter by specifying the Property ID of the field.

  • Caller Tenant (Microsoft Teams)

    • The Microsoft Teams tenant ID associated with the tenant of the calling party.

  • Called Tenant (Microsoft Teams)

    • The Microsoft Teams tenant ID associated with the tenant of the called party.

  • Any Tenant (Microsoft Teams)

    • The Microsoft Teams tenant ID associated with the tenant of any of the call parties.


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