Forum Discussion
Solved
Call records and usage reports are now obfuscating the last 3 digits of the PSTN number
Hi guys, Since 21.04.2022 12:55 CET that on my customer tenants the Call Records that I extract using GraphAPI (https://graph.microsoft.com/v1.0/communications/callRecords/getPstnCalls The PSTN ca...
- 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 🙂
Hi Luis-Ramos,
we have the same problem with at least one customer. Do you still have the problem? And if not, have you found a solution?
we have the same problem with at least one customer. Do you still have the problem? And if not, have you found a solution?
Hi Lucas_Peschek
Yes, still on the same status.
And after two weeks the latest MS support incident update is "what is your customer tenant name?"Hi, Luis-Ramos
I have found out in the meantime that it is a data protection issue:
https://docs.microsoft.com/en-us/microsoftteams/teams-analytics-and-reports/pstn-usage-report
And thanks for the reference to your blog, maybe the workaround via the SBC is something for our customer.
- 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 🙂