Forum Discussion
Compliance recording bot call establishment delay
@MaskedCucumber - Based on the issues you've described, it does seem like the problem is specific to the customer's tenant environment, especially since the bot works fine in other tenants.
- Compare Teams policies, compliance recording settings, and network configurations between the working and non-working tenants.
- Check for conditional access policies, network security groups, or firewall rules that might affect Graph API or media traffic.
Hello, I come back to you after a meeting with the customer.
It seems I didn't understand very well the issue they were facing.
They have indeed many different issues
First issue
When a recorded user calls a non-recorded user, the call fails to establish in a user point of view.
The bot receives established notification though.
Second issue
When a recorded user calls another recorded user, the call establishes.
But the bot receives a single empty roster notification, without any participant :
2025-05-13 14:00:13.0506|31|INFO|IQHttp.ProcessRequest 133|HTTP;REQUEST;131C;[52.112.238.42] => [10.0.0.4:9543] [POST] /notification =>
{
"@odata.type": "#microsoft.graph.commsNotifications",
"value": [
{
"@odata.type": "#microsoft.graph.commsNotification",
"changeType": "updated",
"resource": "/app/calls/05003b80-2299-44e6-adcd-e3beba193cb3/participants",
"resourceUrl": "/communications/calls/05003b80-2299-44e6-adcd-e3beba193cb3/participants",
"resourceData": []
}
]
}
Third issue
When participating in a meeting, there is no audio until the bot kicks in, and the roster is received after a long delay (15-20 seconds)
This bot is used by other tenants without any issue, so I am quite convinced this is an issue with the tenant itself, but I don't know what could trigger this kind of behavior.
I've already double checked compliance recording bot configuration on customer's tenant and everything sounds correct.
Any lead on this ?
Microsoft@MaskedCucumber - Based on the issues you've described, it does seem like the problem is specific to the customer's tenant environment, especially since the bot works fine in other tenants.
- Compare Teams policies, compliance recording settings, and network configurations between the working and non-working tenants.
- Check for conditional access policies, network security groups, or firewall rules that might affect Graph API or media traffic.
- Nivedipa-MSFT
@MaskedCucumber - Could you please confirm if the above solution helped you in any way or are you still looking for more information?
Hello Nivedipa-MSFT​ ,
My bad, I forgot a global teams compliance recording policy on the test tenant.
I will conduct more tests with automatic transcription, but this is unlikely the cause of the issue here.Regards,
Hello Nivedipa-MSFT​ ,
It might be related to calling/meeting policies.
Customer is using automatic transcription, so I've conducted tests by changing transcript options in my test tenant and in teams client.
Since I've updated the options, and whatever their values are, non-recorded users wait 15 seconds to enter a meeting they have initiated.
As soon as they are recorded again, they wait only 6 seconds to enter.This could explain why calls are dropped on customer's site, a timeout might occurred with non-recorded users.
Users are located in EU, bot is hosted in US.
If I use my production tenant, which has not been tampered by changing transcript options, non-recorded users wait 3 seconds to enter, and 6 seconds for recorded users.I haven't found a solution yet to fix my test tenant.
Regards,