I have problem connecting to Office365
Microsoft will discontinue support for basic authentication and EWS api for Office365.
So in order to run LoopMeeting in your Office365 environment you need to use Oauth2 autentication and MSgraph api.
See this link for further information: LoopMeeting Oauth2 and MSgraph
Why does my application “stop” and only display company logo at startup?
In some rare cases the configuration get’s corrupted.
To fix this issue you have to factory reset the panel, reconfigure and update to latest app version.
See chapter 5 in the LM-1012T operation manual
I have an Exchange environment running on Windows Server 2008, 2008R2.
From LoopMeeting version 126.96.36.19933 the app enforces TLS 1.2 communication with the Exchange environment. The reason for this enforcement is to follow best practices for secure communication and make sure the app is PCI compliant.
In older deployments of Exchange/Windows Server TLS 1.2 might not be enabled by default. It is supported, but not enabled. The enablement of TLS 1.2 needs to be done at least on the frontend servers in your environment for LoopMeeting to work.
To test the support for your frontend servers – go to the SSLlabs website and run test for your internet facing host.
If your servers does not support TLS 1.2 you need to enable it for LoopMeeting to be able to communicate. We also suggest you evaluate to disable TLS 1.0 and 1.1 for security reasons.
If you do not want to enable TLS 1.2 make sure you use LoopMeeting version 1.0.23 or above and select “Microsoft Exchange SSL” as server.
I run Office365 and have LoopMeeting on LG or Philips panel.
Microsoft will discontinue support for encryption protocols TLS 1.0 and 1.1 on Office 365. Office 365 still works with TLS 1.0 and 1.1 but is not oficially supported. Office 365 will depreciate TLS 1.0 and 1.1 starting from June 2020.
If you are useing LG or Philips the LoopMeeting app needs to be updated to enforce TLS 1.2.
For LoopMeeting LM-1066 and the new LM-1012 LED this is not an issue since they run TLS 1.2 by default.
If you want to be security compliant, download our latest version.
Why does connection to my exchange environment fails?
Check out the Troubleshoot Video. There can be a number of reasons why you can’t connect to your exchange environment.
Here is an overview of the most common reasons:
The panel is not network connected.
Can be controlled by opening the Internet browser on the panel and try to open a web page.
The time and date is incorrect.
In Android OS, check time and date settings to see if it’s correct. If not, check time zone settings and that you have internet access for NTP time sync. If you want to use an internal NTP server, you can set the internal server here. Then restart the panel. It’s crucial that time and date is synchronised with a NTP server.
The exchange server credentials is wrong, server address is wrong, or the the panel can’t reach the Exchange environment.
This can be checked by opening the internet browser and your Outlook Web Access – https://”your_exchange_server”/owa log on with the credentials to see it it’s correct.