Networking requirements

You are here:

This document details the technical requirements regarding connectivity for the access to the different services provided by Admira.

If the network in which you are going to deploy your players provides unrestricted access to the Internet, you don’t need to read on. You will not have any problem getting your players to work.

If, on the contrary, the players are going to be installed on a network with limited Internet access (corporate networks, hotspots, etc.), it is important that you check with the network administrator if you meet the requirements for the player to run properly.

We have three possible scenarios:

  1. Access to the web portal from a browser.
  2. Connect a Player to the digital signage platform to broadcast content.
  3. Mass upload of content by FTP.
  4. Remote desktop access from the web platform.

Web access to the portal from a browser

To access the portal it is necessary to use one of the officially supported browsers: Mozilla Firefox or Google Chrome.

Access to the Admira web platform is via the secure HTTPS protocol. Thus, the only requirement is to have access to the IPs of the host new.admira.mobi on port 443 and / or 80 via TCP protocol.

The URLs to access the service is:

  • http://new.admira.mobi (redirects to HTTPS)

The Admira website loads certain resources from other providers, so in addition to the mentioned URL, we have to allow the HTTP traffic against the following domains:

  • https://apilb.admira.com
  • https://iotlb.admira.com
  • https://*.googleapis.com
  • https://*.gstatic.com
  • https://*.google.com
  • https://*.ggpht.com
  • https://*.google-analytics.com
  • https://*.matterport.com
  • https://cdnjs.cloudflare.com
The asterisk “*” indicates that all subdomains of the specified domain must be opened. In case of being a problem, contact Admira for the complete list of domains to allow.

The access to the Admira portal that is provided through https://new.admira.mobi, is a high availability service accessed through a load balancer. The public IPs of this balancer are dynamic and unpredictable. If your corporate network is not capable of managing access at the application layer level and it is only capable of doing it at the network layer level, you must access the application through the following URL: https://static.admira.mobi at the IP (50.17.213.23).

However, you must consider that this is not the preferred option for accessing the service, since under this scenario the service is no longer provided in High Availability.

Connecting a Player to the platform

To successfully register and connect a player to the platform, the computer on which said player is installed must have access to the hosts and ports specified below:

Destination HostPortsProtocolVersion Player
apilb.admira.com (IP dinámica)80,443TCPAdobeAir /  HTML5(all)
install.admira.com80,443TCPHTML5 (sssp1/soc/webos/tizen)

legacy.admira.mobi
80,443TCPAdobeAir / HTML5(all)
socket.control.admira.com80,443TCPHTML5(all)
Table 1

Alternatives in networks with restricted internet access

If the player is installed on a network with restricted internet access, the network administrator has different options to allow the player runs properly:

  • Option 1: Explicitly allow outbound requests to the hosts / ports listed in Table-1. Depending on the architecture of the corporate network, this can be done by using VLANs or specific cabling for the Players.
  • Option 2: Use your network’s HTTP proxy server: it requires setting the access data to your proxy in the admira player. Both the Adobe Air-based Windows Player and recent versions of the HTML5 player support proxy with and without authentication.

At layer 3 (Network) and layer 4 (Transport) apilb.admira.com and install.admira.com are the same service. That is to say: opening one implies opening the other since they both have the same IPs and ports. At layer 7 level (Application) the name of the service changes. Thus, if we are giving access at the level of layers 3 and 4, there are 3 rules / exceptions. If we open at layer level 7 they are 4.

If none of the above options is technically feasible, since sometimes the firewall rules only allow IPs instead of names, access to HTTP port 80 and 443 of the IP corresponding to staticapi.admira.com should be enabled, which is always ( 50.17.215.152). Additionally to legacy.admira.mobi 50.17.213.23 on port 80.

Player installer download

To download the player installer, we require access to:

Destination HostPorts ProtocolVersion Player
install.admira.com (IP dinámica)80,443TCPHTML5
new.admira.mobi(IP dinámica)80,443TCPAdobeAir
Table 2

Mass upload of content by FTP (optional)

In addition to uploading content from the web portal, the option of uploading content via FTP is available -on demand. If your project requires this option, you must request that this functionality be activated, and bear in mind that the equipment used for uploading files via FTP is capable of connecting to the hosts and ports listed below.

Destination HostPortProtocol
live.admira.mobi21TCP
Table 3


Remote desktop access (optional)

For Admira Premium clients, we include the remote desktop access service via the web from our platform. To access this service you need:

  1. Access to port 22 (TCP) of the intermediate access server designated in each case.
  2. The express consent of the client.
Destination HostPortProtocol
tunnel[n].admira.mobi22TCP
Table 4

If not stated otherwise by Admira, the destination host is tunnel01.admira.mobi.

Print Friendly, PDF & Email
Table of Contents