microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

EchoBot do not join the call

Open
#786 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
253
Forks
275
Avg merge
1d 5h
Merged PRs (30d)
1

Description

Describe the issue
I setup Azure cloud and everything works fine
I make a POST request to make bot join a meeting.

curl -X POST --insecure -H "Content-Type: application/json" -d '{"joinURL": "https://teams.microsoft.com/l/meetup-join/19:meeting_MWNhYmVhN2ItMWE4Yi00MGQ2LTk5ZGYtMzQzYzk2MzEzY2Zm@thread.v2/0?context=%7B%22Tid%22:%22cbaa6e74-dfa8-4838-b0e2-240cdfffc423%22,%22Oid%22:%22725b4a36-e7b2-4d1f-ab00-89dd3fb20230%22%7D"}' https://ailabbot.com/calls

Code Snippet

Expected behavior
EchoBot join the meeting

Graph SDK (please complete the following information):

  • Version same as cloud deploy

Call ID
Provide the list call ids that encountered this issue. Include the time in UTC/GMT when these call have occurred.

Logs
The log on service:

info: EchoBot.Controllers.HealthController[0]
      HEALTH CALL
info: Microsoft.AspNetCore.Mvc.StatusCodeResult[1]
      Executing StatusCodeResult, setting HTTP status code 200
info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
      Executed action EchoBot.Controllers.HealthController.Get (EchoBot) in 0.104ms
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
      Executed endpoint 'EchoBot.Controllers.HealthController.Get (EchoBot)'
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 GET https://localhost:9442/health - - - 200 0 - 0.5116ms
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 POST https://ailabbot.com/calls application/json 255
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
      Executing endpoint 'EchoBot.Controllers.CallsController.JoinCallAsync (EchoBot)'
info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[3]
      Route matched with {action = "JoinCall", controller = "Calls"}. Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.IActionResult] JoinCallAsync(EchoBot.Models.JoinCallBody) on controller EchoBot.Controllers.CallsController (EchoBot).
info: EchoBot.Controllers.CallsController[0]
      JOIN CALL
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 GET https://localhost:9442/health - -
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
      Executing endpoint 'EchoBot.Controllers.HealthController.Get (EchoBot)'
info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[3]
      Route matched with {action = "Get", controller = "Health"}. Executing controller action with signature Microsoft.AspNetCore.Mvc.IActionResult Get() on controller EchoBot.Controllers.HealthController (EchoBot).
info: EchoBot.Controllers.HealthController[0]
      HEALTH CALL
info: Microsoft.AspNetCore.Mvc.StatusCodeResult[1]
      Executing StatusCodeResult, setting HTTP status code 200
info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
      Executed action EchoBot.Controllers.HealthController.Get (EchoBot) in 0.1022ms
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
      Executed endpoint 'EchoBot.Controllers.HealthController.Get (EchoBot)'
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished HTTP/1.1 GET https://localhost:9442/health - - - 200 0 - 0.6503ms

Additional context
Add any other context about the problem here.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at EchoBot.Controllers.CallsController.JoinCallAsync, using the POST request and service logs shown in the issue to trace what happens after the JOIN CALL message. Confirm the failure with a current call ID and UTC timestamp, then document or fix the point where the meeting join stops and verify that the bot joins successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp
Domain
api, backend, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.