Feb 13 2020 02:35 AM
Feb 13 2020 02:35 AM
I have the project to set up a "Teams" meeting room with a Polycom room equipment that will be certified Teams soon: poly studio X50.
I'm wondering how "Click to join" works when a person receives an invitation from outside the company and the room has not been invited (only the user).
Does the user have to transfer the external Teams invitation to the meeting room email? I don't really understand the Workflow that can be used to make the use of my rooms simple.
Feb 13 2020 09:29 AM
@jfrobs You have probably turned off so that external users can't e-mail to the room accounts mailbox (that is default) so the best way is that an internal user forwards the invite to an room mailbox. Note that the confirmation sent back from the room mailbox will be sent to the organiser (external) of the meeting and not to the one that forwarded the meeting.
Feb 13 2020 11:12 PMSolution
Jan 14 2021 03:33 PM
@Linus Cansby I am having the same issue with coincidentally the same hardware, PolyX50. I understand that the response "should" go back to the meeting originator but it does not seem to accept and respond to anyone outside our organization, or me as the person who forwarded the request to the room. I have asked our IT guy to confirm the setting on the room's email. He said that he spoke with Microsoft and was told that in order to make a meeting request you either need to be within the organization or be a guest. Can you confirm this or make a suggestion of how to accomplish forwarding an external Teams meeting request to our Teams Room? Your prior post seems to indicate that it is a simple setting to allow external requests. Perhaps a screen shot of the setting that I can share with the IT guy?
Jan 14 2021 08:47 PM
@pdnielsen What they have to do is to turn on "ProcessExternalMeetingMessages" for that room mailbox, that is done with Set-CalendarProcessing.
Jan 15 2021 11:59 AM
@Linus Cansby Thank you. It now accepts the invitation and shows the meeting organizer's name on the screen as it should just like when people from within our organization schedule a meeting. The problem now is that there is not a Join button on the screen and the Join button on the TC8 does not function. I have not found a setting within the Poly Native Teams App for internal/external. Do you know anything about the Poly App or do I need to go to the Poly forums?
Jan 31 2021 04:40 AM
Jan 31 2021 02:13 PM - edited Jan 31 2021 02:14 PM
Another thing to check. Are you using SafeLinks as part of Office365 ATP? If SafeLinks is rewriting link URLs on incoming emails from external addresses (even internal depending on how its been configured) then the MTR devices will not recognise the appropriate link in the invite as being a Teams link and will therefore not show a 'Join' button. The solution is to whitelist the applicable domain/url in the SafeLinks policy.
Apr 02 2021 12:37 AM
@pdnielsen We had the exact same issues with a new Yealink bar, no join button on the external touch display (invite from outside of the company's AD) or if the join button is there (from inside the AD) it is not working.
For the first problem we got a Hotfix firmware from Yealink and they are working on the second problem so most likely a MS Teams issue rather than hardware...?!?!?
The Yealink has a "Proximity" join which is convenient so we can join the meeting on a phone or Mac/PC while being in the room and then "add a room" which transfers the meeting to the room.
Jul 15 2021 07:57 AM
Sep 28 2021 01:55 AM
Microsoft makes this so unnecessarily difficult. My people have been tied up for a lot of their time trying to troubleshoot this idiotic problem. We paid a lot of money for a Logitech rallybar and tap app and it works nicely internally, but not being able to use our meeting room when we have an externally-generated teams meeting is insane. What is worse is there seems to be no simple setting to resolve this anywhere. Surely there is some simple setting to allow this?
Oct 01 2021 07:40 AM
I had same issue with Teams Rooms and Yealink touchscreen system.
I found a work around in 6 simple steps: