The aim of this document is to guide the user through the functionalities of the IP Audio Client application, which is the software running on the following Barix Products:
IP Audio Decoder with stereo line level audio output on RCA connectors
IP Audio Decoder with up to 40W amplified output on screw terminal block to drive loudspeakers
IP Audio Decoder with up to 6W amplified output on screw terminal block to drive loudspeakers
Throughout this document those devices are referred to as compatible devices or IPAC devices
The document describes the elements and the functionalities of the application in detail. It doesn't cover arguments related to the physical connections of the IPAC devices, delegating this description in the Quick Install Guide of each one of them.
What is IP Audio Client?
IP Audio Client is a flexible application that controls the audio play-out of the devices on which it runs. It allows the possibility to set up multiple "sources" from where getting the audio and organize them in a multi-layer priority hierarchy, meaning that the source with an higher priority will always play over sources with lower priority.
Thus IP Audio Client satifies multiple application needs, it can work as:
a mass notification endpoint
a background music player
a paging endpoint
a RTP decoder
a VoIP / SIP endpoint
a pre-recorded message player
an AES67 endpoint
IP Audio Client can be configured to run in 2 modes:
One mode excludes the other, meaning that if the application is set to operate in "IP Audio Client" mode it cannot work in AES67 mode. For this reason the entire user manual on AES67 is detached from this manual, which describes solely the IP Audio Client application mode.
About this manual
This manual is intended for distributors, installers and end users of the IP Audio Client solution. It will cover first configuration steps plus details on how to use the applications afte installation.
This manual assumes that the firmware version installed on the compatible devices is the latest one released. (check out the release notes for information on the release history and change log)
Barix always recommends to run the latest firmware available and provides a dedicated download area for registered users on www.barix.com/downloads.
IP Audio Client offers the possibility to update its firmware locally from its web user interface (more details in the Update Page section)
Additional documents and support
The following additional documents are available for the IP Audio Client application:
Exstreamer M400 - Quick Install Guide
IP Former - Quick Install Guide
IP Audio Client - Knowledge Base articles
Product sheets: These documents are available for download on the Barix website for all users in the download area www.barix.com/downloads
Beside checking regularly the Barix website and the Barix help, the user has access to support in several ways:
All IPAC devices offer the possibility to connect to the network via ETH (Ethernet) wired interface (10/100Mbps). If the compatible device supports PoE, this is the only cable required to get the device powered, otherwise you would need to power the device using an external power supply.
IP Audio Client, by default, is configured to be a DHCP client, it acquires an IP address from a DHCP server reachable in the network.
The first configuration of the device involves the following steps:
Make all the necessary connections: audio, network and then power up the unit
During boot the device will announce its IP Address (Sonic IP function), make sure to hear the audio on the output and note the IP address on a paper. An IPAC device takes approximately 40s to finish the boot process
Connect to the IP Address of the device via web browser by typing in the URL the IP address just heard
Enter username and password (username: admin - password: printed on the backside of the device)
Locate the SOURCES tab. Switch ON anyone of the sources and select the type of Source desired among the 7 available. To play BGM from internet for example select Barix Radio or HTTP, which allows you to insert any stream url (icecast, shoutcast or any other web radio)
Click SUBMIT - After few seconds the music starts
This was a quick start chapter to get the device up and running in less than 5 mins playing BGM. If you have issues finding the IP Address of the device, please read the following 2 chapters.
Retrieve the IP address using the Sonic IP® function
All Barix devices are equipped with a function called “Sonic IP®”, meaning that when you boot the device and this is connected to a network where a DHCP server is present, the device will acquire an IP address and announce it over its audio output. This function is useful when you connect to the device for the first time and need to access its web interface for performing the first configuration.
IMPORTANT: Before connecting to the amplification system, make sure the volume of your system is lowered at minimum or completely switched off to avoid potential damage to the system.
Follow the below steps to take advantage of the SonicIP function:
Connect the audio output to the receiving system, this varies depending on the compatible device being used
Make sure the receiving system works fine so that when the compatible device boots you are able to hear the IP Address
Power up the device. If the compatible device supports PoE, this is the only cable you need
After 20s listen to the Sonic IP® announced and note it somewhere
After 35s the device is ready
Retrieve the IP address using the Discovery Tool
Other than the Sonic IP® function, there are other ways to find out a Barix device’s IP address. One is by using the Discovery Tool from Barix.
The Discovery Tool is freely available for download from www.barix.com/downloads.
The Discovery Tool is written in the Java programming language, so it requires a Java Runtime Environment (JRE) installed on your computer. If you do not have a JRE installed, you can download and install it from: https://www.java.com/en/download/ Java run time environments are available for many major operating systems. If you are running the Discovery Tool on a Linux or UNIX platform, the Discovery Tool also requires the X-window graphical user interface.
The Discovery Tool is distributed in a Java Archive (.jar) file. On most operating systems you can run the Discovery Tool by simply double-clicking on the discover.jar file. When the discovery tools open it will show the following interface:
Click the "Get" button to initiate a search. The program will scan the network and list all the Barix devices found with its current IP address, MAC address (labeled "Ethernet Address" in the Discovery Tool), firmware version, and other information. The Discovery Tool will find any device that is on the same network as the computer running the tool, regardless of their current IP address setting. The tool will not search through a router to another subnet. Use the address that appears in the Discovery Tool to access the compatible device via a web browser.
Setting a static IP Address using the Discovery Tool
In the discovery tool window Double click the IP Address field of the device which you want to change set the Static IP Address
Enter the IP address you want to assign.
Click SET in the lower right corner - the tool will reply with a “No error” in the “Set reply” column.
Reboot your device and access the web interface through the newly assigned IP Address. Make sure to finalize the network settings configuration (Subnet, Gateway, DNS), otherwise the device might not work correctly.
With the IP address of the device is possible to connect to the web interface served by the the IP Audio Client application.
Open a web browser and type the IP address of the device in the URL field.
By default new devices or devices that are accessed after a reset to defaults (soft or hard) will ask for credentials to login:
password: printed on the back-side of the device
The settings page is where are available the network settings, time settings, security settings of the application. If the IPAC device has a built-in amplifier there is also a section dedicated to the amplifier controls.
The window is organized in:
The top navigation bar. In addition on the top right corner there are the MAC address and current firmware installed on the device
The operational area. Where the user input values and set parameters
The help section on the left side of the window
Main application controls
In the top bar it is visualized the name of the Firmware and the "Device Alias"
A custom name that can be assigned to the device. This name shows up also in the remote configuration tool
Default value is: " "
The main output volume of the device. From 0% to 100%
Default value is: 50%
Select the main application mode between IP Audio Client and AES67
Default value is: IP Audio Client
In this area, it is possible to configure the device’s network interface and few other functions.
IP Audio Client, like all other Barix products, supports the Dynamic Host Configuration Protocol (DHCP), which allows the device to acquire an IP address available from a pool of addresses hosted by a DHCP server. It is the server that offers an IP address to the device when discovered on the network. The IP address offered by a DHCP server comes with a lease time, meaning that when the leased time is over the DHCP server re-issues the IP addresses to the devices on the network, with the possibility that it might assign a different address than the one assigned previously. In addition, the DHCP server provides all associated information to the requesting device, such as subnet, gateway, and DNS addresses.
This enables / disables the Avahi service, which is the network discovery daemon based on mDNS / DNS-SD used by one IP Audio Client device to discover in the network other IP Audio Client devices.
When enabled the device sends a query packet on the network at the Multicast IP address: 188.8.131.52 on port 5353 as defined by the mDNS protocol. The interval at which these query packets are sent doubles as time passes and no other devices are found in the network.
Sonic IP / Sonic IP Volume
Enable / Disable the Sonic IP function so the device announces its IP Address during boot time.
Set the volume of the SonicIP with the corresponding slide.
Configure the protocol used to access the web interface of IP Audio Client. It can be HTTP or HTTPS. When set in HTTPS the communication between the browser and the device is encrypted. The application uses a self-signed certificate for the SSL/TLS authentication, not one from a CA (Certificate Authority) considered safe from web browsers. For this reason when using HTTPS the browser will warn that the certificate used is not a trusted one (NET::ERR_CERT_AUTHORITY_INVALID). To continue and open the web interface it is necessary to advance manually, “forcing” the browser to trust the self signed certificate. The connection and data communication will be fully encrypted.
Set the DHCP (Yes) or Static IP addressing mode (No).
Only available in DHCP Mode
Provides the DHCP with an hostname to easily identify the device in the DHCP list of leased IP addresses.
Default: " "
Static IP mode
It is the fixed IP address of the RetailPlayer device. The IP address is the unique identifier of a device on a network, in case of static assignment make sure that no other device on the same network has the same IP address assigned to the RetailPlayer
In addition to the IP address, it is mandatory to provide information about the subnet mask. The subnet mask indicates which bits in the IP address are used for the network portion and which bits for the host portion. It is common in Class C LAN to see 255.255.255.0, this configuration indicates that the first 3 octets of the IP address (e.g. 192.168.1.100) are dedicated to the network identification, while the last octet (e.g. 192.168.1.100) is dedicated to the host identification on the network
Gateway IP Address
The Gateway IP is the address of the device that bridges your Local Area Network with the Internet. Typically is a router where devices on a LAN are connected. For using the RetailPlayer in all its cloud-based features, but also to receive a stream from an internet radio in stand-alone mode, for example, it is essential to provide this address. If you are not sure about the Gateway address in your network contact your network administrator
Automatic Domain Name System resolution. If set in Auto the DHCP server will provide the address of a DNS server to contact for the IP name resolution process.
If DNS is set to Manual the device expects the Primary and Alternative DNS server fields to be filled with the related information. When Ethernet IP method is set to Static, DNS will always be set Manual and it is mandatory to provide the address information
Primary DNS and Alternative DNS
This address is for the Domain Name Server. It tells the RetailPlayer which DNS server to contact to resolve domain names into IP addresses. I.e the address of an internet radio like http://barix.streamguys.net/Barix_hi has to be translated into an IP address, this is the job of the DNS server. The alternative DNS is a backup resolution in case the primary DNS server is down. The alternative DNS is not a mandatory field. If you are not sure about the DNS Server address to be used, contact your network administrator.
It's important that the IP Audio Client device operates running the correct date and time. IP Audio Client uses an NTP daemon to set its system time. The NTP protocol is used on the standard port 123. The time set by NTP is in UTC.
On the web interface, the time settings allow the user to change the default NTP pools used by the device. This is because in some situations, customers might be using their internal NTP servers, or they simply prefer to use others. The fields accept either a domain name (which requires a valid connection to the DNS to be able to associate an IP Address to the DN) or an IP Address. It is possible to check the system time in the Status page of the device.
NTP sends packets once every 4mins to the same NTP server to check for clock updates. By leaving the configuration fields empty it is possible to disable the NTP function.
This area is dedicated to secure the login to the device web interface device and to enable or disable the possibility to run critical operations: reboot, reset to factory defaults and update
Enable or disable the reboot function of the device from the web UI
Reset Factory Defaults
Enable or disable the possibility to reset the device to factory default from the web UI
Enable or disable the possibility to update the device from the web UI
Web UI Password
Set the password to access the web interface of the device. If a password is already set another field is displayed: OLD PASSWORD, which is required to modify the current password
default username: admin (it cannot be changed)
default password: printed on the backside of the device
Allows the possibility to upload custom .crt certificates to the device. Useful when the device is used in private enterprise networks where a private CA is in place to validate secure connections
By clicking on the button SUBMIT all the changes made in the SETTINGS page are applied in the configuration.
By clicking on CANCEL all the changes are not applied and the fields return to their previous inserted value.
A source is an originating source of audio, the application allows to arrange sources in 5 priority layers where the layer with the lowest index has more importance compared to the layer with the highest index. Meaning that Layer 1 is the most important and will play on top of any other layer, layer 5 is the least important and will play only in absence of incoming audio in any one of the other layers.
Each layer represents a priority level and a source type can be assigned to it. The common functions available in each layer are:
ON / OFF
Allows to switch the corresponding layer on or off
Set the volume for the corresponding layer relatively to the master volume configured in the settings page, this volume doesn't change in real time, the configuration has to be SUBMITTED for the change to take effect
Each layer can be assigned a name that is the name of the layer
7 different source types are available from the drop down menu of each layer:
Default source configuration
2 sources are ON by factory default: SynApps and InformaCast
NOTE: InformaCast is available only if the IPAC device is licensed, thus the PN purchased is the "Informacast" version.
This allows the device to automatically register with the corresponding mass notification servers as soon as they are plugged. Read the following chapters for more information.
Singlewire's Informacast is a mass notification platform that streams audio to certified endpoints registered with the InformaCast server. This is how the configuration of an InformaCast source looks like:
Singlewire's InformaCast requires a license in order to run on IP Audio Client, just like on any other Singlewire certified endpoint. Make sure to order the right PN when purchasing the IPAC compatible device. When your device is running the correct InformaCast license its Feature will appear as "InformaCast" in the System Status → Licenses as per below screen
IPAC implements the InformaCast API that rules how the IPAC device: register with the InformaCast server, receive commands and notifications. For this reason the configuration is easy and straightforward.
The registration process with an InformaCast server doesn't require any configuration if the server is reachable from the network where the device sits. IP Audio Client devices implement registration over SLP (Service Location Protocol), if that fails TFTP (Trivial File Transfer Protocol) is used (requires DHCP option 150 to be configured in the DHCP). If none of the mentioned protocols are available in the network or failing it is possible to specify manually the URL in the "InformaCast URL" field in the Source configuration.
The automatic registration process is well described in the below logic diagram (picture taken from InformaCast IP Speaker registration notes):
For more information and troubleshooting steps about the InformaCast registration visit this link provided by SingleWire: IP-Speaker-Registration-and-Troubleshooting-Guide
In case your InformaCast server and the IPAC device is behind a firewall, check this link: Informacast Inbound / Outbound connections
InformaCast Manual registration
When entering the URL manually in the source configuration of IP Audio Client the URL should be: http://<ICast_server_IP>:8081/InformaCast/admin
After the registration the device heartbeats the server once every 5 minutes to keep the server updated about its existence. This interval value cannot be configured by InformaCast (despite there is a function on InformaCast that allows it), it is fixed in the configuration file of the device. If the device doesn't send the heartbeat to the server the server will consider the device "expired" and it is not possible to send notifications to it.
InformaCast IDLE Audio
IDLE Audio is a function within the InformaCast source available only when the InformaCast URL is explicitly specified (the IDLE Audio configuration fields appear when the user starts typing in the InformaCast URL field).
This function allows to specify an RTP stream to play as background music when no notifications are sent. It can be seen as a "source-in-a-source". Of course it plays in the same priority level of the InformaCast source (but not over InformaCast notifications), thus if Background music is playing on Priority 1, lower level priority sources will never play.
The url RTP scheme should be as follow: rtp://<IP_Address>:[Port]
It can be a unicast or multicast IP Address.
IDLE Audio format specifies the decoding format to be used for IDLE audio.
How to setup InformaCast on IP Audio Client and receive notifications
Make sure that your InformaCast Server is running and that a network communication with the IPAC endpoint can be established. By default IPAC licensed devices will boot with InformaCast already enabled in the Priority source 1. The highest priority source. Boot your IPAC device.
IPAC devices will try to automatically register with the InformaCast server using SLP (Service Location Protocol), if this fails it will try with TFTP (DHCP Option 150 configured and available in the DHCP of the network), if this fails the device will not be able to register automatically with the server, thus it will be necessary to enter the URL of the InformaCast server manually in the source configuration. The speaker status will confirm the success of the registration when the device is registered with the ICast server providing the time of the last successful registration process.
Navigate to the InformaCast dashboard typing the URL of your server in the browser (typically the administration dashboard can be reached at: https://<ICast_IP>:8444/InformaCast/admin). In the dashboard it is possible to check the number of speakers currently registered with the server and ready to receive notifications.
Clicking on the IP Speakers icon in the top right corner of the dashboard opens the list of IP Speakers with all the details. Underneath the IP speaker list, there is an important flag "Automatically Add Hardware IP Speakers", if this option is not flagged IP Speakers will not be listed automatically, but have to be entered manually following the IP Speaker creation procedure (refer to InformaCast user guide)
Create a recipients group in Groups → Recipient groups accessed from the left side bar menu. Follow the on screen instructions to add IPAC devices to the group and confirm the group creation. This step is not mandatory as you can also send notifications to a pre-defined group called “all recipients” but it’s useful if you want to test only one IP Speaker or a group of IP Speakers.
Test an audio notification: click on "Send Message" in the left side bar, select a "Pre-Recorded" audio notification type, select the recipient group that has to receive the notification and click on SEND
While the notification is received on IPAC device it is possible to monitor the status in real-time. Check the “Advanced” tab to view more details such as the Multicast address used by InformaCast to broadcast the notification (this address is configurable in the InformaCast server)
SynApps Revolution by Intrado is a mass notification platform that streams audio to certified endpoints registered with the SynApps Revolution server. This is how the configuration of a SynApps source looks like on the IPAC device:
IPAC implements the SynApps API to: register with the SA server, receive commands and notifications. For this reason the configuration is easy and straightforward. SynApps is switched ON by default at priority 1 on any new IPAC device. If the device is licensed for InformaCast as well, it is ON by default but in the priority layer 2.
The registration process with a SA server from an IPAC can be automatic or manual.
Automatic registration requires the DHCP server in the network to have enabled and configured DHCP Opt 72 (more information on DHCP options here). Below is an example of a router where it is possible to specify the DHCP option and associate the IP Address of the SA server to it.
Once this is configured the DHCP will release this information to the IPAC device when it will try to find in the network the service provided by the SA server during boot time. If your device was already powered when the DHCP option was configured, reboot it to make sure it will find the information it needs to connect automatically with the SA server.
On IPAC devices the automatic registration is the default option. Leave the “Server” IP Address field empty in the source configuration to benefit from the automatic registration process.
Manual registration is an option to use when for example DHCP Opt 72 is not available in the DHCP server present in the network. Manual registration means that the IP Address of the SA Server IP address has to be manually entered in the SynApps source configuration in the IPAC device. See below example:
After the first registration the device heartbeats the server once every minute to keep the server updated about its existence. This interval value cannot be configured on the device nor on SA Server, it is fixed in the configuration file of the device. If the device doesn't send the heartbeat to the server the server will consider the device "expired" and it is not possible to send notifications to it.
How to setup SynApps on IP Audio Client and receive notifications
Make sure that your SA Server is running and that a network communication with the IPAC endpoint can be established. By default IPAC devices will boot with SynApps already enabled in the Priority source 1 (Priority source 2 if InformaCast is also running). If, after boot, the connection with the server can be established and the DHCP Server in the network provides DHCP Opt 72 the device will register automatically, if this fails or if DHCP Opt 72 is not configured or available the device will not be able to register automatically with the server, thus it will be necessary to enter the URL manually in the source configuration. Here is an example of what is shown in the speaker status after the device successfully registered with a SA server.
Navigate to the SynApps dashboard typing the IP Address of your server in the browser (typically the administration dashboard can be reached at: http://<SA_IP>
Navigate in the Configuration → IP Devices - Here is where all the active / inactive IP Devices appear, including IPAC devices. By clicking on the settings icon on a specific device it is possible to edit its details, i.e. assigning a name.
IPAC Devices are registered as Endpoints in the SA platform, devices capable of receiving audio notifications. Navigate in Configuration → Endpoints. All endpoints available and ready to receive notifications are listed. If it's the first time the device registers with the SA Server it might take some time to appear in the endpoint list. In some cases the time could be up to 10-12 minutes.
Prepare a notification: Locate Notifications → Manage → New Notification
Under General → Notification Type select "Stored Audio"
Under Message Details → Select audio: pick an audio file from the ones available. i.e "Air-raid-siren.mp3"
Under Endpoint and Contact Selection select the IPAC devices that need to receive the notification
Now you can SAVE or SAVE & SEND.
Clicking SAVE & SEND will send the notification to the selected endpoints
Monitor the notification receipt in the Speaker Status of the IPAC device while it is playing. The status will show the RTP Mutlicast address used by SynApps platform (this address is configurable in the SynApps server)
IC Paging is the Barix Paging solution that works relying on the Barix Paging Protocol, abbreviated BARP. A proprietary protocol developed by Barix to allow "BARP devices" to communicate between each other providing audio, control and status messages over a Broadcast or Multicast addresses. An IC Paging system includes:
one or more Master station(s) or ICMASTER running IC Paging firmware
one or more Endpoint(s) or ICCLIENT running IC Paging firmware
IC Paging firmware running on Annuncicom devices is not the same as the one running on IPAC devices. IP Audio Client is a self-contained firmware that implements compatibility with IC Paging devices, it is not an IC Paging firmware like the one deployed on Annuncicom devices
IC Paging implementation on IPAC devices allow IPAC to be endpoints, devices able to receive a stream coming from a master station. A typical example and use case is running the IC Paging firmware on an Annuncicom PS Touch or PS1 or any other Annuncicom device supporting IC Paging firmware and configure multiple endpoints to be part of different zones, so that it is possible from a button on a master station (correct name: PTT or Push-To-Talk) to page in the desired endpoints while pressing the button.
IC Paging Source Configuration
Modify the name of the priority layer
BARP Station ID
Unique identifier of the paging endpoint (also called Zone Group in an IC Paging system). Different endpoints can have the same Station ID. In the IC Master device is possible to assign every ID to groups to page different groups of IDs using different calling buttons (number of buttons depends on the capabilities of the IC Master device)
BARP IP Address
IP Address used by the endpoint to listen/send on the BARP ports. Modify the BARP IP address to use multicast if communication across different networks is desired, or if your LAN policy is not allowing broadcast. This field cannot be Unicast. The BARP address used by the endpoints should match the one set on the Master station and vice versa.
Default: 0.0.0.0 (which corresponds to the broadcast address of the network where the device is installed)
BARP Audio Port
Endpoint local port used to listen for incoming audio from the master. It is possible to configure any unused port between 5555-5999
BARP Control Port
Endpoint local port used to listen for incoming control messages from the master. It is possible to configure any unused port between 5555-5999
BARP Status Port
Destination port number to send status messages to the master. It is possible to configure any unused port between 5555-5999.
IMPORTANT - IC Paging Master Audio Format
IC Paging master running on Annuncicom devices is capable of sending audio in 2 sample rates formats: 8kHz or 24kHz - by default u-Law 8kHz is selected.
IPAC devices are capable of playing only 8kHz sample rates when receiving audio from an Annuncicom IC Paging master.
How to setup IC Paging system
After switching IC Paging Source ON fill in the Station ID field with the desired number. The Station ID is the Zone Group ID used in the BARP protocol to identify one or more endpoint devices. In this example ID 1 is used, all other IC Paging parameters remain with default settings (meaning that BARP will use the Broadcast IP of the network where the device is installed to propagate audio, control and status messages). Click on SUBMIT
On the IC Paging master station (a PS1 device in this example) navigate to Configuration → Basic Settings
On Annuncicom PS1 only one button / group can be configured, thus only Group 1 Address Map is shown. On a PS Touch or Legacy PS16 Annuncicom this would be from 1 to 8. By default each group contains 10 station IDs or zones. So by default our IPAC endpoint will end up being part of Group 1, since its station ID is set to be “1”. Up to 128 station IDs can be selected to be part of a group. To double check which Station IDs are called from a specific group click on View/Modify related to the group required, the below station selection window appears. It is possible to add/remove IDs from the group.
There are no steps required to perform as by default the correct station ID is part of the Zone Group 1. So when pressing the PTT button 1 on the PS1 the IPAC endpoint is called and automatically plays the audio received by the master station, typically from its microphone input.
Check the BARP settings on the IC Paging Master station. They can be found under “Configuration → Advanced Settings → BARP Control”. The Station ID of Master stations can be any number. It is used to notify endpoints about which master is sending the audio and control messages in a multi-master environment. The BARP broadcast address is the BARP IP Address to be used by master stations and endpoints. It has to match on both configurations. When it’s 0.0.0.0 means that the Broadcast IP address of the network will be used to propagate audio and control messages and from the master to fetch the status of the endpoints.
For our example there is no need to change this configuration as it is correct by default.
Important is to double check the audio format selected in the IC Paging Master. IPAC devices support only u-Law 8kHz for the IC Paging Source, thus the audio format must be the one specified. It can be found on the IC Paging Master station under “Configuration → Advanced Settings → Audio” . This is also the default setting on an IC Paging Master device.
The IPAC endpoint is now ready to receive audio from a master station. To summarize, using a DEFAULT configuration on a master station and on an IPAC device, it is only necessary to configure the STATION ID on the IPAC device to be any number from 1 to 10, since the configuration is already done on IC Paging Master station to page Station ID from 1 to 10 pressing the first button (in case of PS1 device it corresponds to Button “B”) using BARP address 0.0.0.0 and ports 5555 for audio, 5556 for control, 5557 for status, which are the same on all the devices when using the default configuration. When the IPAC device receives audio the Speaker Status changes as follow:
SIP stands for Sessions Initiation Protocol and it is the most used protocol for Unified Communication Systems or VoIP (Voice over IP) solutions. One (not more than one) of the priority layers of any IPAC device can be configured to turn the device into a SIP client via the SIP source and benefit from the broad compatibility with many third party vendors to integrate IPAC devices in infrastructures that are already using SIP as their main communication backbone.
A SIP source on IPAC supports 2 operational modes:
SIP peer-to-peer (p2p)
SIP peer-to-peer Mode
It is the most simple SIP mode, which doesn’t require a server for the nature of its working principle. A peer-to-peer communication is a connection established between 2 endpoints only. When in peer-to-peer mode the IPAC device can be called (it is working as a SIP receiver) by any other SIP capable device, the entire connection establishment, setup and dismounting is performed using SIP standards. Below a representation of a source configured in SIP peer-to-peer mode:
There is nothing to configure beside the name of the priority layer. To call an IPAC device in p2p mode it is enough to:
Switch ON one source to be SIP in peer-to-peer mode and click SUBMIT
When pressing the button “A” on the PS1 the call is started to the IP Address of the IPAC device. Pressing the button again terminates the call.
During the call the speaker status changes indicating the caller details
When using P2P mode, the IPAC device uses always the default SIP port 5060 and RTP port 5004. Make sure the remote peers are configured to communicate on the default ports as well.
SIP Server Mode
In Server mode the IPAC device allows to enter the values required to register with a central SIP server that is used to route and handle all the connections and calls between the SIP endpoints. IPAC devices support SIP and SIPS (Secure SIP) protocols (TLS + SRTP ) When switching in Server mode the SIP source display the following parameters and values:
The server url or IP Address that the IPAC device has to register with. It can be the server hostname or the IP Address
The user name for this IPAC endpoint. It is normally the extension number that must be called to reach this extension
The password for the user name entered and that has to be used to authenticate the registration of the user name with the SIP Server. When it is optional leave this field empty
Transport & Security
Allows to configure the transport and security protocols to be used to establish the connection and transport data:
SIP Server Response Codes
When in Server mode the Speaker status provide useful feedback on the server replies when the device attempts to register with it, below is an example of successful registration
More information on SIP Response codes here - Those codes are used to inform the user about connection status between the endpoint and the server.
I.e. if the code shown is the 408 - Request Timeout means: Couldn't find the user in time. The server could not produce a response within a suitable amount of time, for example, if it could not determine the location of the user in time. The client MAY repeat the request without modifications at any later time
This source type allows the device to receive an audio stream using the Real-Time Transport Protocol. RTP Playback allows any IP based audio device that is able to stream over RTP to feed audio to IPAC devices. Examples are:
BGM Distribution where a Barix Instreamer feeds one or more IPAC device(s) streaming audio to an RTP multicast address (instead of an Instreamer it is possible to use also VLC or FFMPEG to stream audio over RTP)
Barionet devices running ffmpeg to stream RTP every time a contact is closed (i.e. to stream an alarm, a pre-recorded message triggered by a switch or a panic button…)
The RTP Address where the device has to connect to in order to receive the audio stream. It supports multicast or unicast addresses.
Multicast URL scheme: rtp://<ip>:<port>
Unicast URL scheme: rtp://@:port - When using unicast the device waits for incoming audio on the specified port. The “@” symbol is used to indicate the self-IP address of the IPAC device.
The RTP playback is available in 2 modes:
Regular: plays back audio maintaining a constant delay, which is the same across multiple devices that are part of a system. This allows the possibility to keep a synchronized play-out. It should be used when playing BGM over RTP. When the RTP audio stream is received the switch to the RTP source is NOT instantaneous, it takes approximately 25 seconds before the stream starts to play. When playing back in regular mode the end to end delay is ~5 seconds.
Low Latency: plays back with the lowest possible latency. It is a mode to be used for RTP paging, or short announcements received over RTP. When the RTP audio stream is received the switch to the RTP source is instantaneous. When playing back in Low Latency mode the end to end delay is between 130 - 200ms.
RTP Payload Types supported
The following Payload types are the ones supported and compatible with IPAC devices. For more info on RTP payload types
European GSM Full Rate audio 13 kbit/s (GSM 06.10)
ITU-T G.711 PCM A-Law audio 64 kbit/s
ITU-T G.722 audio 64 kbit/s
Linear PCM - 16-bit Stereo audio 1411.2 kbit/s, uncompressed
Linear PCM - 16-bit audio 705.6 kbit/s, uncompressed
IMA ADPCM audio 88.2 kbit/s
On top of the above the device is able to decode the following stream formats:
MPEG 1 Layer 3 (MP3) @ 32 - 44.1 - 48 kHz
MPEG2 @ 16 - 22.05 - 24 kHz
The most used protocol adopted by web radios to stream music via Internet. Enabling an IPAC device to connect with a music streaming provider via HTTP(S) transforms the device into a compact and reliable music streaming player. IP Audio Client supports also HTTPS connections to guarantee a secure connection with the music streaming server.
Configuring an HTTP Source is as simple as entering the URL of the web streaming server the IPAC device has to connect to.
Supported stream playlist types
Web streaming server providing an m3u playlist containing stream URLs are supported. IPAC will parse the m3u text file and will play the URL available in the first line of the file
Web streaming server providing an pls playlist containing stream URLs are supported. IPAC will parse the m3u text file and will play the URL available in the first line of the file
When an HTTP(S) Source is playing the Speaker Status reflects the status
On an IPAC device it is possible to upload individual audio files in the Audio Files tab or to connect a USB stick containing audio files in the root folder (if the IPAC device in use offers physical USB ports). Every audio file stored in the internal memory or from a USB external memory can be triggered to play using the “Local File” source. The working principle of this source type is to configure a port number between 8000 and 8999, IPAC will listen for a precise command on that port, when received it will immediately play the audio file specified in the command.
The datagram of the message required to play the file is: FILEPLAY=fileName.xxx and it has to be sent at the <IPAC_IP>:[Configured_Port] via UDP.
Replace “fileName.xxx” with the name of the file that has to play, “xxx” is the extension format e.g. “mp3”.
Supported audio file names: "myFileName.ext" or "myFile Name.ext" - special characters are not allowed and maximum one space character in the name. Two or more spaces are not allowed. Files will fail to upload when not respecting the format expected
Supported audio files formats are: .mp3, .aac, .flac, .ac3, .dts, .wav, .ogg
When the command is sent from a script running on a third party machine double check if it’s required to add the escape character “\n” at the end of the command. E.g. when sending the command from a Barionet device running a Lua script the command written in the script has to be: FILEPLAY=fileName.xxx\n (Check the full guide here with examples on how to trigger the playback also from Windows and Linux machines: https://help.barix.com/ipformer/How-to-trigger-local-audio-files-on-IP-Speaker-via-UDP.14499846740.html)
Audio Files can be stored in the internal memory of the device or they can be played from an external USB memory storage connected to the front panel USB ports (if the IPAC device in use offers physical USB ports). The audio files page is where the user can upload files or check files present on an external USB memory.
Supported audio file names: "myFileName.ext" or "myFile Name.ext" - special characters are not allowed and maximum one space character in the name. Two or more spaces are not allowed. Files will fail to upload when not respecting the format expected.
Individual file size when uploading in the internal memory: 16MB
It is possible to upload in the internal memory .zip archives that contain multiple audio files. It’s important that each individual file does not exceed 16MB.
Supported audio files formats are: .mp3, .aac, .flac, .ac3, .dts, .wav, .ogg
This is a preview function. the audio will play on the output of the device immediately overriding anything that is playing at that moment from the priority layers
Stops the preview of the file that is playing
Select all / Select None / Delete selected
Selects all the audio files (or select individually) → Delete the selected files.
How to handle USB memories
When using external USB memories it’s possible to attach them to the USB port while the device is either powered on or off but to eject or remove a USB there is no “Eject” function available, thus is necessary to power off the IPAC device and remove the USB afterwards, this will ensure no files on the USB will be corrupted.
Remote Configuration Tool
A useful tool to manage multiple IPAC devices installed in the same network. The remote configuration tool is a server-less program. Every IPAC device runs a backend able to automatically find other IPAC devices on the network using the Avahi service and list them in this page. Avahi is built relying on mDNS and DNS-SD which takes advantage of multicast properties to advertise services on the network and enable connections between machines. IPAC devices advertise the services on the IP address: 184.108.40.206 (IPv6 ff02::fb) port 5353 (as per mDNS specifications). Below is a video introduction and explanation on the configuration tool (it refers to IP Former but the video is valid for all other IPAC devices too), where it is possible to see it in action.
The goal of the remote config tool is to facilitate and speed up the configuration of an entire system, particularly useful in case of IP Former installations, where each (IP Former) loudspeaker is an endpoint of the system and it might be easy to have tens of devices into the same installation. Thus it avoids the need to log into every single web interface to perform a configuration but access only one device to configure the entire system. On any IPAC device when opening the Remote Config tab will show:
The table is organized in columns, some of them are dynamic, meaning it is possible to open their content to change configurations (note the small arrow on the right-side of the header). Above the table, in the upper section of the screen there is an indication on the Total number of devices discovered and a search bar that can be used to filter the content of the table. By default the table visualized sorts the devices by their Zone name. A green marker around a source (the one in the RTP BGM in the screen above) indicates that the source is (or was) playing the last time the Remote Config Tool table was refreshed, the marker is not updated in real-time but after a table reload (or clicking on the READ ALL button).
This is the name used in the web interface and in the configuration tool to identify a device. By default is set to “Empty”. To change it click on the pencil tool that appears in proximity of the name cell when overlaid with the mouse. Once modified SAVE.
Change table sorting: in the Name column header there is an arrow, click on it to change the sorting using the device’s name from A -> Z to Z -> A.
It is possible to assign devices to Zones. This makes it easy to apply the same configuration only to devices that are part of the same Zone. By default this field is set to “Zone 0”, all new discovered devices are part of this default zone and can be controlled in bulk immediately.
Add a new Zone: click on the plus-circled button on the header of the zone column. This will open a dialogue window where you can check the list of the already existing zones and add a new one simply typing the name of the new zone to be added and click on Add
Rename a Zone: simple overlay with the pointer the zone name of any device part of the Zone and click on the pencil tool that appears then confirm the change by pressing the “V” confirmation button, the new name will be applied automatically to all devices belonging to that zone.
Assign devices to Zone: select the zone from the drop-down menu in correspondence of the device required, after selecting the new zone a dialogue window asks if the change has to be applied only to that device or all devices part of the same Zone. Selecting NO will only assign that device. Selecting YES will change all devices.
Remove a Zone: there is no such function in the Remote Config Tool. A zone is removed automatically when no devices are part of it. If it’s still available in the drop down is because the web page needs to be refreshed, the zone containing no devices will disappear from the list right after.
Change table sorting: in the Zone column header there is an arrow, click on it to change the sorting from A -> Z to Z -> A.
This is a dynamic column. Click on the arrow in proximity of the Settings header to open the device's settings configuration
For each device it is possible to (from left to right):
These are the same Settings available in the Settings page of each IPAC device. For more help topics on each field refer to the help section of the Settings page. When settings are changed it is important to SAVE them with the corresponding buttons in the device control section or using the SAVE ALL button available in the top right corner of the page.
These are 5 dynamic columns reflecting the priority layers also available in the source tab. Click on the arrow in proximity of the header to expand the desired priority layer and configure the source, the parameters and values available are the same as the ones available for each source described in previous chapters. below is an example of InformaCast source expanded:
Every priority layer will allow the user to:
This column simply visualizes the number of audio files uploaded and stored. Visit the Audio Files section (or Local File source chapter) for more information on how to handle audio files playback
This is an expandable column that opens up the details of the IPAC devices: MAC Addresses, HW Type, FW Version installed, System Time, Up TIme (since how long the device is powered), License (if the device contain any valid license, i.e. Informacast).
From left to right:
Copy / Insert
COPY / INSERT: copies the whole configuration of a device to other devices. When clicking on copy on one device, all copy buttons of the other devices will transform in an INSERT button. Click on as many INSERT as needed to apply the same settings of the COPIED device on the desired devices. The Copy function will allow you to create custom installations where devices part of the same zone might have different configurations. Copy / Insert will only affect Sources configuration and not the settings.
The Copy / Insert function requires to click on SAVE ALL in the top right corner of the page to apply the new configuration to the affected device(s)
This function pushes the configuration of one device to all other OR to devices part of the same zone. A dialogue shows up after clicking the button allowing the user to decide. The “push” function is what actually speeds up large system configurations. After setting up one device it is possible to copy its configuration to all others in 2 clicks.
Unlike the Copy / Insert function the configuration that will be replicated includes also the settings: Master Volume, Sonic IP, HTTPS enable/disable plus all priority layer configurations. On top of this the new configuration is automatically saved and applied to the devices
Reboots all the devices discovered at once. It opens a dialogue asking for confirmation before proceeding.
The Read All button is used to parse the configuration of all IPAC devices in the network and refresh the table. If there are some pending changes not yet saved the user is warned as they must be either canceled or applied (saved) before refresh the table.
When a new source configuration is applied, IPAC might take some seconds while restarting the services required to advertise itself and be identified by the remote config tool, in those occasions if the number of devices discovered is not the one expected, click on Read All so that the number is updated.
Saves any modification made in ALL the devices discovered. If no modifications are done, there is no operation performed and the user is informed.
Cancels any modification performed in any device in the list and restores the initial condition
The Speaker Status page is the main dashboard of the IP Audio Client application. The window is quite essential , it displays the current playback status with the source arranged from top to bottom reflecting the priority layers. A green marker colors the currently playing source.
Each source contains the information related to the source itself and they change according to the status of the single source. A thorough description on how the speaker status changes for each source is given in the source chapter of this guide.
The Play count is a counter that shows the number of times the corresponding source played. The counters are reset every time a change in the source configuration is applied or after a reboot.
The actual IPAC device hardware (in parenthesis is the Part Number)
The Barix IPAM codec module installed in the device (in parenthesis the ID of this component)
Media Access Control address - This is the hardware address of the Ethernet interface of the device
Linux kernel version
The version of the Linux operating system in use
The bootloader version currently in use
Shows if the device is connected via the Ethernet interface to the network
The current IP address of the Ethernet interface
The subnet mask on which the device is operating
The gateway address currently set
The DNS server addresses (primary and secondary) currently in use. Provided either by the DHCP or entered manually in the settings page
The device's current local time
How long the device is powered on
The name of the base license for the IPAC device
Either if the license is active or expired
The date when the license was issued
The date when the license will expire
The license unique identifier
If this license has any additional features (e.g. InformaCast)
Either if the license that is running on the image is valid or invalid (in such case the application wont run)
Shows up only if there is any USB external memory connected to the IPAC device providing the details of the same
*Only available on IPAC devices with temperature sensor implemented in the amplifier (e.g. IP Former TPA400)
Shows the current temperature of the amplifier. It updates at every page reload.
*Only available on ceratain IPAC devices with automatic gain amplifier adjustment depending on the power available and impedance measurement feature (e.g. Exstreamer MPA400)
The power source detected to power the IPAC device (PoE, PoE+, PoE++, 4PPoE or External Power Supply)
The speaker load detected connected to the IPAC device’s terminals
The amplifier output voltage (Vpp) capability
The Logs page displays the events occurring operation of the IPAC device. Logs are useful for debugging issues, they give a detailed insight into every process within the OS. On the top-right corner, it is possible to click the button “Download all messages” to download all log files.
When contacting the Barix support it is useful to attach along with the communication the Log files downloaded and the status page screenshot. Do not forget to give a description as much detailed as possible about the steps made that led to the issue.
Reset to factory defaults - Soft reset
The defaults page allows performing a soft-reset. Such operation reverts all settings except the network settings back to factory defaults (it doesn't perform a firmware downgrade, just a reset of the settings for the running application). The reset to factory defaults can be enabled or disabled from the settings page, under "Security Settings".
Reset to factory defaults – Hard reset
It is also possible to perform a hard reset. A hard reset will revert all settings to factory defaults including the network settings.
To perform a hard reset locate the reset button on the front panel of the IPAC device and keep it pressed for approximately 10 seconds using a sharp-pointed tool while the device is powered. The status led will blink green 3 times, informing that the reset operation is started. After a few seconds, the device will reboot with factory defaults. Reload the page after the operation is completed.
Rescue Image Process
In some occasions it is possible that the application faces some issues that cannot be restored with a hard reset to default. In this situation a rescue image process might solve:
If your IPAC device is powered, shut it off
Make sure the device is connected to internet. For this process to work the device will attempt a connection to Barix Download server via HTTP (port 80), if successful it will download the rescue image from this server
While the device is off, press the reset button
Keep the button pressed while powering up the device
Keep the button pressed in for 34 seconds after the device is powered, then release
When the rescue process starts the led blinks orange
The device restarts and the LED will blink orange indicating a FW update/downgrade process is in progress
When the LED will turn green (blinking or steady), reboot the device
After this process the device will run the firmware image fetched from the download server, which normally corresponds to the last one released.
IP Audio Client offers the possibility to update the firmware of the device from this page.
Run always the latest firmware available from Barix as it might include bug fixes, improvements or new useful features. Check the latest firmware available on Barix Website.
In the same page it is possible to visualize the current firmware version running.
Update the firmware
In the Update page click on “Please click here to start the update”, the system update page is accessed
Click on “Choose File”, locate and select the corresponding TAR archive just downloaded
Click on “Upload”, a processing bar will show up indicating the upload process completion. Wait until the process is finished (don't disconnect power supply during this operation)
Once the upload is complete the device will reboot automatically. Wait ~2 mins and reload the page or click the home link to go back to the home page. If necessary, after the update perform a hard reset of your browser to empty the cache and hard reload. (How to empty cache and hard reload)
The reboot is the process of power cycling the device (ON → OFF → ON). It’s a complete power cycle. The reboot can be performed from the web user interface or from the reset button located on the front panel of the device.
Reboot - web interface
Click "Reboot the device" to restart the device. While restarting a screen showing a countdown of 10 seconds appears. At the end of the countdown. Wait approximately 20 seconds and then reload the web page or click on the text shown “click here to return to the home page”.
Reboot - button
The reboot of the device from the button is performed by pressing the Reset button located on the front panel of the IPAC device for ~3 seconds.
A long press of this button (10 seconds) will reset the device to factory defaults.
Compliance and further Information
This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
Reorient or relocate the receiving antenna.
Increase the separation between the equipment and receiver.
Connect the device into an outlet on a circuit different from that to which the receiver is connected.
Consult the dealer or an experienced radio/TV technician for help.
Safety and precaution recommendations apply. Find them in the download section at www.barix.com
Find your distributor on this list for more hardware.
For questions that are extending the documentation, feel free to contact us on: