Forum Discussion
Seeking Guidance on Real-Time Audio and Video Analysis in a Teams Plugin
Hello @Itay_Nadir, The error you are encountering, Microsoft.Graph.Communications.Core.Exceptions.ServiceException: 'Code: 9999 Message: Unknown internal server error, typically indicates an issue with the service or configuration rather than the code itself.
-
- Verify that the app has the Calls.JoinGroupCall.All and Calls.InitiateGroupCall.All permissions granted and admin consented.
- Enable detailed logging in your application to capture more information about the error.
- Ensure that the joinParams being passed to the AddAsync method are correctly formed and contain all required information.
- Double-check the values for JoinUrl, MeetingId, and other parameters.
- Ensure that the scenarioId being used is unique for each call. Reusing scenario IDs can sometimes cause issues.
-
Hi,
Thanks for your response and guidance! We're using the exact same repository and followed the setup instructions, including this video (https://www.youtube.com/watch?v=jxPltGlZKE4).
However, when running the example as is, we encountered the following error:
Microsoft.Graph.Communications.Core.Exceptions.ServiceException: 'Code: 9999
Message: Unknown internal server error.
Scenario Id: 3fa0cf1d-5e4c-4735-baea-a97ec3f79aa8
Inner error:
'This error occurs at the following line in PsiBot\PsiBot.Service\Bot\BotService.cs:165:
var statefulCall = await this.Client.Calls().AddAsync(joinParams, scenarioId).ConfigureAwait(false);Would you happen to know what might be causing this issue? Any insights or steps to troubleshoot this further would be greatly appreciated.
Thanks again for your help!
MicrosoftHello @Itay_Nadir, The error you are encountering, Microsoft.Graph.Communications.Core.Exceptions.ServiceException: 'Code: 9999 Message: Unknown internal server error, typically indicates an issue with the service or configuration rather than the code itself.
-
- Verify that the app has the Calls.JoinGroupCall.All and Calls.InitiateGroupCall.All permissions granted and admin consented.
- Enable detailed logging in your application to capture more information about the error.
- Ensure that the joinParams being passed to the AddAsync method are correctly formed and contain all required information.
- Double-check the values for JoinUrl, MeetingId, and other parameters.
- Ensure that the scenarioId being used is unique for each call. Reusing scenario IDs can sometimes cause issues.
- Sayali-MSFT
Hello @Itay_Nadir, We would appreciate it if you could share your valuable feedback via the Microsoft Teams Developer Community Response Feedback link?
Thank you for the suggestion! Here's how I resolved the issue: I removed the "MediaSession" object and switched to using "requestedModalities". Instead of continuing with the C# project, I sent an API request directly through Postman, and it worked successfully. Appreciate your guidance!