Forum Discussion
Solved
Calls appear in chat history
Hi
A couple of my users have reported they've started seeing their recent calls appear in the chat screen. I can't figure out how to disable this and it doesn't seem to do it for everyone. Has anyone come across this before and is it possible to stop it. It's the entries which start +44 that are the issue. There's no actual chat
Thanks
- Hi All,
The latest update from our SIP vendor, they said Microsoft resolved the issue on their end. We had to get our users to log out and log back into Teams. The calls no longer appear in the chat history.
Cheers,
Ian
- My Teams updated a couple days ago and I have not signed out or back in. Appears that the chats created from calls has been resolved on my desktop!
My Teams is also back to normal this week
We have some users reporting the same issue.
I have kept an eye on this thread for a few days and waited to see if the reported MS fix comes through and sorts it for us, but our users are still reporting an issue.
Just logged it with MSHi all,
We are having the same issue.
Can anyone provide a ticket number as I would like to log one too and attach that number to mine so the agent I speak to has a clue as to what to do.
Thanks
- I logged it with Microsoft yesterday, Ticket Case #: 30660414 - however I'm not sure how much help it would be, the Microsoft Agent I'm dealing with is currently telling me it's a Computer \ User profile issue and I need to get them to use a new local account. I pointed him to this thread showing we're not the only people with this issue.
- Hi All,
The latest update from our SIP vendor, they said Microsoft resolved the issue on their end. We had to get our users to log out and log back into Teams. The calls no longer appear in the chat history.
Cheers,
IanIan Lord Just to clarify - Your SIP provider found a fix, or Microsoft devs found a fix and deployed to all? Just wondering if this is a result for everyone...
- HI Aweswalker,
Our SIP provider said it was an issue on the Microsoft end and that MS resolved it.
Sign out and sign back in seems to fix it for the end user.
- Hi Ian.
Don't suppose you were able to extract any information regarding the fix. I wonder if there's a power shell script we can run to clean the calls up.
Thanks- No I wasn't. Vendor just confirmed MS fixed the issue on their end.
I've had confirmation from MS that this is a bug, it has been fixed and will be rolled out to the general ring in the next 4-6 weeks.
- Yep, this is the information that I have just received from the original engineer who told me that it was a new 'Feature'!
Hammed (Microsoft)
Monday, April 4, 2022 3:00 PM GMT
Hello Kevin,
Thanks for the feedback.
The fix for this issue has already been rolled out and it is expected to get to affected user's end in 2 months.
Some affected users are already receiving the updates, the estimated time for all affected users is 2 months.
Best Regards- Has anyone experienced or heard if this fix will affect the mobile platform?
- Thanks JasonRUK
Lets hope it's sooner. My users are going crazy about it
I have been following along for a while, experiencing the same issues, following the same trouble shooting. There are a couple things that I have found that I haven't seen mentioned.
I have the Teams Mobile app, and it shows the same multitude of "Just Me" or number titled chats. So I am getting the same response on my phone.Also, I have noticed a change when answering phone calls. Instead of answering and going to the generic figure in the dialog box of the call, I now am often seeing my own picture and it says "Waiting for others to join the call...", even though I am actively talking with the caller. Not sure if that is related or not, but it is there.
I would like to know who supposedly asked for this "feature" for it to be something important enough for Microsoft wanted to bless us with. (Heavy sarcasm font enabled)- I have been advised by Microsoft that this is a new feature! Not sure we actually want it?! There also appears to be no way to turn this feature off. The response I received on my ticket is:
I would like to inform you that incoming call queue number showing in chat tab on Teams client is a new feature in teams client.
This new feature will allow call queue agent to chat with customers.
This is to inform you that incoming call queue number in chat tab is an expected behavior and Microsoft are working to enhance users experience in Teams client.
Best Regards
Hammed
Microsoft 365 Support EngineerKevinJParker do not want this feature. what a waste of time. Needs to be an option only that needs to switched on if required.
KevinJParker - A feature that can't be used by maybe 50% of the callers? Classic Microsoft feature.
Any other confirmation from Microsoft that this is a feature rather than a bug? Our receptionists are starting to see it since they're Direct Routing call queue agents.- I received an even more bogus response than that.
IplayanITguyonTV Interesting. What did they tell you?
I have gone back to Hammed to ask for more information about this new 'feature'? How are we supposed to use it? Why isn't it in the web version? etc
Same here.
Environment: 3rd Party VOIP via Teams.
Incoming call queue calls drops either the number or "Just me" as a new chat.
Not only affecting our staff, but clients we resell to as well.
Microsoft Support please sort this, Our phones are off the hook with complaints.
Same here, reported for the last week. I can confirm it only happens to calls via a call queue, not calls direct to the user. This is with version 1.5.00.5967 and yes, only happens on the desktop app. The generated 'chats' do not appear in the web app.
Ticket raised with MS- Microsoft Teams Version 1.5.00.5967 (64-bit). It was last updated on 10-Mar-2022
- I tried uninstalling and reinstalling. It works for a time then goes back to showing calls. Log out, log in, same thing. It only happens on the desktop app
- Same issue here with people in a call queue!!
Anybody with a response from Microsoft yet?
Will log a ticket also looks like a bug in the latest releases...
- Just chipping that I have a customer who is reporting that this started happening from yesterday. Just gathering teams client versions and screenshots and will then be logging via their 365 portal.
Recreating the resource accounts seems dangerous, we've had delays of up to 48 hours when reassigning a DDI from one resource account to another and can't afford that sort of down time for external callers.
We are using Direct Routing, not sure how relevant that is?
