This document describes the network requirements of RetailPlayer S400 and SP400 devices to operate correctly when attached to a computer network.

The document helps network IT departments making sure the RetailPlayer establishes the needed connections to operate free of issues.

ConnectionDescriptionIP AddressProtocolURLPort
Portal*

The RetailPlayer portal is the platform used to configure and control RetailPlayer devices. It's a mandatory connection to ensure device operation in Portal Mode.

The connection is established via HTTPS and upgraded to Secure WebSocket (wss).

The HTTP connection is used to retrieve the time from the Portal even if the HTTPS connection cannot be established (an add-on to the NTP, that could fail in some networks) - The Portal sends a 404 reply to this request, the timestamp in the reply is used by the device to set its own time and date.

195.201.171.48

HTTPS

HTTP

https://player.manage.barix.com

443

80

Update Server

FW <=6.2.0

The server that the RetailPlayer contacts to update the firmware. It's a mandatory connection if the user desires to update the firmware from the Portal and not locally from the web UI.

The connection protocol to the download server follows the same protocol configured on the device web interface, thus it can be over HTTP or HTTPS.

N/A

Check locally to which IP your DNS solve the FQDN of the download server

HTTP(S)


download.k3x.io

Canonical name:

storage.googleapis.com

80(443)

Update Server

FW >=6.2.1

N/A

Check locally to which IP your DNS solve the FQDN of the download server

HTTP(S)

release.barixupdate.com

Canonical name:

storage.googleapis.com

80(443)
Barimon Server****Barimon is Barix's utility server for monitoring devices remotely. This is not a mandatory connection.62.75.191.52HTTPhttp://www.barimon.net80
Flexa Server**Flexa Server is Barix utility that allows the smart distribution of python applications for IPAM based modules. This connection is not mandatory.52.169.188.236HTTPShttps://flexa-base.azurewebsites.net443
NTP***

The Time synchronization server - it is derived from one of the pools set in the device.

NTP is crucial for setting the time at every boot, failing in doing so the devices will not be able to validate HTTPS TLS certificates resulting in the inability to connect with the Portal (but still they are able to play http audio streams)

Derived from the Pool of addressesNTP

1.barix.pool.ntp.org

2.barix.pool.ntp.org

3.barix.pool.ntp.org

123
DNSDomain Name ServerSet by DHCP or manually in the local web ui of the player

DNS


53
Audio streamsThese are channels configured to play-out the audio from the S400 RetailPlayer. In most cases audio streams are http or httpsYour streaming server IP address

HTTP

or

HTTPS

configurable in the settings of the Portal or the player

80

or

443

Priority URL

The Priority URL support HTTP(S) or RTP Multicast or Unicast protocols. When used with Multicast the device sends out in the network IGMPv2 packets, switches that support IGMP will be able to identify this packets and use it accordingly to be aware of the ports joining the same Multicast group.

In FW <=6.2.0 the default address is set to rtp://224.0.0.56:12345

Configured on device web interface


*Portal connection: from FW version 6.0.0 the players send an HTTP HEAD request to the Portal to retrieve date and time information

**Flexa Server connection has been removed starting from FW version 6.0.0 

***From FW version 6.0.0 the NTP servers are exposed in the web UI of the players, thus configurable bu the user. The default pools are the ones described in the table

**** Barimon function and its connection have been removed starting from FW version 6.0.0