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 🙂
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.
The incident was closed as is:
- the 3 (and then changed to 4 after I mentioned on the ticket that the documentation was mentioning 4 in CH but I was getting 3 digits obfuscated ) digits obfuscation will stay like that as a regulatory country demand. MS refused to provide any official reference.
- The change was unannounced by MS and even the support of MS doesn't know nothing about that.