One of the most powerful tools in a support professional’s arsenal is the tried-tested-and-true method of restarting a computer to resolve strange issues. I can’t tell you how many times this fixed the oddest issues over the years. Why does it work? You might as well ask where socks go once placed in the clothes dryer.
I’m excited/sad to report that the same method works in Microsoft Teams to resolve strange issues that defy explanation. I’m not talking about client-side issues. I’m talking about issues at the Office 365 end of things. How does that work when there are no administrator-accessible servers to restart? You simply toggle the relevant setting off and back on again.
We use Direct Routing for our PSTN services, and for the most part it works great. In the past few weeks, I’ve had some of our users experience strange issues with telephony in Teams.
- A few users were unable to receive any PSTN calls. Troubleshooting at the SBC would show 487 Request Terminated – Phone number not found.
- Another user’s outbound PSTN calls were showing as Anonymous/Private. There weren’t any caller ID policies being applied that would account for the behaviour.
Set-CsUser -Identity UserID@contoso.com -EnterpriseVoiceEnabled:$FALSE
Set-CsUser -Identity UserID@contoso.com -EnterpriseVoiceEnabled:$TRUE