Encountering ServiceException Code 9999 During /joinCall API Usage in PSI Bot

[wo-yashsinghvi]

Hello Microsoft Graph Communications API Team,

I am developing an application that utilizes the Microsoft Graph Communications API, specifically the /joinCall endpoint. During implementation, I encountered the following error:

Status Code: InternalServerError
Microsoft.Graph.Communications.Core.Exceptions.ServiceException: Code: 9999
Message: Unknown internal server error.
Scenario Id: cf779b75-bb12-482d-9e47-13cb0e40dee9

Context:

• API Endpoint: /joinCall
• Scenario ID: cf779b75-bb12-482d-9e47-13cb0e40dee9
• Permissions Granted: Calls.JoinGroupCall.All (admin consented)
• Application Registration: Configured as per [Microsoft Teams bot registration guidelines](https://learn.microsoft.com/en-us/microsoftteams/platform/bots/calls-and-meetings/registering-calling-bot)
• Request Payload: Includes callbackUri, targets, requestedModalities, among other required parameters

Request:

I am seeking assistance to understand the root cause of this ServiceException with code 9999 during the /joinCall API operation. Any guidance on troubleshooting steps, potential misconfigurations, or insights into this error would be greatly appreciated.

Thank you for your support.

[wo-yashsinghvi]

@InDieTasten Can you please help me with this issue?

[wo-yashsinghvi]

@ssulzer Can you please help me with this issue?

[ssulzer]

@wo-yashsinghvi This has been referred to the Graph Communications team. Can please you share any other kind of call-id and/or timestamp associated with that Scenario-ID? Thanks.

[wo-yashsinghvi]

I just tried it out right and got the error again. Here is the error stack trace:

Status Code: InternalServerError
Microsoft.Graph.Communications.Core.Exceptions.ServiceException: Code: 9999
Message: Unknown internal server error.
Scenario Id: 4f605d5f-0117-4675-bf52-4f4767e9d74b
Inner error:
	 ---> Microsoft.Graph.Communications.Core.Exceptions.ServiceException: Code: 9999
Message: Unknown internal server error.
Inner error:
	
   at Microsoft.Graph.Communications.Client.Transport.GraphAuthClient.<ValidateResponseAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Graph.Communications.Client.Transport.GraphAuthClient.<SendHttpRequestAsync>d__4`2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Graph.Communications.Client.Transport.GraphClientWrapper.<ValidateAndWrapAsync>d__12`1.MoveNext()
   --- End of inner exception stack trace ---
   at Microsoft.Graph.Communications.Client.Transport.GraphClientWrapper.<ValidateAndWrapAsync>d__12`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Graph.Communications.Client.Transport.GraphClientWrapper.<SendAsync>d__11`2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Graph.Communications.Resources.StatefulResourceCollection`4.<GenerateEntityAsync>d__26.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Graph.Communications.Calls.StatefulCallCollection.<GenerateEntityAsync>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Graph.Communications.Resources.StatefulResourceCollection`4.<CreateStatefulResourceAsync>d__31.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Graph.Communications.Resources.StatefulResourceCollection`4.<GenerateStatefulResourceAsync>d__22.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
   at PsiBot.Services.Bot.BotService.<JoinCallAsync>d__13.MoveNext() in D:\Projects\microsoft-graph-comms-samples\Samples\PublicSamples\PsiBot\PsiBot\PsiBot.Service\Bot\BotService.cs:line 165
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
   at PsiBot.Services.Controllers.JoinCallController.<JoinCallAsync>d__4.MoveNext() in D:\Projects\microsoft-graph-comms-samples\Samples\PublicSamples\PsiBot\PsiBot\PsiBot.Service\Controllers\JoinCallController.cs:line 68

[InDieTasten]

Might be related/duplicate of #789

[wo-yashsinghvi]

This issue is likely caused by PSI Bot using deprecated libraries. You have a couple of options:

1. Use EchoBot as the base and integrate the video-related code from PSI into it.
2. Alternatively, check this comment out.