Forum Discussion
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 callee and callerID are masked on the last 3 digits. example +41768111***
I also noticed the same behaviour looking at the data and export the usage PSTN reports
https://admin.teams.microsoft.com/analytics/reports
This as made a chaos on some of my customers that rely on those records for example to charge back contractual service hours dependent on the amount of time an individual called. Now there is not enough data to track back!
- Was this a planned change?
I could not find any announcement on MS usual channels - Is there a setting on the Tenant to make them available again?
I check the Report Settings and it's still active:https://admin.microsoft.com/#/Settings/Services/:/Settings/L1/Reports
I open incidents at MS support but as you know is slow as ....
- 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 🙂
13 Replies
Hi Luis
Have you found any solution for this problem? I'm struggling with the same problem here in Switzerland, that we can't assign calls anymore.
- What do you mean you "cannot assign calls anymore"?
- Until now, we have always matched the incoming and outgoing calls (call number and call duration) with the service recording for our support services.
Why not to use a 3rd party solution like MoYoBi?
MoYoBi is able to show the complete dialled number.
More info on MoYoBi web site.
I hope it will help you.
Michel
- 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?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.
Luis-Ramos Did the level of permissions assigned to your account change?
I think the last three digit obfuscation only applies to Communication Support specialist and engineer.
Use Call Analytics to troubleshoot poor call quality - Microsoft Teams | Microsoft Docs
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
