Cannot Join External Skype for Business Online Meeting - RealPresence Group 500

[Anonymous]

Skype meetings that are sent from our own Outlook Online to the Group Series appear on the touch panel with the "join" option and are able to be joined. However we have allowed external meeting requests on the room resource as we need to allow the Group Series to be booked in this way. The Skype meetings are accepted and appear on the touch screen however there is no "join" option and only 3 dots where the join should be. How can I join externally created Skype meetings? We have other VC units (Microsoft Surface Hubs for example) that are easily able to join externally created Skype meetings. What is the issue here? Note: Even though the meetings are externally created they still use the same Exchange\Skype online calendar\mailbox for the Skype room system accounts the group series are logged on to. So the meeting is internal but the request is processed as an external request.

What is different in the way the GS touch panel reads and displays the meeting requests that make the "join" feature not work in this instance? 

Model: RealPresence Group 500

SW: 6.1.1-370109

ModelModel

[SteffenBaierUK]

Hello Not an EV Guy,

welcome to the Polycom Community.

This should be the same issue as the search can find => here <=

Please get this into support.

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

[Anonymous]

Hi Steffen Baier UK,

Thanks for the prompt explanation. That makes sense and explains why other MSFT based platforms can still read it and use the join feature.

Do we know specifically what EXO is stripping out? I assume it is not the entire TNF as part of the invite is still there. And then if we do how can we configure EXO\O365 to let is pass? The only setting I am aware of in O365\EXO is to turn TNF On\Off for specific domains. Nothing more granular than that. I have control of all the Exchange servers\EXO tenants in the mail routing path can make changes to TNF rules as required.

If this is a feature request then it's a way off I assume? So for this situation I need to work around to have EXO not strip out the bits of the TNF we need.  Surely this must be pretty common now especially in blended environments where we have some domains and mailboxes on premise and GS500 connecting to SfB Online?

Thanks!

[SteffenBaierUK · Accepted solution]

Hello Not an EV Guy,

I believe this is already addressed in the next release but opening a support ticket will give you access to our team which can share dates etc.

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

[Anonymous]

Thanks,

I opened a support ticket yesterday in tandem with the forum post. I will await their reply on timeframes. In the mean time I plan to test the below solution as a work around. Would you expect this to viable in the mean time?

https://technet.microsoft.com/en-us/library/mt691563.aspx

Regards.