Forum Discussion
Teams Call History Not Updating After Recent Teams Update
Hi All,
We have had a few calls from our users about the built in teams call history not accurately tacking incoming and outgoing calls correctly, You will login in the morning and your first 3-4 calls will be tracked normally but then when you look a few hours later you have "apparently" not made or gotten any calls. I have found a work around by just closing teams fully by quitting it and reopening it and that seems to fix it for a little while but the next day it does the same. It seems to be effecting most of the business. It only seems to of started happening this frequently after the new UI update a few weeks back
Anyone else getting similar behaviour?
Thanks,
Brad
17 Replies
- vonalterCopper Contributor
My call history was fine for a week, but now no calls register??????? Have tried lots of fixes, but nothing works.
- stesz1115Copper ContributorThings seem better on my end!
- HDJ-BXITBrass ContributorSame here. Waiting on Microsoft to work its magic to fix this. Thanks guys!
- schlussel2010Copper ContributorMy results today seem to be better than yesterday! All incoming and outgoing calls are correctly identified in my history. One missed call (for which there was a voicemail message) does not show up but is listed in the Teams activity feed.
- stesz1115Copper ContributorI've just been using the web app to keep up with my call history, which doesn't seem to have fallen victim to whatever this new update was just yet.
- gpoon80Copper ContributorSame here. Nothing more to add.
- schlussel2010Copper ContributorI have the same issue. What is odd is that my Teams app at home with the same UI and version number has the issue while my Teams app in my office works fine. I also don't understand how there was a UI update without a change in version number.
- Luis-RamosBrass Contributor
schlussel2010(for your last question)
There are actually two types of 'updates' done by MS:
- one is the client to support new features- the other one is the 'enable features' policies that MS releases per tenant/region (whatever the criteria they use)
It's a very common procedure that I noticed on Teams.
The best way is to 'sniff' the JSON policy received by the client to find out new features and if they are enabled for you 😉You can see an example here, where the client supported Teams live events, but in my country it was disable by an MS specific policy
https://itbasedtelco.wordpress.com/2020/11/21/how-to-create-teams-live-events-in-switzerland-and-other-regions/- schlussel2010Copper ContributorThanks, A good explanation regarding build numbers but unfortunately, the problem remains--at least as of last night.
- SusanZ965Copper ContributorSame issue here as well, thanks for spelling it out well.
- stesz1115Copper ContributorWe are also having this problem. I don't see it as a reported issue from Microsoft at all, I hope they can address it soon. It's very inconvenient.
- Donald24ALCopper ContributorWe are experiencing the same problem.
- Hoggie112Copper ContributorThis has also been reported to us, also what is interesting the view is different from other users that are on the same version