Delegate tagging

Note the following tagging behavior for cases where users are designated delegates.

Scenario 1

User B (delegate) is not configured in the BOT profile in Azure, but is configured in Enterprise Manager under the profile in the data source. User A is configured in the Azure profile, and B is defined as A's delegate. The call is recorded and tagged as expected, because User B is a participant in the call and is configured in the data source profile. The recording is kept.

For the side that is represented as User B (ANI or DNIS), tagging will indicate "userB (on behalf of userA)." The extension will be "userB". In this configuration, when User B makes a call, not on behalf of User A but on behalf of User B, the call is not recorded as expected, because User B is not configured in the BOT profile.

If the other party is recorded, there will be a recording.

Scenario 2

User B (delegate) is not configured in the BOT profile in Azure nor in Enterprise Manager under the profile in the data source. The call is recorded, as events from the BOT are still received, since User A is configured to be recorded. The recording is only kept if the member group fallback mode in Enterprise Manager is set to "Liability." Liability mode means that all recordings are kept when no CTI is available. The Recorder Integration Service otherwise has no ability to create CTI sessions and tag the recording with CTI.

In this case, only call audio is recorded and kept by default, as currently video and screen share require special triggering within the Enterprise Manager recording profile configuration.