Closed Githamza closed 5 years ago
@Githamza, we are removing the requirement of the initial 204 No Content response for Graph API. Your bot already uses that. Please remove the corresponding logic and retry.
The documentation will shortly be updated to reflect this. For future issues of the graph API, please take a look here.
I trying to respond to a call in Teams but actually I'm not getting a respond from the bot.
First I get access_token from Graph API.
Then I have a route that intercept bot calls.
Here's POST function
As mentionned in documentation , Server sould first reply 204 in order to get response in Graph API protocol.
Actually I don't get a response. Bot still ringing until It gets voice message : " You can't talk to the bot just yet , we are working on it".
As mentioned in Teams API documentation, I should get callback with the ressource id and other information to be able to answer to the call.
So I use my POST function to answer. but here I don't get any 202 Accepted response as indicated in docs, instead I get more than one callback with different ressource ids, then after some seconds I get the voice message.