Bot problem: Client Media Error

[vidilab]

Our policy recording bot is removed from a call halfway during a call. We would like it to remain in the call until the end.

Currently using library version 1.2.0.7270.

Call IDs:

34003580-931f-4d23-9cee-46cfb7745e39 (2024-10-08T09:04:23.9993188Z)
40005180-3432-4177-ad93-a6e9b360f13d (2024-10-08T09:15:38.4361194Z)
6d003880-cdb4-4b38-8d60-69067b71bd2d (2024-10-08T09:15:38.5161160Z)

Logs contain:

      "@odata.type": "#microsoft.graph.commsNotification",
      "changeType": "Deleted",
      "resourceUrl": "/communications/calls/6d003880-cdb4-4b38-8d60-69067b71bd2d",
...
        "resultInfo": {
          "@odata.type": "#microsoft.graph.resultInfo",
          "code": 410,
          "message": "Client Media Error. DiagCode: 410#301005.@",
          "subcode": 301005
        },

It occured a few times on the same day. I also noticed there is a queue, is that normal, or does it indicate a problem? Queue found for resource communications/calls/40005180-3432-4177-ad93-a6e9b360f13d, current queue size 7 with id communications/calls/40005180-3432-4177-ad93-a6e9b360f13d

What can we do to avoid the error?

[vidilab]

We continue to have this problem (Client Media Error). What is causing this?

Call IDs:

2d003480-7fee-4cd7-b3f8-c2a24c7f5d21 (2024-11-12T12:13:29.7064339Z)
05003380-dd8d-4e66-9b11-e1bb8791f5b5 (2024-11-11T13:58:05.9925044Z)

[yk-recall]

Hey vidilab, if you're experiencing issues with your policy recording bot being removed from calls prematurely due to 'Client Media Error' (DiagCode: 410#301005), you might want to check out the Recall.ai API.

It’s a simple 3rd party API that lets you use meeting bots to get raw audio/video/metadata from meetings without you needing to spend months to build, scale, and maintain these bots.

Here are the API docs:

https://docs.recall.ai

[ssulzer]

Hi @vidilab I can see the mid-call drop and call setup failures with your bot. Is it running in Azure?

[vidilab]

Hi @vidilab I can see the mid-call drop and call setup failures with your bot. Is it running in Azure?

It's running self-hosted on a Windows machine, not in Azure

[vidilab]

It occured another 4 times today, call IDs:

01005580-b536-4f0e-ae4a-fd030a59dc59
37005380-dda4-4e3d-8475-5f71e64b48fd
34005380-df93-463d-82b6-4e11b140094b
1b005180-911c-419c-b888-e57925d6453b

Anything we can do to solve it?