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.
Microsoft@MaskedCucumber - Thanks for bringing this issue to our attention.
Ensuring that your Microsoft Teams compliance recording bot has minimal call establishment delays involves a few steps to optimize performance and understand the underlying infrastructure.
- Region Selection: Consider selecting "West Europe" if most of your US-based users are closer to Europe than to India. While "Global" may seem like a balanced choice, it can introduce inconsistencies due to varied data center locations.
- Optimizing Bot Configuration:
- Ensure the bot services are running efficiently.
- Utilize Azure's monitoring tools to identify performance bottlenecks.
3. Monitoring and Diagnostics:
- Use Azure Monitor and Application Insights to track the performance of your bot.
- Identify if specific regions are causing longer delays and see if adjustments can be made.
4. Azure Traffic Manager:
- Implement Azure Traffic Manager to route incoming service requests to the closest data center dynamically.
- This can help minimize latency by directing traffic based on geographic proximity.
References:
Azure Traffic Manager | Microsoft Learn
Azure Monitor overview - Azure Monitor | Microsoft Learn
Please let us know if you have any further query here.
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 ?
- Nivedipa-MSFT
@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,