Mark Oliver's World

Ghost Calls In A Microsoft Teams Compliance Recording Bot _ Part 2

20/06/2024

This is one of many posts in a series on Microsoft Teams Compliance Recording .

I wrote the other day about "Ghost Calls" sent from MSTeams to the Compliance Recording Bot. I now have a bit more information and an idea as to what is happening.

When a user has a Compliance Recording Policy against them, and they make a MSTeams call, Teams sends the recording bot a call (created) notification .

We know now, that MSTeams expects a response to that call notification in the form of an Answer or a Reject within 5 seconds of the notification being sent.

If an Answer/Reject is not received within that time, then a deleted notification (with a subcode of 8544) is sent from MSTeams as if to say Tough, you were too slow to respond, so the call will continue without you!.

But sometimes, we then get MSTeams sending us a new and different notification for a new call (effectively a retry), so I think this may be happening for 1 of 2 reasons:

  1. The Compliance Recording Policy for the user REQUIRES the call to be recorded before it can start, so it will retry before failing the call.
  2. The person being called has not yet answered the call and therefore MSTeams is giving another chance to include the bot.

More testing is required to determine if either of these ideas are true.

Let me know if you have any other ideas.

Thank you for your time.

If you want to reach out, catch me on Twitter!