/
Microsoft Teams Bot Service: Potential recording loss due to missing participant update alert

Microsoft Teams Bot Service: Potential recording loss due to missing participant update alert

Potential Recording Loss Due to Missing Participant Update Alert

Content

Alert: Potential recording loss due to missing participant update
Service: <SERVICE_NAME>
Computer name: <COMPUTER_NAME>
Alert id: .122.0.10
Time: <TIME> (UTC)
Severity: Warning

Description:
The call was not recorded because of the missing participant updates but the number of active participants is more than one.

Active Speakers (mediaSourceID: rtpCount):
<LIST_OF_ACTIVE_SPEAKERS>

Alert attributes:

Azure User Id (OID: .200.18): Entra ID of the recorded user
Call Start Time (OID: .200.20): Call Start Time (UTC)
Teams Tenant Id (OID: .200.16)
Call Id (OID: .200.5)
X-Microsoft-Skype-Chain-Id (OID: .200.19)
Description (OID: .200.1): The call was not recorded because of the missing participant updates but the number of active participants is more than one.

Cause

This alert is generated if there are more than one active speaking participants at the end of the call, and the call should have been recorded but the recording never started because the necessary participant update for triggering the recording was missing.

Resolution

If you receive this alert, please contact Verint support and provide the teamsbot.log file from the server on which the Teams Bot service is running. The file is available in the APPLICATION_FOLDER\log folder.