Apr 28 2021 06:42 AM
Apr 28 2021 06:42 AM
I have an X50 running firmware 3.3.2-286154 paired with a TC8 running 3.3.2-210446 which I am attempting to use with Teams. I am able to log into my Teams account on the TC8 however the screen on the X50 doesn't change from the prompt to log in. Simultaneously the TC8 which is now logged in shows "Couldn't find any devices" "Make sure the device you want to pair is signed into the same Teams account"
How do I sign in the X50 given that I have no way to control it? Should signing in on the TC8 not sign in the X50 also?
Apr 28 2021 08:59 AM
May 05 2021 01:38 PM
Same problem for me too. I was able to boot, pair, and login in with the TC8 while the X50 just sat there waiting for me to log it into teams. I solved this by connecting a USB keyboard into the back of the X50 and entering the username / password. Not very practical for enterprises that are going to deploy these in large quantities.
May 06 2021 06:08 AM
May 11 2021 02:16 PM - edited May 11 2021 02:19 PM
Same here with X30 and X50s on version 3.4 ...
That bug was also present on 3.3.2 which for us, meant that either the TC8 or the Studio (Or both) got disconnected from Teams after the upgrade to 3.3.2
What changed now, the TC8 is -sometimes- classified as a "Touch Console" when you look for collab bars which wasn't present in January 2021.
Did any of you manage to make the remote device
sign in provisioning work on the Poly collab bar (Or any other bar) ?
May 13 2021 06:36 AM
There is an article describing how the TC8 interacts with Teams over on Jeff Schertz's blog. This describes how the new MTRoA interface does its magic to work like an MTRoW interface without having a direct USB connection like the MTRoW variant. It is essentially a separate device and though the hardware is Bluetooth paired, the Teams application layer does not directly pair over the LAN or Bluetooth but via the device's registration with Teams cloud services. Image below from Jeff Schertz:
Jeff mentions that an administrator will facilitate a one-time connection between devices during deployment.
Unfortunately, this does not appear to be true. It seems to be occurring with every update. I hope this isn't the permanent state of things.