Forum Discussion
WJ_Analyst
Jul 08, 2021Brass Contributor
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...
- Jul 12, 2021Thanks 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.
PeterRising
Jul 10, 2021MVP
Well, Microsoft documentation suggests the user should be able to control this - https://docs.microsoft.com/en-us/microsoftteams/how-can-caller-id-be-used-in-your-organization#end-user-control-of-outbound-caller-id - and there is no specific reference to it only working on the mobile app as far as I can see. I'd suggest escalating your ticket once more and highlighting this.
WJ_Analyst
Jul 12, 2021Brass Contributor
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.
- fmelJul 15, 2021Copper Contributor
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.
- WJ_AnalystJul 15, 2021Brass ContributorThe 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.
- WJ_AnalystJul 19, 2021Brass ContributorMicrosoft 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."