Push notifications for incoming Teams calls

Jeroen H 40

Hi,

I'm trying to create an app that can catch incoming Teams call events.
I'm using this SDK documentation to achieve it. I mentions the possibility for push notifications (even specifially mentioning for incoming calls) that work when the app is running in the background using Azure Event Grid or Event Hub.

Next, I used the Event Grid and this quickstart to create an Incoming Call event for the Azure Communication Service that the SDK uses to get its Teams User Access Tokens.

My problem is that I can't get this event to trigger.
Calling a user that has an initialized callingAgent from the SDK does not trigger it.
What do I need to change for this to work?

Vikram Boorla (Tata Consultancy Services Limi) 240 Reputation points Microsoft Vendor

2024-03-21T04:12:06.5566667+00:00

Hello Jeroen H
Could you please share the repro steps and manifest to test it from our end ?
Jeroen H 40 Reputation points

2024-03-21T08:45:14.37+00:00

I'll have a look at it and return to you with some steps.
Jeroen H 40 Reputation points

2024-03-21T11:21:26.63+00:00
Dear @Vikram Boorla (Tata Consultancy Services Limi) ,

For reproduction steps:

Creating a working calling client:

In cmd, create a react app with

npx create-react-app app-name-here

In App.js, from this tutorial, follow the 'Install the SDK', 'Initialize required objects' and 'Receive a Teams incoming call' code segments.

You'll need to acquire a Teams User Access Token, you can follow this tutorial for that.

This is where the Azure Communication Service comes into question.
If all went well, incomingCallHandler should be called whenever a user account associated with a User Access Token and an initialized TeamsCallAgent receives a call.

Creating the ACS event

This link describes how to add an event to your ACS service. For the event, I chose 'Microsoft.Communication.IncomingCall'. For the event endpoint, I chose a webhook on the same server that provides the User Access Tokens.

The webhook cannot be a localhost.

An authentication message is sent to the webhook and must be appropriately handled before it is accepted. Look at 'Validation details' here to see how.

Now, I expect this event to be fired to my webhook when a user with an initialized TeamsCallAgent receives a call, but it doesn't trigger.

I'm afraid I'm not sure what kind of manifest you are asking for. The manifest.json present in my project files describe little more than icon descriptions and background hexcodes, so I doubt they'd be of much use.
SnehaAgrawal-MSFT 18,361 Reputation points

2024-03-26T07:39:31.1466667+00:00

@Jeroen H Thanks for asking question! You can use Azure Communication Services and Graph API to integrate communication as Microsoft 365 users into your products.

Suggest you to refer this document for detailed steps- Communication as a Microsoft 365 user
Jeroen H 40 Reputation points

2024-03-26T09:28:35.3966667+00:00
Thank you @SnehaAgrawal-MSFT for the reply.
I have actually already tried both of your suggestions before, but each come with their own faults for me:

The ACS approach works for catching incoming calls, but only when the app is in the foreground.

MS Graph is unable to catch incoming calls in real time, it only gives the possibility to request a call record after the call is already over.

As such, I was hoping that this event grid approach, that was specifically mentioned for this usecase, would work.
Jeroen H 40 Reputation points

2024-03-28T08:50:52.0533333+00:00

@SnehaAgrawal-MSFT Thank you for your reply!
I am currently attempting other approaches for receiving call events, but for anyone looking for solutions themselves, I'd like to make two small notes on your comment:

For approach 1, this approach seems only fit for mobile devices.
I think I have been unclear about my project; I am indeed making an app, but I meant an app for inside of the Teams client. This means that events must also be able to be received on pc as well. Apologies for the confusion.

Approach 2 I already tried out with the link I mentioned in the original comment. The instructions to register Microsoft.EventGrid is the only practical difference that I can see between approach 2 and my link. I did register it when trying out event grid, set up a webhook and still didn't receive incoming call events. As such, in the context of incoming Teams call events I have my doubts with this approach.
SnehaAgrawal-MSFT 18,361 Reputation points

2024-03-28T12:36:05.19+00:00

@Jeroen H Reached you privately, please respond.

1 answer

SnehaAgrawal-MSFT 18,361 Reputation points

2024-03-28T07:24:57.49+00:00
@Jeroen H There are two separate things that you are mentioning here.

Getting notifications to work. This has nothing to do with eventgrid. setting up event grid will not trigger "IncomingCallHandler". https://learn.microsoft.com/en-us/azure/communication-services/concepts/notifications#deliver-push-notifications-via-azure-notification-hubs Follow the steps under Deliver push notifications via Azure Notification Hubs from the above link to get push notifications working.

Now events was mentioned above. this will not result in getting your "incomingCallHandler" invoked. But you can get all the incoming call events to a webhook on your service. You can follow - Quickstart - Subscribe to Azure Communication Services Events - An Azure Communication Services quickstart | Microsoft Learn

You need a service which exposes a webhook publicly and you can should configure it to eventgrid.

Validate Azure Communication Services events - An Azure Communication Services how-to document | Microsoft Learn

If you properly handle the validation event in the service, the event subscription should succeed on the portal.

and 2) are orthogonal things. with events going to event grid to webhook to customer's service, they can potentially loop it back into their app if they have built their own push notification system. if not, please strictly follow 1) to getting push notifications working for the app. you can use 2) for auditing, tracking incoming calls and also if you want to answer the calls from a service/server app using our server sdk.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment