Forum Discussion

BroGale's avatar
BroGale
Copper Contributor
Jan 17, 2021
Solved

Proximity join doesn't work from Teams Desktop app

Hi all, We have been testing / piloting the Poly Collaboration Bars X30 & 50 for months and now rolled out the devices in over 80 (!) meeting rooms over the last 2 weeks. Since last week, all of a...
community
microsoft teams
  • Andreas-N's avatar
    Andreas-N
    Feb 15, 2021

    Pavel Yurevich Just received the latest teams client update today, problem solved! Thanks alot Pavel!
    Desktop App Update: Microsoft Teams Version 1.4.00.2879 (64-bit). It was last updated on 2/15/21.

MedpaceTeams's avatar
MedpaceTeams
Copper Contributor
Apr 15, 2021
Greg,

Any updates on when this might be fixed ?
Wayno's avatar
Wayno
Brass Contributor
Apr 20, 2021
Our company current has a Premier Support ticket with Microsoft on this. They are currently advising that the updated Teams desktop app containing the fix should be entering Ring 4 in the next week or so.
  • MedpaceTeams's avatar
    MedpaceTeams
    Copper Contributor
    Apr 29, 2021
    We have a support ticket open as well, I was told we may be getting close to a fix being deployed. May 4 seems to be the date they are projecting.
    • Eug's avatar
      Eug
      Brass Contributor
      May 04, 2021

      It's May 4th and I just checked and most of my rooms are working...which is so strange if this is a Desktop App on Windows 10 issue.  I mean, if it works for one Crestron Flex it should work for all, no?  

      At least two of my rooms are not working and but the other ones are.

       

      Teams app on W10 says a room nearby when I go to join and if I click the Room Audio it picks the rooms I'm in - except for these two rooms where it doesn't see them.  Instead it sees the Conference Room next door - on the other side of the wall.

      Also, I am now able to search in the list for a room when joining which is nice and was missing as well.

      I am on Teams V 1.4.00.8872

      • ChipRoebuck's avatar
        ChipRoebuck
        Copper Contributor
        May 20, 2021
        I have been working with MSFT on this issue fairly extensively. Our tenant got the fix pushed to our ring about two weeks back. For us we found there is a different behavior in receiver sensitivity depending on the model of MTR device installed. We have the Crestron UC-MX150-T and the UC-CX100-T. The MX-150-T works better and I can usually get it to work within 12 feet line of sight (UC Engine compute mounted behind display). However, the UC-CX100-T is a different story and I need to be within 3 feet of the UC engine. The root cause is the Intel MX-150-T uses the NUC Skull Canyon compute module and the CX100-T uses an ASUS compute module. There is a significant difference in the RF propagation output between these models. I've made contact with Crestron and am asking for a fix. Maybe the solution is an USB external bluetooth antenna that can be extended somewhere central to the room (Table?). My contact at MSFT share this with me: "With regards to the current experience, we have 2 RSSI power level cutoffs. One for detecting Nearby Rooms and the other detecting High Confidence nearby rooms. If the detected signal is strong enough that meets the High Confidence threshold, then the room will be automatically populated in the Room Audio banner. If the receiver only meets the Nearby threshold, then the Room Audio banner will be highlighted, but not pre-populated. In your scenario, with the UX-CX100-T, the receiver is not meeting the High Confidence threshold at 3ft and only meets the Nearby room threshold. This is expected behavior, but the beacon strength from the ASUS compute module needs to be investigated and improved." Does anyone out there have a large deployment of the Crestron UC-CX100-T that can confirm my findings? Or for that matter any other MTR models experiencing this issue?

Resources