04-03-2019 11:09 AM
04-03-2019 11:09 AM
I've read the previous article on this, it was of no help. We now have several users all running the latest Teams client version 1.2.00.7161, and both Teams-to-Teams and PSTN-to-Teams calls are failing to ring the desktop. Mobile clients work fine for them. They can join Teams meetings and make Outbound PSTN calls. We are using Direct Routing as well, but because this is both Teams-to-Teams and PSTN calling affected, I don't believe this to matter. Regardless, their TeamsUpgradePolicy has been set to Upgrade, as the users are in Teams Only mode, not Islands.
Seems to work for a while after rebooting the PC, but sometime in the next hour it quits. Even for setting up Meetings some times has just Teams, and other times it displays both Skype and Teams. InterpretedUserType is HybridOnlineSfBUser, and doesn't change. WhenChanged also hasn't changed in over a week.
This is maddening.
04-03-2019 11:17 AM
@Korbyn Forsman If it's working after a reboot but then stopping, it sounds to me like some kind of network issue perhaps? If you connect a client directly to the internet without corporate security controls etc. does it keep working?
04-03-2019 01:33 PM
@Korbyn Forsman the Teams meeting button in Teams will only show if the add-in is not connecting through an authenticating proxy server. Still sounds like it's related to your network infrastructure to me. Also bear in mind that the client caches it's state for quite long periods of time, hours to days.
04-08-2019 08:33 AM
@Steven Collier I beleive there was an issue actually happening with MS Teams. We also had a number of customers also report the issue or similar issues of license flapping, though nothing was posted by MS. For a number of users Uninstalling Teams and then and only after performing a Online Repair of the Office Suite, and then Reinstalling Teams did they appear to be receiving calls through the Desktop App for a longer period of time, but still have to reboot ever now and then because the incoming calls to the Desktop App just go straight to voicemail. I would think if it was a network issue, they wouldn't be able to IM me and tell me about it.
On the 3rd, an updated Version, 1.2.00.8864 came out which people, including myself, had to run the "Check for Updates" and Refresh multiple times before the client finally updated. Seems to be better, but might still be too early to tell, many users haven't made it to the latest update yet.
04-08-2019 12:30 PM
@Korbyn Forsman IM uses an entirely different set of network protocols than media. You are not seeing the same experience as other people, I look after many clients and this isn't something we see, calls work as long as the network is clearly allowing UDP traffic required. If the client has failed back into using HTTPs for call traffic then all sorts of things can happen as HTTPs is often inspected, adjusted, proxied etc.