Recorder Analytics Framework server role to servers associations

Use Server Associations for the Recorder Analytics Framework Comprises the Recorder-based set of components shared by all the Real-Time Analytics (RTA) Framework solutions, part of Real-Time Speech Analytics as well as Identity Authentication and Fraud Detection (IAFD, also known as voice biometrics). role to associate an instance of the role with one or more servers. The association determines which Recorder Analytics Framework role each server uses.

In most deployments, the Recorder Analytics Framework role on each Recorder must be associated to that Recorder. This association ensures that Analytics campaigns are processed on each Recorder against the recordings for that Recorder only.
For deployments using centralized biometrics (using extra servers for historical detection Function of the IAFD product that compares a caller’s voice to one or more voiceprints in a watch list to detect if a target is participating in a call. and verification Feature in voice biometrics where the speaker’s voice is compared to a collection of employee or customer voiceprints that should match the call. If a match occurs, the speaker is said to be verified.), the Recorder Analytics Framework role on Recorders must not be associated to that Recorder. The Recorder Analytics Frameworks on the centralized biometrics servers is associated with the Recorders. This association ensures that the Recorders do not run any voice biometrics campaigns.

To perform historical detection or verification

Associate every Recorder to a single instance of the Recorder Analytics Framework on a server running the Voice Biometrics Engine.

The simplest method is to associate each Recorder to the local instance of the Recorder Analytics Framework.

This association causes the Recorder Analytics Framework on each Recorder to process all historical detection and verification Analytics Rules against the recordings for that recorder only.
Alternatively, associate each Recorder to a single instance of the Recorder Analytics Framework on one centralized biometrics server.

This association causes each centralized biometrics server to process all historical detection and verification Analytics Rules against the set of recorders to which it is associated.

To perform automatic enrollment Process in the IAFD product where an employee, customer, or target is registered and the system is then able to assist with identity verification and watch list detection when that speaker is on a call.

Associate every Recorder to a single instance of the Recorder Analytics Framework on a server running the Voice Enrollment Engine.

The simplest method is to associate each Recorder to the local instance of the Recorder Analytics Framework.

This association causes the Recorder Analytics Framework on each Recorder to process all automatic enrollment rules against the recordings for that Recorder only.
Alternatively, associate each Recorder to a single instance of the Recorder Analytics Framework on a centralized enrollment server.

This association causes each centralized enrollment server to process all automatic enrollment rules against the set of Recorders to which it is associated.

If you fail to associate a Recorder to any instance of the Recorder Analytics Framework with a specific engine, then no historical (post-processing) Recorder Analytics Rules for that engine are processed against the recordings for that Recorder.

If you associate a Recorder to multiple instances of the Recorder Analytics Framework with a specific engine, then all historical Recorder Analytics Rules for that Engine are processed multiple times against recordings for that Recorder, which wastes resources and duplicates results.

Related information

For complete information about all deployment scenarios supported, refer to the Real-Time Analytics (RTA) Framework Server Role Deployment Guide.