microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

ParticipantsOnUpdated is not called when a participant joins a meeting

Open
#550 1 comment 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

I'm checking the sample of teams-recording-bot to work. At that time, ParticipantsOnUpdated is not called when the participant joins the meeting. In the first place, all the events in the CallHandler class have not been called. Also, there is no log of requests coming to the PlatformCallController class.

The experiment is conducted by preparing our own server. Therefore, .env :

AzureSettings__ServiceDnsName=<My server domain>
AzureSettings__CertificateThumbprint=<My server thumbprint>
AzureSettings__InstancePublicPort=8442
AzureSettings__CallSignalingPort=9441
AzureSettings__InstanceInternalPort=8442

Webhook Url for Teams channel in Azure :

https://<My server domain>:9441/api/calling

As a test, I sent a request locally to https://<My server domain>:9441/api/calling with POSTMAN, and the log showedPublish to <TopicName> subject Notification HTTP POST. I was able to confirm that the request came to the PlatformCallController class.

During the actual meeting, Publish to <TopicName> subject JoinCall is called forPOST /joinCall, and Publish to <TopicName> subject Ending Call is called forDelete /calls/<Call ID>. However, NotificationHTTPPOST is not called when a participant joins a meeting or raises his hand.

When I monitored the reception status with Wireshark, there was no log received by 9441 except forPOST /joinCall and Delete /calls/<Call ID>.That is, the Teams server is not sending events except at POST /joinCall andDelete /calls/<Call ID>.How can the Teams server send an event to the Bot when a participant attends a meeting or raises his hand?

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 in Samples/V1.0Samples/AksSamples/teams-recording-bot and trace the /joinCall flow through PlatformCallController and CallHandler. Reproduce the meeting scenario while monitoring port 9441 and the existing request logs, comparing it with the successful local POST. Done means the cause of missing participant and hand-raise notifications is identified and the expected event reaches ParticipantsOnUpdated, or the limitation is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
api, backend
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.