This article provides some tips for troubleshooting network issues on an OMNIplayer, a media player used for digital signage. We also highlight third-party websites that may cause problems with time synchronization for different devices.
Basics
Databeat has a few requirements which may already have been approved by your organization or by default. (Read more: Network access and requirements)
In general, troubleshooting by elimination or simply talking internally with your IT department could provide you with the requirements and information you need, but to help speed things up here are some pointers on the most common issues we hear about when troubleshooting the Databeat OMNIplay app.
1. Incorrect date, time, or DST settings?
If you are using a Proxy, or simply blacklist everything you have not whitelisted, then we recommend checking out the network traffic/package capture from the device after a reboot to see where the network-based time, date, and DST synchronization fails.
Please follow the installation guides with accuracy. The device configuration, especially time and date settings, are vital for the device to be allowed on the network to download content, report, and operate after installation.
Tip: You can use https://time.is/ in your channel as a web page or as an iframe widget to troubleshoot.
2. Deprecated or outdated web browser version?
Security patches, policies and requirements may deem your web browser incompatible. Hopefully you can upgrading by talking to the manufacturer or you would need to consider other hardware options. Unfortunately, both LG nor Samsung does not allow the built-in web browser to be updated. However, Android is quite flexible, both in terms of web browser and Android version, talk to your supplier or partner. (Or Check out this article explaining how to update the web browser on certain Android devices)
3. Using a network proxy?
From our experience it usually works as expected when configured correctly, but please note that there have been cases where contacting the manufacturer of the device and updating the firmware has been necessary.
4. Your network may blacklist third parties
Based on our troubleshooting experience over the years, we have noted some third parties that may be blocked in the network and cause issues with time, date, and DST synchronization for different devices:
- Azure Traffic Manager
TrafficManager.Net, time.trafficmanager.net, and timestg.trafficmanager.net are associated with Azure Traffic Manager, a cloud-based traffic routing service by Microsoft that distributes user traffic across multiple endpoints for improved availability and performance of web applications, API endpoints, and other network services hosted in Azure. - WorldTimeServer
WorldTimeServer.com provides current local time in various cities and countries around the world, as well as additional information such as time zone, sunrise and sunset times, and daylight saving time information. The website also offers tools for creating customizable clocks and widgets.
- Samsung websites
SamsungCloudSolution.com, cdn.samsungcloudsolution.com, and oempprd.samsungcloudsolution.com are websites related to Samsung's cloud-based solutions for businesses, offering cloud storage, security, data analytics, and IoT solutions to help businesses manage and store their data securely in the cloud, analyze their data to gain insights, and connect and control their IoT devices.
We hope this article was helpful. If you have any further questions or need assistance, don't hesitate to reach out to our support team.