Skip to content

Recording rules

Recording rules decide, per call, whether the recorder keeps the audio. They let you record everything for one tenant, record on demand for another, and skip internal calls for a third — without touching the phone-system side of the integration.

Where: Administration › System › Recording Rules. The page has four tabs: Settings (the default rule and related options), Custom rules [before], Auto rules, and Custom rules [after].

Note

This page describes the generic rule engine. For a worked, platform-specific walkthrough — including the platform-side policy that must deliver calls to the recorder in the first place — see Teams Recording Rules in the Microsoft Teams Integration Guide.

Rule levels and evaluation order

MiaRec evaluates rules from most to least specific. The first matching rule wins:

  1. Custom rules [before] — exception rules you create, evaluated first.
  2. User auto rules — from the Record setting on each user profile (Always / On-demand / Never / Default); applies to calls associated with that user.
  3. Tenant auto rules — from the Record unknown users setting on the tenant profile; applies to calls associated with the tenant but not with any user.
  4. Custom rules [after] — rarely used; evaluated after the auto rules.
  5. Default recording rule — the system-wide fallback for calls that matched nothing above.

The user- and tenant-level settings are edited on the user and tenant profiles; the Auto rules tab shows the resulting rules in one place for convenience. Correct rule matching therefore depends on calls being associated with the right tenant and user — see the association settings in Tenant configuration.

The default rule and settings

On the Settings tab, click Edit Configuration:

  • Default recording rule — one of:
    • Record — record the call.
    • On-demand — the user can turn recording on or off during the call; if no action is taken, the recording is discarded.
    • On-demand (default: keep) — same, but the recording is kept when no action is taken.
    • Do not record — never record.
  • Ignored calls processing — "Save metadata for ignored calls": keeps the call record (without audio) for calls the rules declined.
  • On-demand recording — '"Look-back" on-demand recording': when enabled, on-demand recordings include audio from the beginning of the call; otherwise audio starts at the moment recording is triggered.
  • Pause recording timeout — automatically resume a paused recording after the given number of seconds (0 disables the timeout).

Custom rules

Custom rules express exceptions: record everything for this tenant unless the call is outbound, or do not record calls of a given type. Click Add on the Custom rules [before] tab and define:

  • Tenant — the tenant the rule belongs to.
  • Condition — the match criteria (call attributes such as direction or platform-specific metadata fields).
  • Action — Record / On-demand / On-demand (default: keep) / Do not record.
  • Position — before or after the auto rules (before is the common case).

Prefer 'Do not record' exceptions

Structure custom rules as record by default, except… with the Do not record action. A custom rule with the Record action can consume an additional recording license when it triggers on a call for a user who is already licensed through the auto rules, leading to license oversubscription.

Early check of recording filters

By default, the recorder postpones rule evaluation until media (RTP) is received: recording starts for every call and the audio is discarded later if the rules decline it. That is invisible to callers — unless recording announcements are enabled, in which case participants can hear an announcement for a call that is ultimately not recorded.

To evaluate rules before recording starts, enable Early check of recording filters under Administration › System › Recording Interfaces › SIPREC (Recording Filters Behavior section). In multi-platform deployments, apply it per recorder instead with an override (Category Protocol::SIPREC, Key EarlyCheckRecordingFilters, Value true) — see Recorder servers.