| Connection | Description | IP Address | Protocol | URL | Port |
| Portal* | The RetailPlayer portal is the platform used to configure and control RetailPlayer FLEX 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 | HTTP or HTTPS | https://player.manage.barix.com | 80 or 443 |
| Update Server | The server that the Flex player 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: 157.90.165.210 IPv6: 2a01:4f8:1c1c:5983::1 | HTTP | http://release.barixupdate.com/ | 80 |
| 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 | 1.barix.pool.ntp.org 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 | These are channels configured to play from the audio-out of the FLEX Player. | IPv4: 104.236.202.73 | HTTP or HTTPS | *.overheadmusic.com | 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 In FW > 6.2.0 the priority URL is empty by default | Configured on device local web interface |
FLEX Network Requirements
Below are the network requirements of Flex devices to operate correctly when attached to a computer network.
*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 by the user. The default pools are the ones described in the table
Bandwidth Requirements and Usage:
- Required speed: At least 0.5 Mbps of available internet speed to stream music smoothly.
- Upload Usage (outbound traffic): The Flex should average less than 75 MB per day to remain connected to the player portal.
- Download Usage (streaming traffic): One stream at 128 kbps uses approximately - 0.06GB (56 MB) per hour
It's All About Quality
Stream quality is measured in kilobits per second (kbps). Lower bitrates (64–128 kbps) use less bandwidth, while higher bitrates (192–320 kbps) increase audio quality but require more data. We deliver our music streams at 128 kbps stereo, providing an optimal balance of consistent sound quality and efficient bandwidth usage for most business environments. Total bandwidth usage depends on:
- Stream bitrate
- Hours of playback
- Number of active devices
CONCERNED ABOUT BANDWIDTH?If bandwidth usage is a concern, consider requesting the use of OPEN HOURS scheduling, which determines when a FLEX unit is allowed to stream music.