Forum Discussion
Call records and usage reports are now obfuscating the last 3 digits of the PSTN number
- That section seems to have been introduced 20 days ago and pulled 2 days ago
https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/search?q=obfuscation&type=commits
Besides blowing up business cases, it's still a total mess: (1) I am in Switzerland and it's masking 3 digits and not 4. (2) if you make a call forward or get calls to Call Queues, it will mask the callee (your own number) and keep the callerID (the external number that the call is forward 🙂
No, I thought of something like that but I have the Teams Administrator role . I don't even have the other roles and I can do any Teams admin tasks.
Actually I noticed the 'issue' started with a powershell that extracts the record using the GraphAPI https://graph.microsoft.com/v1.0/communications/callRecords/getPstnCalls
And that one you need to register an application with permissions to get the CDR data.
I have this now on at least 3 customers.
Opened an Support incident at MS, but they are still trying to understand my problem after 6 days....
Since 26.04.2022 15:51.07 CET that the records start appearing without mask when you export them from TAC, but are still masked if you extract using the https://graph.microsoft.com/v1.0/communications/callRecords/getPstnCalls
Again, no explanations published or provided by MS support
And now we don't get and call history records newer than 28.04.2022 9.21 CET.
I've never been so much frustrated working with MS