Network access and requirements for the DatabeatOMNI platform and services

In this article, you will find the network requirements for all DatabeatOMNI services and apps. The basic concept is that your OMNIplayer and OMNIcast devices must be able to communicate with the DatabeatOMNIserver to function.

Network requirements for DatabeatOMNI

URL and security

OMNIplayers require access to DatabeatOMNI on open URL:
All communication is based on HTTPS. (More info on HTTPS here).

DatabeatOMNI Server IP address

Our servers, on, have the common IP address

(Previous DatabeatOMNI Common IP and are no longer in use).


All communication between DatabeatOMNI and OMNIplay is via Port 443 (HTTPS/SSL).

If your organization has a highly secure and strict network, or simply requires more information, please contact to confirm.

Using Widgets

With the use of widgets, users may add a host of different features and integrations on screen in addition to displaying standard content (video, pictures, graphics, and webpages). This can be newsfeeds, weather and traffic info, calendar content, messages, dashboards, and social media posts as well as different frameless web pages (using iframe technology).

This means that Databeat OMNIplayers may need to access other webpages, servers and services on different domains, even internal (not on the internet) webpages. Examples can be Social Media services, Office 365, internal Microsoft Exchange Servers, Google G-Suite, Newsfeeds, etc. The OMNIplayers will need access to these services and they must be based on https to work.

Accessing web pages and web integrations.

The DatabeatOMNI web widget feature provides a flexible, yet simple way, to integrate with other systems. Learn more about this feature here.