Open jsweiler opened 4 years ago
Just a note that it seems if I switch to using v1 (non beta) of the graph sdk that I don't get the issue described above. Were there some things that were fixed in the v1 version?
@ananmishr @ksikorsk @ssulzer Could any of you please comment on this issue?
@zhengni-msft @satyakonmsft Can you help look.
@jsweiler in the description, you mentioned answering call failed for the first time, so it worked for the second time? The logs you provided are in the reversed order. Can you try beta again and provide the full logs in order?
I did try it again in. The first time it failed to answer and then the second time it did successfully answer. I copied the logs from the /logs endpoint of the sample remote media application, so the newest is at the top. logs.zip
@jsweiler, the first log is "deleted. callee could not be reached" this means the bot didn't respond within 5 seconds or didn't answer within 15 seconds. If answer failed for the first time only, please check the network connection.
Ok, the confusing thing is if I take this app (the sample app from this repo) and use the v1 graph sdk the first call in will work just fine. There are no other code changes just using differenct graph nuget packages. Is there something in the beta graph sdk that would take longer to answer?
@jsweiler no, there is no extra check for beta graph sdk. Is it 100% repro?
@paywuAtMicrosoft In my testing is consistently always works the first time with the v1 sdk and consistently doesn't work when I use the beta sdk.
@jsweiler I was trying to reproduce the issue you describe by using the Incident sample bot with reference to Beta Nuget. Seems like I didn't hit that issue. Did you use the same sample code as we provided?
Yes, I simply published the IncidentBot project to an Azure app service (An S1 app service). Also the issue only happened when published to azure not when running locally.
I got same issue. how did you sort it out ?
Im using v1 and always hit this issue when restart service. Even if A calls B and B decline. A try call again then it will go to voice mail.
Any solution to this yet?
Any solution? I can reproduce it consistently using version 1.2.0.850
Describe the issue I have taken the remote media sample application and published it to an Azure App Service. The issue I have is on the first call to my resource account from a Teams client the call fails in Teams and I get a few errors from the logs which I have below.
Expected behavior I would expect the
Call.Answer()
to succeed.Graph SDK (please complete the following information):
Call ID 521f0b00-431f-49e4-972a-d4da044def36, 2020-03-11T18:41:32.7101527Z
Logs
Additional context If I call again any number of times it will then work until I restart the web app in Azure. Then it will have the same failure the first time.