microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

[BUG] Call Notification is showing up when teams is opened in browser

Open
#316 0 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

Call notifications are missing when initiating a call with cloud communications api

I have a bot configured with the required permissions to make a call to users using cloud communications api. I have initiated a call using postman. We have two users whom we want to add into the call. one of them is using Teams CLIENT and other one is logged into teams in a browser.

When we initiate a call (using serviceHostedMedia), users who logged into teams client is getting notifications, but for users who logged into teams in the browser are not getting any notifications.

Environment:

  1. Browser [chrome]

  2. Context [Microsoft Teams, Web]

  3. Version [v1.0 Cloud Communications API]

Code Snippet

{
    "@odata.type": "#microsoft.graph.call",
    "direction": "outgoing",
    "subject": "Create a group call with service hosted media",
    "callbackUri": "https://myserver.com/api/snc/microsoft_graph_api/evet",
    "source": {
        "@odata.type": "#microsoft.graph.participantInfo",
        "identity": {
            "@odata.type": "#microsoft.graph.identitySet",
            "application": {
                "@odata.type": "#microsoft.graph.identity",
                "displayName": "Comm Call Bot",
                "id": "37a1f7fb-7476-46de-accb-36516f762fd1"
            }
        }
    },
    "targets": [
        {
            "@odata.type": "#microsoft.graph.invitationParticipantInfo",
            "identity": {
                "@odata.type": "#microsoft.graph.identitySet",
                "user": {
                    "@odata.type": "#microsoft.graph.identity",
                    "displayName": "XXXXXXXXXXXXXXX",
                    "id": "a8ae286f-6c1c-470e-b453-bb3a5aa87018"
                }
            }
        },
        {
            "@odata.type": "#microsoft.graph.invitationParticipantInfo",
            "identity": {
                "@odata.type": "#microsoft.graph.identitySet",
                "user": {
                    "@odata.type": "#microsoft.graph.identity",
                    "displayName": "XXXXXXXXXXXXXXX",
                    "id": "43baba33-9071-44ce-b3ea-c18eb05ca038"
                }
            }
        }
    ],
    "requestedModalities": [
        "audio",
        "video"
    ],
    "mediaConfig": {
        "@odata.type": "#microsoft.graph.serviceHostedMediaConfig",
        "removeFromDefaultAudioGroup": "false"
    },
    "tenantId": "a46df9b7-2c9b-49d5-8c9f-d1b3de4ba59f"
}

Expected behaviour
All users should get the call notifications even in the browser

Graph SDK:

  • v1.0, beta

Call ID
4d1f0000-0820-4079-8d9e-126d40117453
dd1f0100-2220-438b-a5a4-07a01a47397d

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 by reproducing the call from Postman with the Cloud Communications API and serviceHostedMediaConfig, comparing Teams client and Teams in Chrome. The expected result is that every targeted user receives a call notification, including the browser user; no repository file or test entry point is identified in the issue.

Written by the indexing model from the issue text.

Assessment

Domain
api, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.