Forum Discussion
Solved
Caller ID not working on desktop application
Multiple teams within our organization require the ability to block their name and telephone number on a per call basis. I have setup a Caller ID Policy with the following settings: Block incoming...
- Thanks for your reply. Yes, I agree with you that the user should be able to control the Call Blocking and there is no mention that it can only work from specific device. I have escalated the ticket once again and requested the ticket be routed to the engineering team that is responsible for the programming of this feature and functionality. Fingers crossed I get response from the appropriate team.
Thanks for your reply. Yes, I agree with you that the user should be able to control the Call Blocking and there is no mention that it can only work from specific device. I have escalated the ticket once again and requested the ticket be routed to the engineering team that is responsible for the programming of this feature and functionality. Fingers crossed I get response from the appropriate team.
Hi, same issue here with the Teams desktop client. I need to test specific PSTN calls as Anonymous but It's impossible to check this box. And I was able to do it months ago... I hope that you receive a positive feedback.
- The ticket is now being reviewed by a Microsoft escalation engineer who will review the case notes and will then open a Design Change Request if required. I will post their reply once they provide their response to this issue.
- Microsoft finally agreed that this issue is a bug. Please see their response below.
"I would like to inform you that I have revised the complete case summary and have also collected all the information shared by you. I also got some similar incidents reported by our different customer’s and it seems to be a bug. Please allow me to further investigate on this so that we can proceed further accordingly! By the time appreciate your patience and cooperation. Have a great weekend! Thank you for choosing Microsoft Partners Network."- Fix will hopefully deployed in 6 to 8 weeks.
"Greetings!
I also tried re-producing this issue in my test tenant and experience same behavior. I would like to inform that this is a known bug in Microsoft environment which is experienced and re-ported by multiple Teams users and Product Group team is already aware of this issue. Also, they are already working to get this fixed. I tried reaching back to Product Group team requesting an ETA on fix, so they confirmed that FIX is already on its way to deploy to all the Microsoft tenant, and it would be completed within 6-8 weeks.
Rest be assured I have also updated a request on your behalf and once this will be deployed you will be notified by Microsoft. Please let us know if we can proceed with the archival of this service request as of now?
Looking forward for your response!".