RetailPlayer Network Requirements
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.
Connection | Description | IP Address / Name | Protocol | URL | Port |
|---|---|---|---|---|---|
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.126.106 | HTTPS HTTP | 443 80 | |
Flexa Registry*** | The Flexa Registry is the Barix service used to inform the devices to which Portal they need to connect with. It is contacted by the device 5 mminutes after boot. Without the ability to reach the registry the device won’t connect with the Portal | HTTPS | flexa-base.azurewebsites.net | 443 | |
Update Server | 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. | IPv4: 49.13.159.43 IPv6: 2a01:4f8:1c1b:6c24::/64 | HTTP or HTTPS | http://release.barixupdate.com/ | 80 or 443 |
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 addresses | NTP | 2.barix.pool.ntp.org 3.barix.pool.ntp.org | 123 |
DNS | Domain Name Server | Set by DHCP or manually in the local web ui of the player | DNS | 53 | |
Audio streams / SnP Channel | These are channels configured to play-out the audio from the S400 RetailPlayer. In most cases those are http or https (ftp is also supported by SnP). Chack with the music provider which IP:PORT should be allowed in the network. | Provided by the music provider | HTTP / HTTPS / FTP | configurable in the settings of the Portal or the player | Configurable |
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 In FW > 6.2.0 the priority URL is empty by default | 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
**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
'*** From FW v7.0.0 onward