SOLVED

View Call History

%3CLINGO-SUB%20id%3D%22lingo-sub-299442%22%20slang%3D%22en-US%22%3EView%20Call%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-299442%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20seen%20that%20%22Call%20history%22%20button%20only%20appears%20when%20you%20have%26nbsp%3B%22Entreprise%20Voice%20license%22%2C%20but%20until%20some%20days%20ago%20it%20was%20visible%2C%20and%20it%20was%20very%20useful%20for%20me%20to%20see%20the%20Teams%20voice%20conversations%20I've%20done.%20Now%20the%20button%20is%20missed%2C%20and%20I%20have%20no%20way%20to%20see%20nor%20the%20duration%20neither%20the%20calls%20done%20with%20my%20contacts.%20Is%20there%20any%20other%20way%20to%20see%20the%20voice%20conversations%20and%20the%20duration%20of%20them%3F%20It%20must%20be%20independent%20of%20the%20kind%20of%20license%2C%20if%20you%20can%20do%20a%20call%2C%20you%20would%20see%20it%20on%20history.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-299442%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHistory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHow-to%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUser%20Interface%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-299778%22%20slang%3D%22en-US%22%3ERe%3A%20View%20Call%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-299778%22%20slang%3D%22en-US%22%3EI've%20created%20the%20issue%20on%20Office365%20admin%20center.%20Perhaps%20the%20reason%20is%20the%20response%20of%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%20below.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-299735%22%20slang%3D%22en-US%22%3ERe%3A%20View%20Call%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-299735%22%20slang%3D%22en-US%22%3EThey%E2%80%99ve%20been%20deploying%20this%20feature%20and%20then%20pulling%20it.%20Your%20going%20to%20just%20have%20to%20give%20it%20time%20till%20they%20fully%20complete%20the%20roll%20out%20and%20it%E2%80%99ll%20show%20back%20up.%20I%20think%20they%20are%20just%20having%20problems%20with%20the%20roll%20out%20and%20it%20comes%20and%20goes%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-299683%22%20slang%3D%22en-US%22%3ERe%3A%20View%20Call%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-299683%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20could%20do%20it%20from%20the%20office365%20admin%20center.%20Or%20click%20on%20the%20feedback%20button%20in%20microsoft%20teams%20on%20the%20left%20side.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-299676%22%20slang%3D%22en-US%22%3ERe%3A%20View%20Call%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-299676%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20checked%20that%20the%20app%20is%20succesfuly%20updated.%20So%2C%20how%20can%20I%20report%20a%20service%20request%3F%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-299648%22%20slang%3D%22en-US%22%3ERe%3A%20View%20Call%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-299648%22%20slang%3D%22en-US%22%3E%3CP%3Eif%20so%20i%20would%20suggest%20to%20check%20if%20there%20is%20a%20update%20for%20your%20desktop%20version.%20If%20that%20is%20not%20the%20solution%20please%20report%20a%20service%20request.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-299517%22%20slang%3D%22en-US%22%3ERe%3A%20View%20Call%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-299517%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20working%20on%20Windows%2010%2C%20and%20I've%20tried%20on%20other%20computers%20(w10%20too)%20and%20company%20users%2C%20on%20the%20web%20version%20too.%20The%20button%20is%20not%20displayed%20anywhere.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20recently%20installed%20the%20mobile%20version%20to%20try%20and%20there%20the%20button%20is%20shown.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-299475%22%20slang%3D%22en-US%22%3ERe%3A%20View%20Call%20History%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-299475%22%20slang%3D%22en-US%22%3E%3CP%3Ecan%20you%20explain%20some%20more%20is%20it%20browser%20is%20it%20on%20the%20mobile%20is%20it%20on%20windows%20on%20mac%3F%20etc%3F%3C%2FP%3E%0A%3CP%3EDid%20you%20try%20the%20different%20platforms%20to%20test%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

I've seen that "Call history" button only appears when you have "Entreprise Voice license", but until some days ago it was visible, and it was very useful for me to see the Teams voice conversations I've done. Now the button is missed, and I have no way to see nor the duration neither the calls done with my contacts. Is there any other way to see the voice conversations and the duration of them? It must be independent of the kind of license, if you can do a call, you would see it on history.

7 Replies
Highlighted

can you explain some more is it browser is it on the mobile is it on windows on mac? etc?

Did you try the different platforms to test?

Highlighted

I'm working on Windows 10, and I've tried on other computers (w10 too) and company users, on the web version too. The button is not displayed anywhere.

 

I've recently installed the mobile version to try and there the button is shown.

Highlighted

if so i would suggest to check if there is a update for your desktop version. If that is not the solution please report a service request.

Highlighted

I've checked that the app is succesfuly updated. So, how can I report a service request? Thanks.

Highlighted

You could do it from the office365 admin center. Or click on the feedback button in microsoft teams on the left side.

Highlighted
Best Response confirmed by Marc Tomas (Occasional Contributor)
Solution
They’ve been deploying this feature and then pulling it. Your going to just have to give it time till they fully complete the roll out and it’ll show back up. I think they are just having problems with the roll out and it comes and goes
Highlighted
I've created the issue on Office365 admin center. Perhaps the reason is the response of @Chris Webb below.