Barix Wiki - User contributions [en]

Broadcast

2010-11-18T04:14:30Z

Yhorebapemy:

>== Broadcast ==

=== What is Broadcast ? ===
Broadcast is a method used on IP (and other) Networks to distribute a data block on the network to '''every''' connected device. Of course, a device may want to not process the block, it may have no application listening to the port the block is sent to, or it may be switched off - but generally, broadcasts are received by '''all''' hosts on the network

=== How does Broadcast differ from Multicast ? ===
[[Multicast]] is a "group specific" broadcast. Using special Addresses, a Multicast is *not* received by all host on the network, but only by those who are explicitely asking for it. Details in the [[Multicast]] article on this wiki.

=== What is the Broadcast address ? ===
To address a block to a device on the network, it either needs to be sent to the IP Address of the device, or sent as broadcast. For the broadcast, a specific IP Address is used, which is determined by setting all "host" bits in the IP address to "1", and using the same "network" part. For details on this, please check [[IP Address]] on this wiki.
To determine the correct broadcast address, the correct netmask is '''crucial'''. With a wrong netmask, the calculated broadcast address will not match the network and is either sent as a direct block to one host or eventually considered to be on another network (and ignored by all hosts). Here is an example of how a broadcast address is determined:
192.168.001.010 - IP Address of the sender
255.255.255.000 - Netmask
000.000.000.255 - all host bits to one
192.168.001.255 - calculated correct broadcast address

=== Can I send a Broadcast to another network ?
Generally, NO - a Broadcast is a function on a local network. Routers will generally not forward the broadcasts. Depending on the system configuration and routers used, there may be ONE special exception: the "global" broadcast address, which will be addressing all IP networks on the same lan. It is also used for applications such as getting an IP address by DHCP (when the network is not yet known). The global broadcast address is 255.255.255.255
However, do NOT expect a router to forward global broadcasts unless it is capable and configured to do so !

=== How can I send a block to a group of remote devices, then ? ===
Well ... Barix devices eventually (depending on firmware version and type) provide a "rebroadcasting" feature. IP Blocks sent to the device (for example, from a remote source), may be rebroadcasted on the local LAN by the network. This is exstreamely helpful to address many devices concurrently in a remote network without multiplying the packets to all destinations and clogging the links.

Back to [[FAQ]]

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://emyrejivim.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
----
=[http://emyrejivim.co.cc CLICK HERE]=
----
</div>

Product Matrix

2010-11-17T23:56:16Z

Yhorebapemy:

>=Barix Audio Product Matrix=
Barix audio products are a combination of HW capabilities versus SW functionalities. Almost any SW version can be loaded on any HW device. The attached tables help you to find out which combination best fits your requirements. First look at what HW device provides the right capabilities and then look at what SW version enables the required features.
 
==Hardware Features==
{|

! width="100" bgcolor="#C22" align="center" style="color:#FFF;"| Audio Codec
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 100
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 110
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 120
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 200
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex P5
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 500
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 1000
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| In 100
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 100
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 155
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 200
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 1000
|-
! bgcolor="#EEE" | Audio module
| bgcolor="#EEE" align="center" | IPAM 300
| bgcolor="#EEE" align="center" | IPAM 300
| bgcolor="#EEE" align="center" | IPAM 300
| bgcolor="#EEE" align="center" | IPAM 300
| bgcolor="#EEE" align="center" | IPAM 300
| bgcolor="#EEE" align="center" | IPAM 100
| bgcolor="#EEE" align="center" | IPAM 100
| bgcolor="#EEE" align="center" | IPAM 100
| bgcolor="#EEE" align="center" | IPAM 100
| bgcolor="#EEE" align="center" | IPAM 100
| bgcolor="#EEE" align="center" | IPAM 100
| bgcolor="#EEE" align="center" | IPAM 100
|-
! PCM/G711
| align="center" | dec
| align="center" | dec
| align="center" | dec
| align="center" | dec
| align="center" | dec
| align="center" | dec & enc
| align="center" | dec & enc
| align="center" | dec & enc
| align="center" | dec & enc
| align="center" | dec & enc
| align="center" | dec & enc
| align="center" | dec & enc
|-
! bgcolor="#EEE" | MPEG
| bgcolor="#EEE" align="center" | dec
| bgcolor="#EEE" align="center" | dec
| bgcolor="#EEE" align="center" | dec
| bgcolor="#EEE" align="center" | dec
| bgcolor="#EEE" align="center" | dec
| bgcolor="#EEE" align="center" | dec & enc
| bgcolor="#EEE" align="center" | dec & enc
| bgcolor="#EEE" align="center" | dec & enc
| bgcolor="#EEE" align="center" | dec & enc
| bgcolor="#EEE" align="center" | dec & enc
| bgcolor="#EEE" align="center" | dec & enc
| bgcolor="#EEE" align="center" | dec & enc
|-
! AAC
| align="center" | dec
| align="center" | dec
| align="center" | dec
| align="center" | dec
| align="center" | dec
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" |
|-
! bgcolor="#EEE" | WMA
| bgcolor="#EEE" align="center" | dec
| bgcolor="#EEE" align="center" | dec
| bgcolor="#EEE" align="center" | dec
| bgcolor="#EEE" align="center" | dec
| bgcolor="#EEE" align="center" | dec
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
|-
| colspan="13" | &nbsp;"dec"'' stands for decoding, ''"enc"'' for encoding''
|-
! width="100" bgcolor="#C22" align="center" style="color:#FFF;"| Audio Interfaces
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 100
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 110
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 120
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 200
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex P5
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 500
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 1000
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| In 100
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 100
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 155
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 200
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 1000
|-
! bgcolor="#EEE" | Microphone In (& Bias)
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | unbalanced
| bgcolor="#EEE" align="center" | balanced
| bgcolor="#EEE" align="center" | unbalanced
| bgcolor="#EEE" align="center" | balanced
|-
! Microphone Type
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" | electret, coil
| align="center" | electret
| align="center" | electret, coil
| align="center" | electret, coil
|-
! bgcolor="#EEE" | Mic Bias DC
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | 2.7 V
| bgcolor="#EEE" align="center" | 3.4 V
| bgcolor="#EEE" align="center" | 2.7
| bgcolor="#EEE" align="center" | 12 V sel
|-
! Analog Input
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" | stereo bal.
| align="center" | stereo bal.
| align="center" | stereo unb.
| align="center" | mono unb.
| align="center" | mono unb.
| align="center" | mono unb.
| align="center" | stereo bal.
|-
! bgcolor="#EEE" | Analog Output
| bgcolor="#EEE" align="center" | stereo unb.
| bgcolor="#EEE" align="center" | stereo unb.
| bgcolor="#EEE" align="center" | stereo unb.
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | stereo bal.
| bgcolor="#EEE" align="center" | stereo bal.
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | mono unb.
| bgcolor="#EEE" align="center" | mono bal.
| bgcolor="#EEE" align="center" | mono unb.
| bgcolor="#EEE" align="center" | stereo bal.
|-
! Headphone Output
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" |
| align="center" |
| align="center" |
| align="center" | &#10004;
| align="center" |
| align="center" |
| align="center" |
| align="center" |
|-
! bgcolor="#EEE" | Speaker Output
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | 2 x 25W
| bgcolor="#EEE" align="center" | 1 x 5W
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | 1 x 2W
| bgcolor="#EEE" align="center" | 1 x 5W sup
| bgcolor="#EEE" align="center" | 1 x 8W
| bgcolor="#EEE" align="center" |
|-
! S/P DIF Input
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" | opt. & coax
| align="center" |
| align="center" |
| align="center" |
| align="center" |
|-
! bgcolor="#EEE" | S/P DIF Output
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | optical
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
|-
! AES/EBU Interface
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" | in & out
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" |
|-
! bgcolor="#EEE" | Aiphone SUB I/F
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" |
|-
| colspan="13" | &nbsp;"unb."'' stands for unbalanced, ''"bal."'' for balanced,''"sel" ''for selectable: either electret bias with current supervision or coil (no bias) with impedance test,'' "sup"'' for speaker supervision, ''
|-
! width="100" bgcolor="#C22" align="center" style="color:#FFF;"| Other Interfaces
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 100
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 110
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 120
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 200
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex P5
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 500
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 1000
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| In 100
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 100
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 155
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 200
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 1000
|-
! bgcolor="#EEE" | Ethernet
| bgcolor="#EEE" align="center" | 1 x RJ45
| bgcolor="#EEE" align="center" | 1 x RJ45
| bgcolor="#EEE" align="center" | 1 x RJ45
| bgcolor="#EEE" align="center" | 1 x RJ45
| bgcolor="#EEE" align="center" | 1 x RJ45
| bgcolor="#EEE" align="center" | 1 x RJ45
| bgcolor="#EEE" align="center" | 1 x RJ45
| bgcolor="#EEE" align="center" | 1 x RJ45
| bgcolor="#EEE" align="center" | 1 x RJ45
| bgcolor="#EEE" align="center" | 2 x RJ45
| bgcolor="#EEE" align="center" | 1 x RJ45
| bgcolor="#EEE" align="center" | 2 x RJ45
|-
! RS-232
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" |
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" |
| align="center" | &#10004;
| align="center" | &#10004;
|-
! bgcolor="#EEE" | RS-485
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
|-
! Infared receiver
| align="center" | ext
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | ext
| align="center" | ext
| align="center" | ext
| align="center" | ext
| align="center" | ext
| align="center" | ext
| align="center" | ext
| align="center" | ext
|-
! bgcolor="#EEE" | Infared output
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
|-
! Dry Contact Input
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" | 4
| align="center" | 4
| align="center" |
| align="center" | 2
| align="center" | 2 sup
| align="center" | 2
| align="center" | 8 sup
|-
! bgcolor="#EEE" | Relay Output
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | 1 NO
| bgcolor="#EEE" align="center" | 1 NO
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | 4 NO
| bgcolor="#EEE" align="center" | 4 NO
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | 1 NO
| bgcolor="#EEE" align="center" | 1 LED
| bgcolor="#EEE" align="center" | 1 NO
| bgcolor="#EEE" align="center" | 8 NO, 1 NC
|-
! Flash Memory Interface
| align="center" | USB
| align="center" | USB
| align="center" | microSD
| align="center" | USB
| align="center" |
| align="center" | USB
| align="center" | USB
| align="center" |
| align="center" | USB
| align="center" |
| align="center" | USB
| align="center" |
|-
! bgcolor="#EEE" | LCD Display
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
|-
! Status LEDs
| align="center" | &#10004;
| align="center" |
| align="center" |
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
|-
! bgcolor="#EEE" | I/O LEDs
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | 4
| bgcolor="#EEE" align="center" | 4
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | 8
|-
| colspan="13" | &nbsp;"ext"'' stands for external accessory IR Kit or VSC (Volume Source Control),'' "sup"'' for input supervision, ''"NO"'' for Normally Open contacts,'' "NC"'' for Normally Closed contacts, ''"LED"'' for LED driver instead of relay, ''
|-
! width="100" bgcolor="#C22" align="center" style="color:#FFF;"| Power Supply
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 100
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 110
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 120
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 200
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex P5
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 500
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 1000
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| In 100
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 100
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 155
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 200
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 1000
|-
! bgcolor="#EEE" | DC Voltage range
| bgcolor="#EEE" align="center" | 9..30 V
| bgcolor="#EEE" align="center" | 9..30 V
| bgcolor="#EEE" align="center" | 9..30 V
| bgcolor="#EEE" align="center" | 24 V
| bgcolor="#EEE" align="center" | 48 V
| bgcolor="#EEE" align="center" | 24..48 V
| bgcolor="#EEE" align="center" | 24..48 V
| bgcolor="#EEE" align="center" | 9..30 V
| bgcolor="#EEE" align="center" | 9..30 V
| bgcolor="#EEE" align="center" | 24..48 V
| bgcolor="#EEE" align="center" | 16..30 V, 48V
| bgcolor="#EEE" align="center" | 2 x sup 24..48 V
|-
! AC Voltage range
| align="center" | 12..24 V
| align="center" | 12..24 V
| align="center" | 12..24 V
| align="center" |
| align="center" |
| align="center" |
| align="center" |
| align="center" | 12..24 V
| align="center" | 12..24 V
| align="center" |
| align="center" | 16..24 V
| align="center" |
|-
! bgcolor="#EEE" | PoE 802.3af
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" |
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" |
|-
| colspan="13" | &nbsp;"sup" ''stands for voltage supervision''
|}
----
 
==Device's Software Support Overview==
{|

! width="100" |
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 100
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 110
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 120
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 200
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex P5
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 500
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ex 1000
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| In 100
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 100
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 155
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 200
! width="60" bgcolor="#C22" align="center" style="color:#FFF;"| Ann 1000
|-
! bgcolor="#EEE" | Audio module
| bgcolor="#EEE" align="center" | IPAM 300
| bgcolor="#EEE" align="center" | IPAM 300
| bgcolor="#EEE" align="center" | IPAM 300
| bgcolor="#EEE" align="center" | IPAM 300
| bgcolor="#EEE" align="center" | IPAM 300
| bgcolor="#EEE" align="center" | IPAM 100
| bgcolor="#EEE" align="center" | IPAM 100
| bgcolor="#EEE" align="center" | IPAM 100
| bgcolor="#EEE" align="center" | IPAM 100
| bgcolor="#EEE" align="center" | IPAM 100
| bgcolor="#EEE" align="center" | IPAM 100
| bgcolor="#EEE" align="center" | IPAM 100
|-
! Exstreamer FW
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | -
| align="center" | -
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
|-
! bgcolor="#EEE" | Streaming Client
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
|-
! Instreamer FW
| align="center" | -
| align="center" | -
| align="center" | -
| align="center" | -
| align="center" | -
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
|-
! bgcolor="#EEE" | Annuncicom FW
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
|-
! ABCL annunfdx
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
|-
! bgcolor="#EEE" | ABCL rtp stl
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
|}
----
 
==Software Features Overview==
{|

! width="120" bgcolor="#C22" align="center" style="color:#FFF;"| SW Package
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Exstreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Streaming Client FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Instreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annuncicom FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annfdx ABCL
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| RTP STL ABCL
|-
! bgcolor="#EEE" | Version
| bgcolor="#EEE" align="center" | 8.31
| bgcolor="#EEE" align="center" | 2.18
| bgcolor="#EEE" align="center" | 3.16
| bgcolor="#EEE" align="center" | 3.07
| bgcolor="#EEE" align="center" | 0.22 [1]
| bgcolor="#EEE" align="center" | 2.05
|-
| colspan="13" | &nbsp;[1]'' the Annfdx BCL application is included in the ABCL Dev Kit V0.34''
|-
! width="125" bgcolor="#C22" align="center" style="color:#FFF;"| WEB Tabs & Pages
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Exstreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Streaming Client FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Instreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annuncicom FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annfdx ABCL
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| RTP STL ABCL
|-
! Home with I/O status & control
| align="center" | &#10004;
| align="center" | -
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | -
| align="center" | &#10004;
|-
! bgcolor="#EEE" | Settings
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
|-
! Defaults
| align="center" | &#10004;
| align="center" | -
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
|-
! bgcolor="#EEE" | Status
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
|-
! Reboot
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
|-
! bgcolor="#EEE" | Update (Bootloader)
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
|-
! /status info page
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
|-
! bgcolor="#EEE" | Ethersound
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
|-
! width="125" bgcolor="#C22" align="center" style="color:#FFF;"| Network Config
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Exstreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Streaming Client FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Instreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annuncicom FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annfdx ABCL
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| RTP STL ABCL
|-
! IP address/DHCP
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
|-
! bgcolor="#EEE" | DHCP Host Name
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
|-
! Sonic IP
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
|-
! width="125" bgcolor="#C22" align="center" style="color:#FFF;"| Streaming Config
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Exstreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Streaming Client FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Instreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annuncicom FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annfdx ABCL
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| RTP STL ABCL
|-
! Send Mode (Always, on Talk ...)
| align="center" | -
| align="center" | -
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
|-
! bgcolor="#EEE" | Trigger Level/Time
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
|-
! Stream Control/Strategy
| align="center" | -
| align="center" | -
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | -
| align="center" | -
|-
! bgcolor="#EEE" | Destination Table
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
|-
! Multicast
| align="center" | -
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | -
| align="center" | &#10004;
| align="center" | &#10004;
|-
! bgcolor="#EEE" | Tx Audio Port
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
|-
! Source Address / Port / Path
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | -
| align="center" | -
| align="center" | &#10004;
| align="center" | &#10004;
|-
! bgcolor="#EEE" | Receive Buffer
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
|-
! Receive control/strategy
| align="center" | &#10004;
| align="center" | -
| align="center" | -
| align="center" | &#10004;
| align="center" | -
| align="center" | -
|-
! bgcolor="#EEE" | Rx Priority Port
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
|-
! Rx Audio Port
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | -
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
|-
! width="125" bgcolor="#C22" align="center" style="color:#FFF;"| MP3 Stream
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Exstreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Streaming Client FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Instreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annuncicom FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annfdx ABCL
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| RTP STL ABCL
|-
! Raw UDP
| align="center" | &#10004;
| align="center" | -
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | -
|-
! bgcolor="#EEE" | RTP
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
|-
! BRTP
| align="center" | -
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | -
| align="center" | -
| align="center" | &#10004;
|-
! bgcolor="#EEE" | TCP
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
|-
! HTTP
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | -
| align="center" | -
|-
! bgcolor="#EEE" | Shoutcast
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
|-
! Icecast
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | -
| align="center" | -
| align="center" | -
|-
! bgcolor="#EEE" | zServer
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
|-
! USB file
| align="center" | -
| align="center" | &#10004;
| align="center" | -
| align="center" | -
| align="center" | -
| align="center" | -
|-
! width="125" bgcolor="#C22" align="center" style="color:#FFF;"| PCM/G711 Stream
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Exstreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Streaming Client FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Instreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annuncicom FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annfdx ABCL
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| RTP STL ABCL
|-
! Raw UDP
| align="center" | -
| align="center" | -
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | -
|-
! bgcolor="#EEE" | RTP
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
|-
! BRTP
| align="center" | -
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | -
| align="center" | -
| align="center" | &#10004;
|-
! bgcolor="#EEE" | TCP
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
|-
! width="125" bgcolor="#C22" align="center" style="color:#FFF;"| AAC+ Stream
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Exstreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Streaming Client FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Instreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annuncicom FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annfdx ABCL
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| RTP STL ABCL
|-
! HTTP/Shoutcast
| align="center" | -
| align="center" | &#10004;
| align="center" | -
| align="center" | -
| align="center" | -
| align="center" | -
|-
! bgcolor="#EEE" | USB file
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
|-
! width="125" bgcolor="#C22" align="center" style="color:#FFF;"| WMA Stream
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Exstreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Streaming Client FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Instreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annuncicom FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annfdx ABCL
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| RTP STL ABCL
|-
! MMS HTTP/TCP
| align="center" | -
| align="center" | V1.5x only
| align="center" | -
| align="center" | -
| align="center" | -
| align="center" | -
|-
! bgcolor="#EEE" | USB file
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
|-
! width="125" bgcolor="#C22" align="center" style="color:#FFF;"| Audio Interface
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Exstreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Streaming Client FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Instreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annuncicom FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annfdx ABCL
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| RTP STL ABCL
|-
! Mic In
| align="center" | -
| align="center" | -
| align="center" | -
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | -
|-
! bgcolor="#EEE" | Analog Line In
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
|-
! Digital Line In
| align="center" | -
| align="center" | -
| align="center" | &#10004;
| align="center" | -
| align="center" | -
| align="center" | &#10004;
|-
! bgcolor="#EEE" | Aiphone In/Out
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
|-
! width="125" bgcolor="#C22" align="center" style="color:#FFF;"| Other Interfaces
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Exstreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Streaming Client FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Instreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annuncicom FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annfdx ABCL
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| RTP STL ABCL
|-
! RS-232 Gateway
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
|-
! bgcolor="#EEE" | RS-485 Gateway
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
|-
! IR Gateway
| align="center" | &#10004;
| align="center" | -
| align="center" | &#10004;
| align="center" | -
| align="center" | -
| align="center" | -
|-
! bgcolor="#EEE" | Contact Input Control
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | 4
| bgcolor="#EEE" align="center" | 2
| bgcolor="#EEE" align="center" | 2
| bgcolor="#EEE" align="center" | 4
|-
! Relay Output Control
| align="center" | -
| align="center" | 4
| align="center" | -
| align="center" | 1
| align="center" | 1
| align="center" | 4
|-
! bgcolor="#EEE" | CTS as Input
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
|-
! RTS as Output
| align="center" | &#10004;
| align="center" | -
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | -
| align="center" | -
|-
! bgcolor="#EEE" | Display Driver
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
|-
! width="125" bgcolor="#C22" align="center" style="color:#FFF;"| Control API
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Exstreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Streaming Client FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Instreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annuncicom FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annfdx ABCL
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| RTP STL ABCL
|-
! IR control
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | -
| align="center" | -
| align="center" | -
| align="center" | -
|-
! bgcolor="#EEE" | WEB cgi
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
|-
! Serial port
| align="center" | &#10004;
| align="center" | -
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | -
| align="center" | -
|-
! bgcolor="#EEE" | TCP/UDP port
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
|-
! width="125" bgcolor="#C22" align="center" style="color:#FFF;"| Device Management
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Exstreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Streaming Client FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Instreamer FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annuncicom FW
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| Annfdx ABCL
! width="110" bgcolor="#C22" align="center" style="color:#FFF;"| RTP STL ABCL
|-
! SNMP MIB
| align="center" | -
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
|-
! bgcolor="#EEE" | SNMP traps
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
|-
! MTELL/Barimon
| align="center" | -
| align="center" | &#10004;
| align="center" | -
| align="center" | -
| align="center" | -
| align="center" | -
|-
! bgcolor="#EEE" | Remote Update
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | &#10004;
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
| bgcolor="#EEE" align="center" | -
|-
! Security
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
| align="center" | &#10004;
|}
----

Back to [[Main Page]]

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ivejixok.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
----
=[http://ivejixok.co.cc CLICK HERE]=
----
</div>

Instreamer 100

2010-11-17T23:54:59Z

Yhorebapemy:

>[[Image:Instreamer100_FrontPlate_Web200.gif|right]]
[[Image:Instreamer100_RearPlate_Web200.gif|right]]

Converts any analog or digital audio source, including tuners and CD players, into high-quality VBR MPEG1 and MPEG2 streams (stereo mode). G.711 and PCM as well (mono mode). The audio is encoded in real-time, and the generated audio stream can be distributed, via an IP-based network or the Internet, to one or more receivers or Shoutcast/Icecast-servers.

Barix Instreamer 100 can be easily managed via a web browser interface using PCs, web pads, PDAs or other web-enabled devices. With serial and Ethernet control APIs, open IP-standards, and the MP3 format, the device can also be integrated with other components.

Connecting the Barix Instreamer 100 to audio equipment is made simple by offering stereo RCA analog inputs as well as optical S/PDIF and coax digital inputs.

More information available in our website:
http://www.barix.com/downloads/Instreamer_Family/81/

Back to [[Main Page#Products]]

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ahowulumus.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
----
=[http://ahowulumus.co.cc CLICK HERE]=
----
</div>

Control commands

2010-11-17T23:54:49Z

Yhorebapemy:

>= Control Commands =

* [[Modbus]]

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://asifetyr.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
----
=[http://asifetyr.co.cc CLICK HERE]=
----
</div>

X8-Update

2010-11-17T23:54:26Z

Yhorebapemy:

>== X8 Update procedure ==

This page describes how to update the firwmare of a Barix X8 module

=== prerequisites ===
You need to have the following available:
* PC with a serial port and a terminal program such as hyperterm
* Serial cross cable (DB9 femaleto DB9 female)
* Barionet with recent software version (min. 2.13 recommended)
* mbt_vxx application (currently available on the Barionet yahoo group in the files section), loaded in WEB4
* Power supply (min. 9V, max. 30V, to supply both Barionet and X8, min. 300mA)
* necessary wires to connect X8

=== hardware setup ===

* Connect the PC to the serial port of the Barionet with the cross cable

* Wire the X8 with the Barionet and power supply as following:

{|border="1" cellpadding="5" cellspacing="0"
|-
|'''Signal'''
|'''Barionet'''
|'''X8'''
|-
|RS485 B
|J7 pin 5
|J3 pin 3
|-
|RS485 A
|J7 pin 4
|J3 pin 2
|-
|Power +
|J6 pin 15
|J3 pin 1*
|-
|Power -
|J6 pin 16
|J3 pin 2*
|}

(*) the X8 has a built in bridge rectifier, so polarity of the power connection is unimportant.

=== procedure ===

1) Reset the Barionet. You should see the prompt of the MBT application. If you select "2" - service, you get
into the modbus testing/exercising menu. note that the software will automatically set the serial parameters to 19200,e,8,1
and if a change is needed, it will automatically reboot/restart.

2) check if the connected X8 is working, for example, with a "read command":
R0,256,4<CR>

Answer (example): READ: 00B2 0005 0005 0001

this shows 8 bytes from the eeprom of the X8, being type, firmware version (5) , serial number 1 (5) & 2 (1). The device will respond independent of its modbus address as this is a read to the "broadcast" address. ** note ** the numbers displayed are in hexadecimal notation. A serial number of an X8 such as 10-31 would be displayed as 000A 001F !

3) send the "firmware erase" command to the X8 - it needs the serial number of the X8 as two decimal numbers as parameter as a security feature. For example, X8 with serial number 5-001 needs the following command
F5,1<CR>

4) the X8 will turn three of the four visible LEDs on, and after about 6 seconds 2 will stay iluminated.

...you can repeat this now for as many X8 as you wish. The X8 devices will be "erased" after this procedure. And new software will be loaded in the next step.

5) enter "X" command to leave the service mode, then select "3" for the firmware loader

6) the barionet will reconfigure the serial port, restart. Select "3" again for the load app (or wait it will be entered automatically).

7) if the X8 is still connected (and erased), press "S" to send the firmware to the X8. Otherwise, any X8 connected will start loading automatically after approx. 6 seconds.

8) after about 20 seconds, the firmware load is complete and the X8 will start blinking with one LED. power off/on the X8, it may still blink with the middle LED, repower again. The X8 now will blink only with one corner LED, all others will be off. The device has been loaded with the firmware and is operative.

Back to [[FAQ]]

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ehivemit.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
----
=[http://ehivemit.co.cc CLICK HERE]=
----
</div>

SIP Paging

2010-11-17T23:53:33Z

Yhorebapemy:

>== SIP Paging applications with Barix devices ==

Barix IP Audio devices are ideal products to extend a SIP based phone system (PBX) such as Cisco Callmanager, Asterisk or OpenSER with paging functionalities. 
 
All Barix Exstreamer and Annuncicom devices can be loaded with the SIP firmware (which is a free download from the website). Once this firmware is loaded, the devices provide a functionality similar to a specialized phone.
 

For paging applications, an Exstreamer (output only) device suffices. 
The device can be programmed to auto-answer an incoming phone call, activate a relay with call reception (to activate a paging amplifier, for example), and output the call audio received through its analog output. Depending on the device, you have a choice of line level, 600Ohm balanced or even 2W, 8W or 2x25W amplified output, suitable to directly drive overhead speakers.
Some device models (Exstreamer 110/120/500, Annuncicom 100,200,1000) provide at least one contact closure output (relay). 
These contact closure outputs (up to 8 with the Annuncicom 1000) can be used for zone control, assuming that the SIP Paging gateway (Barix device with SIP firmware loaded) is connected to a traditional paging amplifier, which has inputs with which zones can be selected.
Details on how (as an example) an Asterisk PBX is configured to drive the Zone Control relays on an Annuncicom 1000 are in this wiki article: [[Asterix_Server_configuration_for_Relay_control]] 
 
Other PBX systems should work similar, and you can always control the relays even in-call by issuing certain commands to the device (common speak, you would say via DTMF, technically, button presses are typically delivered using SIP INfo or RFC 2833 encapsulation). Details are, again, in the article referred to above.

So .. Barix devices are ideal SIP Paging and Intercom devices, useable in a vast range of applications.

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://yxakowu.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
----
=[http://yxakowu.co.cc CLICK HERE]=
----
</div>

Configuration Update

2010-11-17T23:53:28Z

Yhorebapemy:

>=Configuration Update=
The current configuration is stored in a non-volatile memory (EEPROM). The memory layout depends on the specific Firmware. If you updated the device with a new Firmware make sure to apply the “factory defaults configuration”. If you update the device with a different type of a firmware (e.g. load ABCL over the Exstreamer) make sure that you do the serial update. The current configuration can be changed via the web user interface. When hit the “Apply” button the new values are stored into the EEPROM.

==Factory defaults using Serial Rescue ==
The EEPROM is overwritten during a Serial Rescue by the factory defaults configuration using the binary file config.bin which is located in the folder “update_rescue” of the delivered Firmware Update Kit. This file can be edited with a hex editor. Consult the “configuration memory usage” table carefully before you make any changes.

==Factory defaults using Web Update==
The “factory defaults configuration” (config.bin) is also contained in the application image which is loaded into the flash memory. When applying the “Web Update” make sure to apply the “factory defaults configuration” by pushing the reset button for more than 10 seconds.

==Common Gateway Interface (CGI)==
The current configuration can also be changed using the CGI API embedded in every Barix device. This can be helpful when controlling Barix devices via automated scripts. The ''setup.cgi'' interface allows to set new configuration values over HTTP for every parameter available on the WEB user interface of the device.

There are two methods of sending the configuration over HTTP: GET and POST. The method used depends on the type of the firmware. The GET method is more common, however newer versions of certain firmware use the POST method (e.g. Streaming Client version >=2.02). Check your firmware's technical manual for more details.

Sending the configuration from a PC is easy but the detailed usage may depend on the tool and version used on the PC server side. An example using ''GNU Wget ver.1.11.4'' with the POST method follows:

On a device (IP 192.168.2.66) running the Streaming Client Firmware we want to set the SNMP server IP address to 192.168.2.111
wget "--post-data=B686=192&B687=168&B688=2&B689=111&" http://192.168.2.66/setup.cgi
The variable's name (e.g. B686) can be found looking in html source of the device WEB UI or in Technical Documentation of the specific Firmware.

Example of the GET method: On a device (IP 192.168.2.67) running the ABCL Firmware we want to disable the Sonic IP
wget "http://192.168.2.67/setup.cgi?B198b7=1"

== [[Default Configuration Customization]] ==

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ityjykuwap.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
----
=[http://ityjykuwap.co.cc CLICK HERE]=
----
</div>

Alarm Applications

2010-11-17T23:53:17Z

Yhorebapemy:

<big>'''Barix products in Alarm Applications'''</big>

Barix products can be used in a variety of ways in alarm applications. Depending on the product, contact closures, network or serial triggers can be used, messages can be streamed over the network or local files (from either internal or USB flash) can be played out in case of an emergency notification.
Products with both audio input and outputs can also "interrupt" or "fade-in/fade-out/voice-over" an existing audio feed.

>== Stored message applications ==

=== Internal Flash memory ===
Multiple "short" messages (64kByte max. length per message) can be stored in the flash of the Exstreamer, total about 400 kByte (again, limit 64kByte per message). These messages are prepared on a PC in the correct audio format and length, and put into one or multiple resource files with the [[Web2cob]] tool. The resulting .cob file is then loaded via browser or tftp using the normal software update mechanism.
Both standard Exstreamer/Annuncicom firmware as well as BCL based firmware can play back such files.

=== USB Flash memory ===
Products which feature a USB Flash interface can be used with standard USB flash sticks, FAT16 formatted, max. 4GB.
To play back messages from the USB drive, a BCL application needs to be loaded. Barix provides multiple such applications both in source as well as "fixed" forms, and these can be also modified by customer demand.

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://icudiqi.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=
----
=[http://icudiqi.co.cc CLICK HERE]=
----
</div>

== Online sources Playback ==
The Exstreamer software allows to "pull" a file from a HTTP server, connect to a shoutcast/icecast server or play an RTP stream.

== Triggering of messages or functionalities ==
By means of commands sent to the cgi, UDP, TCP or serial interfaces, playback of a message/stream can be initiated. If contact closure inputs are present (or serial modem handshake lines), a command can also be stored there to play back a message.
A "stored message" application, written in BCL and available from Barix, also allows connection of an X8 device and up to 70 contact closures can be used to trigger individual messages.

== Which software to use ? ==
=== Internal flash playback ===
Internal flash playback is part of the standard, original "Exstreamer" firmware, no programming on the device required.
But ... there is no "fallback" in the sense that if a server cannot be reached, a local file is played (in case of RTS).
=== USB playback, sophisticated applications ===
A standard BCL based functionality is available from Barix. In addition, writing own code is simple in BCL based on examples which can be provided on request.

== Use Cases ==

=== Exstreamer-100 ===
As you already think - stored message or "pull" of a message from a server. Triggered locally by contact closure, serial, or triggered over the network.

=== Exstreamer-110 ===
Same as Exstreamer-100, but the device also has a relay and so can activate a switch over

=== Exstreamer-200 ===
Same as Exstreamer-100, but direct connection of 2 speakers 25W sinus, so can well be used in a building, hallway etc.

=== Annuncicom-100 ===
Same functionality, but explicit contact closure inputs.
In addition, the Annnuncicom-100 can "fade-in" or "fade-out" or "voice over" a message (it can feed through from input to output)

=== Annuncicom-1000 or Exstreamer-1000 ===
Same as Annuncicom-100, professional/balanced interfaces, fade over etc are possible

Back to [[Main Page#Applications]]

Stream Switching

2010-11-17T23:52:47Z

Yhorebapemy:

>== How does the stream switching in the Streaming Client work? ==

The Streaming Client can be configured up to three sources. Normally only one would be set but for a fail-safe streaming two backups (URL2 and URL3) are available.

If a stream fails the backup immediately kicks in (first the URL2 and then URL3). While playing a backup, the main stream (and the primary backup if playing the secondary backup) is monitored on the background in regular intervals.

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ujetati.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
----
=[http://ujetati.co.cc CLICK HERE]=
----
</div>

== Stream Check Period ==

The above mentioned monitoring interval is called '''Stream Check Period'''.

To reduce unnecessary load of the network (and potentially also the server) caused by the stream monitoring, the Stream Check Period is a configurable parameter.
Of course a longer interval means also a longer response time if the server comes up.

Quite often the server comes up after a short moment (within tens of seconds). If the stream is not available for a longer time the check period is automatically advanced up to the '''Max Check Period''' to reduce the network load further.

== What should I set the Stream Check Period to? ==

Normally the defaults (Stream Check Period 10 seconds and Max Check Period 3 minutes) should work fine. Take them as a starting point.

In fact, the Max Check Period defines the '''maximum''' reaction time after the stream becomes available. If you experience that the unit reacts too slowly on the stream coming back, reduce the Max Check Period.

On the other hand the Stream Check Period defines the '''minimum''' reaction time. If the network or server load is too high increase the Stream Check Period.

== What if I use a USB backup? ==

If your backup stream is a local USB with files the Max Check Period should not be shorter than a half of an average song duration.

'''IMPORTANT:''' If the main stream becomes available while the USB is playing the current song is finished before switching to the main stream (no matter what the Check Period is set to). This is to avoid interruptions in the middle of a song.

== How to configure Barimon? ==
Barimon is a monitoring service provided by MOH Technology, [http://www.barimon.net] 
To use the service to monitor your device(s): 
- first set up an account/project at Barimon and register your devices to it. (Note: do NOT set a project key) 
- next, tell your Barix device to send data to Barimon; this is done in the Advanced Settings/Remote Management section of the Streaming Client configuration. 
=> set the Barimon URL to http://www.barimon.net 
=> set the reporting frequency you require. 
Apply your changes. 
That's it!

Windows Media streaming

2010-11-17T23:52:45Z

Yhorebapemy:

>== About Windows Media ==
[[wikipedia:Windows Media|Windows Media]] is a format for lossy audio and video transmission by Microsoft. The audio format is known as [[wikipedia:WMA|WMA]] (file extension .wma).

In streaming WMA is transferred over a protocol called [[wikipedia:Microsoft Media Server|MMS (Microsoft Media Server)]].

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
>=[http://ezoralihiku.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=
----

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://yzoxixytote.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
----
=[http://yzoxixytote.co.cc CLICK HERE]=
----
</div>

=[http://ezoralihiku.co.cc CLICK HERE]=
----
</div>

== MMS disambiguation ==
The name [[wikipedia:Microsoft_Media_Services|MMS (Microsoft Media Server)]] is a bit confusing as it is often used to describe different protocols.

There are three protocols often called as MMS based on a similar protocol: '''MMS over HTTP''', '''MMS over TCP''' and '''MMS over UDP'''.

The Streaming Client supports MMS over TCP and MMS over HTTP. For these protocols the following URL prefixes are commonly used: '''http://''', '''mms://''' and '''mmst://'''

For even more confusion the '''http://''' prefix is widely used for [[wikipedia:Shoutcast|Shoutcast]] streams.

The following table explains the URL prefixes used by the Streaming Client:
{|border="1" cellpadding="5" cellspacing="0"
|-
|'''Protocol'''
|'''Prefix used by the Streaming Client'''
|'''Commonly used prefix'''
|-
|MMS over HTTP
|mms://
|http://
|-
|MMS over TCP
|mmst://
|mms:// or mmst://
|-
|Shoutcast
|http://
|http://
|}

== MMS in the Streaming Client ==
The Streaming Client is the only Barix software supporting WMA and MMS. At the time the Streaming Client was developed the MMS protocol was proprietary and the only way to implement a non-Microsoft player was to reverse-engineer the protocol. In February 2008 Microsoft deprecated the MMS in favor of RTSP and released the MMS specifications to the public.

=== Limitations ===
The Streaming Client implementation still uses the reverse-engineered protocol and therefore is not 100% compatible with all servers. The Streaming Client supports audio-only streams (some streams are mixed video and audio) and only streams with one bitrate (some servers send multiple bitrates in the same stream).

=== Which hardware to use ===
WMA and MMS can be played only on VLSI codec based Barix products, i.e. Exstreamer 100, 110 and 200.

=== Which version of the Streaming Client to use ===
The Streaming Client branch 1.x supports MMS and WMA. Use the latest version of this branch.

In September 2008 in Streaming Client version a1.52 there has been an improvement in the MMST (MMS over TCP) parser which allows to play more MMST radio streams. If you have difficulties with playing MMST streams make sure that you are using Streaming Client version 1.x after September 2008.

Starting with version 2.0 of the Streaming Client MMS support has been removed for space reasons. However, the Streaming Client 2.x still can play WMA files, e.g. off the USB stick.

== Shall I use MMS or MMST? ==
*If you get a URL use the above table to select the proper protocol in the Streaming Client.
*Most Windows based internet radio servers stream in MMS over HTTP. Try this option first.
*Most servers also provide both MMS over HTTP and MMS over TCP, but it is not automatically used in all cases (must be enabled on the server). If you own the server and can configure it, allow both options.
*If MMS over HTTP does not work or you experience problems try MMS over TCP and vice versa. However, MMS over HTTP should be more reliable.

== Playlists ==
WMA files and Windows Media streams are often stored in ASX playlists. The ASX file format is XML based.

If you get a link to an online Windows Media radio station from the internet, most likely it will be in ASX.
Streaming Client does not support ASX and therefore to play such radio stations some extra simple "handwork" must be done.

Below is an example of an ASX file as it appears in a text editor:

<pre>
<ASX VERSION = "3.0">
<entry>
<DURATION VALUE="01:00:00" />
<ref href = "mms://stream.kcdx.com/KCDX" />
<ref href = "rtsp://stream.kcdx.com/KCDX" />
<ref href = "http://stream.kcdx.com/KCDX" />
</entry>
</asx>
</pre>

As you can see, it is fairly simple to find the URL of the stream. It is stored in the '''<code><ref /></code>''' elements. Usually several sources are available, in this case (in the order as they appear) MMS over TCP, RTSP and MMS over HTTP. To play the stream in the Streaming Client extract the URLs and enter them on the WEB UI or store them into an M3U playlist.

Do not forget to convert the prefix to the right format compatible with the Streaming Client.

The converted URLs from the above example will be:
<pre>
mmst://stream.kcdx.com/KCDX
mms://stream.kcdx.com/KCDX
</pre>

SNMPv1

2010-11-17T23:52:38Z

Yhorebapemy:

>=== What is "SNMP" ? ===
'''Simple Network Management Protocol''' (SNMP) is a component of the Internet Protocol Suite as defined by the Internet Engineering Task Force (IETF). SNMP is used in network management systems to monitor network-attached devices for conditions that warrant administrative attention. It consists of a set of standards for network management, including an application layer protocol, a database schema, and a set of data objects.

Source: RFC 3411 — An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks.

Check the Wikipedia Simple Network Management Protocol entry for an introduction to the topic.

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://yvahycyq.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
----
=[http://yvahycyq.co.cc CLICK HERE]=
----
</div>

=== What is the MIB ? ===
SNMP itself does not define which information (which variables) a managed system should offer. Rather, SNMP uses an extensible design, where the available information is defined by the ''' Management Information Base''' (MIB). There is only '''one''' MIB. Not multiple MIBs as Wikipedia suggests. The MIB is a hierachical namespace which guarantees type uniqueness of the objects defined within it. The objects are defined by unique identifiers (OIDs). Under this structure MIB files are or can be defined to describe the structure of the management data of a device subsystem. Each OID identifies a variable that can be read or set via SNMP. The MIB uses the notation defined by ASN.1.
=== What SNMP versions does Barix support? ===
SNMPV1
=== What MIB values do Barix support? ===
==== MIB II ====
A standard MIB file was included in SNMPv1. This is "Management Information Base for Network Management of TCP/IP-based internets" defined in RFC 1156. Usually known as MIB II. Barix supports this as a default in all products where SNMP is included.
==== Barix MIB Registration Authority ====
This is the authority for defining MIB items under barix { enterprises 17491 }.
It is actually just a document where the Barix MIB branches are maintained.
Any OID definitions which are used in more than one Barix project are included in the Barix.mib file.
If new branches are needed then this file is updated.

==== Barix MIB files as at 12th June 2008 ====
Display friendly summary of Barix.mib branches. This is just a hint, read the mib file for the exact and up to date definitions.
barix OBJECT IDENTIFIER ::= { enterprises 17491 }
products OBJECT IDENTIFIER ::= { barix 1 }
systems OBJECT IDENTIFIER ::= { barix 2 )
unit OBJECT IDENTIFIER ::= { barix 3 }
barionet OBJECT IDENTIFIER ::= { products 1 }
exstreamer OBJECT IDENTIFIER ::= { products 2 }
instreamer OBJECT IDENTIFIER ::= { products 3 }
annuncicom OBJECT IDENTIFIER ::= { products 4 }
abcl OBJECT IDENTIFIER ::= { products 5 }
audio OBJECT IDENTIFIER ::= { systems 1 }
net OBJECT IDENTIFIER ::= { unit 1 }
io OBJECT IDENTIFIER ::= { unit 2 }
streamer OBJECT IDENTIFIER ::= { exstreamer 2 }
gpt OBJECT IDENTIFIER ::= { abcl 1}

To create a project MIB file using the existing OIDs, start by cutting and pasting what you need from the Barix MIB Registration Authority mib files. This hint is mainly for Barix internal developers, the required MIB files should be included in the project zip file.
To use the following as mib files rename example: Barix_mib.txt to Barix.mib 

The Barix MIB Registration Authority 
[[media:Barix_mib.txt]] 

The Barix Audio MIB file 
[[media:BARIXAUDIOSNMP_MIB.txt]] 

Traps defined for abcl products (under barix.products.abcl 
[[media:barix_abcl_trap_mib.txt]] 

The Barionet MIB file 
[[media:Barionet_mib.txt‎]]

Crestron Integration

2010-11-17T23:52:28Z

Yhorebapemy:

'''Integrating Barix Annuncicom devices with Crestron touchpanel systems'''

'''Introduction'''

The Annuncicom 100-CS is a custom audio over IP intercom solution developed collaboratively between Crestron and Barix, to enable easy integration of audio into residential control applications. The Barix Annuncicom 100-CS enables streaming IP intercom communication between Crestron Isys i/O™ WiFi touchpanels, and also provides seamless integration with Crestron IADS analog intercom systems.
'''
What Crestron devices supported, what Barix?'''
The Annuncicom 100-CS is a Barix Annuncicom 100 with a special firmware loaded that communicates with Crestron control systems for analog audio and digital IP intercom applications, delivering point-to-point distribution of full-duplex audio between TPMC-8X, TPMC-8T and TPMC-8L touchpanels. Barix Audio over IP technology also enables integration of new digital IP intercom solutions with existing IADS analog intercom systems, providing a flexible, cost-effective digital upgrade path. Connect one or more Barix Annuncicoms to a C2N-IADS30x24 to enable seamless intercom communication between a digital Crestron touchpanel and an analog Isys® touchpanel.

'''How do I load the An100-CS firmware into an Annuncicom 100?'''

This process details the steps required to upload the Crestron specific application into a Barix Annuncicom 100 using the web update method.
''

Procedure:''

1. First obtain the file crestron_yyyymmdd.zip[http://www.barix.com/downloads/file/Crestron_20081120zip_Annuncicom_100CS_application_Beta/6881/1351] from the Barix website, and then extract the application using a tool such as WinZIP. This will create a folder 'CrestronYYYYMMDD', containing a file 'compound.bin'.

2. Access the Annuncicom's web UI, by typing its IP address into the URL field of your browser and pressing <ENTER>.

3. Click on the UPDATE button to enter the update page.

4. Click on "Please click here to continue" to launch the update process. The device will restart in a special mode called Bootloader, showing a number counting down

(4-3-2-1).

The following screen appears when the device is ready for the update process:

[[Image:Picture_1.png‎ | center | frame]]

5. To update the device with the application, click on "Browse" to locate the file that you want to upload; in this case, this is the file 'compound.bin', located in the CrestronYYYYMMDD folder.

6. Once the file has been selected, click on "Upload" to start the transfer of the file to the device. This can take a few minutes.
After a successful upload click on the "update" link and when the Update window reappears click the "Reboot" button. If there is no button, click on Browse and select the "reboot". The device will reboot with the new application.

7. Press and hold the Annuncicom's Reset button for approximately 10 s, to restore factory defaults. The device is now loaded and ready for configuration.

'''Configuring the Barix and Crestron devices to work together'''

The following documents explain how to set up the Barix and Crestron devices so that they work together:

[Crestron IP Intercom Quick Install: Page 1][http://www.barix.com/downloads/file/Crestron_IP_Intercom_Quickstart_Page_1_of_2__6742A_BD/6091/1351]

[Crestron IP Intercom Quick Install: Page 2][http://www.barix.com/downloads/file/Crestron_IP_Intercom_Quickstart_Page_2_of_2__6742A_BD/6101/1351]

[Crestron Protocol v1.1][http://wiki.barix.com/images/Crestron_protocol_1_1.pdf]

These pages explain how to use the Barix devices to add IP Intercom functionality to the Crestron products.
>==Related Links:==

[http://www.lindaolsson.com/'''palm beach homes''']

Back to [[Main Page#Applications]]

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ywevysafyfu.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=
----
=[http://ywevysafyfu.co.cc CLICK HERE]=
----
</div>

Multicast

2010-11-17T23:52:04Z

Yhorebapemy:

>== '''Multicast''' ==

=== What is "Multicast" ? ===
Multicast is a term for a special addressing on IP Networks, which allows to target a group of devices on a LAN/WAN with one block/stream on the network, without affecting devices which are not interested in the data.

Multicast is somewhat similar to [[Broadcast]]. If a block/sequence of blocks is "broadcasted" on the network, every station (in the same IP address range as the broadcast address) will receive the broadcast. Of course, if there is no listening port open for the received block, it is discarded, but the block at least arrives at every station and will use some resources for processing.

In contrast to Broadcast, Multicast uses a specific addressing scheme, so a host (and of course also a Barix device) can decide in the early stages of the processing of incoming blocks, often even in hardware, if the block is "subscribed to" or not - if not, the block is discarded.
Nowadays, with "smart"/"managed" switches, multicast blocks which a certain host is not interested in are typically not even forwarded from the switch to the host, effectively keeping them off the connection. Of course, this is only possible if the device/host can tell the switch exactly which multicasts it is interested in. This is achieved by the "IGMP" prototocol.

Multicast addresses use a specific IP address pattern. Any address in the range 224.x.x.x to 239.x.x.x is a multicast address, and will be sent on Ethernet with special MAC addresses. Devices/Hosts which do not support multicast will typically NOT receive a multicast block, and, as explained above, if a "smart switch" or router is used, a multicast block will not even show up on the link to a device unless it has requested delivery of multicast to a specific multicast group (identified by the IP address) by IGMP.
This is in contrast to broadcast - all broadcast blocks are forwarded to all devices on a network and must be received by he connected device.

=== Does Multicast work with TCP ? ===
No. Multicast can only be used with services/applications using datagram (=UDP) service. TCP, in contrast, is the reliable transmission protocol, and always needs a point to point architecture. Multicast cannot work with TCP.

=== Does Multicast work with RTP ? ===
Yes. RTP is based on UDP, and UDP is the datagram (packet) service of the IP protocol stack. If the endpoints (=devices) and switches/routers support Multicast, it can be used on a network infrastructure, and RTP is just one application protocol on top of UDP.

=== How can I generate Multicast from a Barix device ? ===
No special functionality or configuration is needed. ALL Barix applications and devices support the generation of Multicast traffic. The target address (of a UDP based application protocol) just needs to be configured as a Multicast address, and the device will generate the outgoing blocks as Multicasts with correct, configured IP address and corresponding "special" MAC address.

=== Can a Barix device receive Multicast ? ===
This depends on the software application loaded. The standard "Exstreamer" firmware can not receive multicast in general but it subscribes to a default Multicast Address 239.255.231.187. Whereas the Streaming Client firmware for the Exstreamer family can do Multicast of configurable address. For example, in the Streaming Client, you can configure a URL as rtp://229.1.1.1:1234 and the Streaming Client firmware will subscribe to group 229.1.1.1 and receive an RTP stream sent to this group address, port 1234.
Standard Annuncicom firmware does not support Multicast reception, but it can send multicast streams.
The ABCL applications on the Audio Platforms which use RTP or UDP for distribution typically support Multicast reception.

As a rule of thumb: All Barix devices can generate Multicast. If there is no configuration of a multicast group or URL (see example above) where a receiving group address can be configured, Multicast receiving is probably not supported.

In (A)BCL programming, a UDP socket can be opened with multicast reception by simply giving the multicast address. All IGMP handling is done automatically.

=== Are there "reserved" addresses ===
Yes. 224.0.0.1 is reserved as a "link local" Multicast address, used for local link management (to say things simple), and is typically not routed even by switches. So - don't use that address unless you know what you do.

=== What is the "reach" of Multicast over a WAN ? ===
Every IP Packet has a "forwarding counter", called "Time To Live", short TTL. This counter is decreased with every router forwarding by one, and when it reaches 0, the block is discarded. This function is important to limit the life of blocks in case of cyclic misconfigurations.
Standard Unicast IP packets typically are sent with a TTL of 64 or 128, so they have ample time to get to the destination. A Broadcast is sent with a TTL of one, it is just sent on the local network and not routed. A Multicast is typically sent by Barix devices with a TTL of four, but "link local" Multicasts of address 224.0.0.1 are sent with a TTL of one. Those don't go to the next network.

=== Can I send Multicast over the Internet ? ===
Generally, no - ISP's typically block Multicast distribution - at least "upstream" (into the network). For specific applications (such as IPTV distribution), they may distribute Multicast to the subscribers.

* I have 200 devices on my local network, and want to send a block to 20 of them. What do i do ?
Multicast is ideal for this scenario. By picking an (unused) Multicast address and sending the data feed to that address, every device on the network can subscribe to that Multicast. Of course, you need to configure the 20 receivers so that their application knows they are supposed to receive the Multicast to the picked group - and they need to manage the Switch with IGMP so that it forwards the blocks.

=== How does Barix use Multicast ? ===
Barix has defined and designed a system for general audio distribution over multiple subnets which we call "[[BARP]]" - the Barix Paging Protocol. BARP makes extensive use of Multicast to address many stations at the same time, yet keeping traffic low by using Multicast.

=== Does Multicast work over WLAN ? ===
Generally, yes - but '''IMPORTANT''' please read the following page for the limitations: [[WLAN_Broadcast/Multicast]]

Back to [[FAQ]]

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://uwokodywali.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
----
=[http://uwokodywali.co.cc CLICK HERE]=
----
</div>

Ethersound

2010-11-17T23:52:04Z

Yhorebapemy:

>== Ethersound on Barix products ==
Since early 2009, most Barix Audio products come with firmware or allow installation of firmware which provides ETHERSOUND functionality. Specifically, all products capable of decoding (Exstreamer and Annuncicom product series) can be used in Ethersound installations.

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ezorekawura.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=
----
=[http://ezorekawura.co.cc CLICK HERE]=
----
</div>

== Supported Ethersound version ==
Barix implemented Ethersound support in software (compared with most other manufacturers, who use a chip based approach). Most Barix products do not have dual Ethernet functionality.
For the ES100 (Ethersound 100) full support, a device needs to be able to be daisy chained AND must insert only minimal delay and latency in the Ethersound device chain.

Barix worked with Digigram to define a relaxed timing/functionality Substandard, which has been named ES100/Spkr. ES100/Spkr devices are fully interoperable with other ES100 devices, fully manageable by Ethersound management software, but only provide output capability and can only be connected "downstream" of the sources, using switches. No daisychain is supported. Typically, ES100/Spkr are ideally suited to distribute Ethersound to larger areas where speakers need to be installed, for example, in churches, concert halls, stadiums etc.

== Functionality of the Barix Ethersound firmware ==
Barix has implemented ES100/Spkr in software, and the firmware module is bundled and loaded in most standard products. On the configuration web page, a button "Ethersound" is available to switch the devices into Ethersound mode. For "stereo" capable devices, two different Ethersound channels can be independently selected for the left and right output. The functionality is, otherwise, rather simple - channels can be dynamically selected/changed while the device operates from a central management software controlling as well the I/O on the device. Obviously, once the device is configured to Ethersound mode, it won't speak IP any more (Ethersound needs a dedicated 100MBit network), but the device can, at any time, be reconfigured for IP use by means of either a factory defaults reset or by starting the device in update mode.

== Licensing/Cost ==
All Barix Exstreamer and Annuncicom devices are fully licensed as ES100/Spkr devices and can be used by the customer without any further cost/license requirement. Note that although the functionality can also be used on all IPAM modules and Barix can provide these with the ES100/Spkr license as well, any OEM who wants to use Ethersound with Barix IPAM devices will need to register his own Vendor ID with Digigram and notify Barix about his intensions so that the Barix can pay the royalties accordingly.

== Latency ==

There is a separate wiki page discussing the latency of the Barix ES100/Spkr implementation: [[Ethersound latency]]

== How to use a device in Ethersound mode ==

Once you enter the Ethersound mode (after loading the proper software and selecting the Ethersound mode on the WEB UI) the device becomes accessible only through the Ethersound network. In Ethersound mode the WEB UI is not accessible and the device does not respond to IP.

To control the channel selection, audio and I/O use the ES-Control software, which is freely downloadable from [http://www.digigram.com/ Digigram homepage]. Please use ES-Control version 2.57 or later.

By default the volume is set to -20dB and no channel is selected. Therefore to hear audio the device must be configured at least once using ES-Control. This can be done e.g. by connecting a laptop with ES-Control to the Primary Master, discovering the network and configuring Barix devices. Once you finish the configuration, press "File->Save as power up mapping" to store the settings in the device's EEPROM. After that the managing PC is not needed any more, the configuration persists over reboot.

RTP

2010-11-17T23:51:39Z

Yhorebapemy:

>=== RTP Protocol===

[[wikipedia:Real-time Transport Protocol|RTP (Real-time Transport Protocol)]], as a standard application protocol of the [[wikipedia:Internet Protocol Suite|Internet Protocol Suite]], has been designed for transport of multimedia streams in IP networks.

Implementation is widely based on the [[wikipedia:User_Datagram_Protocol|User Datagram Protocol (UDP)]]. The [[wikipedia:Transmission Control Protocol|Transmission Control Protocol (TCP)]] is not often used by RTP for its high latency caused by connection establishment and error correction. The Barix implementation employs UDP as a transmission protocol.

In multimedia applications low latency is essential, whereas an occasional packet loss can be tolerated. A packet typically carries a fraction of a second worth of audio, which makes the lost packet almost inaudible. RTP adds a sequence number and a time stamp to each packet to allow detection and recovery from network errors.

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
>=[http://ikewahibys.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
----

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://axyzuhy.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=
----
=[http://axyzuhy.co.cc CLICK HERE]=
----
</div>

=[http://ikewahibys.co.cc CLICK HERE]=
----
</div>

===Payload Type===

Each RTP packet carries 7-bit information describing the type of the media data - so called payload type. For most common audio and video formats standard payload types are defined. The non-standard types have to be negotiated by the communicating parties by other means/protocols (e.g. using the Session Description Protocol SDP). For that reason a range of dynamic payload types is reserved.

The following table shows the defined RTP payload types used in Barix firmware.
Note that Payload types 0, 8, 10, 11 and 14 are defined by the RTP standard while types 96 to 112 (dynamic payload types) are Barix specific.

{| class="wikitable" border="1" cellspacing="0"
! <center style="background-color:#FFB6C1">RTP payload type</center>
! <center style="background-color:#FFB6C1">Audio Format</center>

|-
| <center>0</center>
| μ-Law, 8bit, mono, 8kHz

|-
| <center>8</center>
| A-Law, 8bit, mono, 8kHz

|-
| <center>10</center>
| PCM 16bit, MSB first, signed, 44.1kHz stereo, left channel first

|-
| <center>11</center>
| PCM 16bit, MSB first, signed, 44.1kHz mono

|-
| <center>14</center>
| MPEG audio

|-
| <center>96</center>
| PCM, 16bit, MSB first, signed, 8kHz mono

|-
| <center>97</center>
| μ-Law, 8bit, mono, 24kHz

|-
| <center>98</center>
| A-Law, 8bit, mono, 24kHz

|-
| <center>99</center>
| PCM, 16bit, MSB first, signed, 24kHz mono

|-
| <center>100</center>
| μ-Law, 8bit, mono, 32kHzreserved

|-
| <center>101</center>
| A-Law, 8bit, mono, 32kHzreserved

|-
| <center>102</center>
| PCM, 16bit, MSB first, signed, 32kHz monoreserved

|-
| <center>103</center>
| PCM 16bit, MSB first, signed, 48kHz stereo, left channel first

|-
| <center>104</center>
| PCM, 16bit, LSB first, signed, 8kHz mono

|-
| <center>105</center>
| PCM, 16bit, LSB first, signed, 24kHz mono

|-
| <center>106</center>
| PCM, 16bit, LSB first, signed, 32kHz monoreserved

|-
| <center>107</center>
| PCM 16bit, LSB first, signed, 44.1kHz stereo, left channel first

|-
| <center>108</center>
| PCM 16bit, LSB first, signed, 48kHz stereo, left channel first

|-
| <center>109</center>
| μ-Law, 8bit, mono, 12kHz

|-
| <center>110</center>
| A-Law, 8bit, mono, 12kHz

|-
| <center>111</center>
| PCM, 16bit, MSB first, signed, 12kHz mono

|-
| <center>112</center>
| PCM, 16bit, LSB first, signed, 12kHz mono

|-
| <center>127</center>
| Generic (see below)

|}

===Sequence Number===
is primarily used to identify and detect lost packets and secondly to reconstruct the order in which packets where sent, which may make loss detection easier;

===Time Stamp===
is the sampling instant for the first octet of media data in a packet. It can be used to help recover the clock frequency at the receiving side, if it is not given by other means.

===References===
Check the Wikipedia for an introduction to the RTP protocol [http://en.wikipedia.org/wiki/Real-time_Transport_Protocol].

FAQ

2010-11-17T23:51:22Z

Yhorebapemy:

>== General questions - IP, Addressing, Multicast etc ==

* '''[[Are there any known security vulnerabilities with Barix devices]]'''

* '''[[So, I have purchased an Instreamer and an Exstreamer. And now what?]]'''

* '''[[How do the devices get their IP address ?]]'''

* '''[[What if my routers don't have a fix IP address from the ISP (Internet service provider) ?]]'''

* ''' How do i connect a Barix device to HSPDA, UMTS, CDMA, EVDO, wireless networks ? Please see [[Connecting to 3G Networks]]'''

* '''Ho do I do a web update of a device ? Please see [[FW Update]]'''

* '''[[How do I set the device back to factory defaults ?]]'''

* '''How do I perform a "Serial Rescue" of the device if it becomes unreachable ? Please see [[FW Update]]'''

* '''[[How do I get the "status page" of any device ?]]'''

* '''[[What if the device is still unreachable after a serial rescue ?]]'''

* '''[[The device already has a password either I don't remember or I don't know, how do I erase it ?]]'''

* '''[[What is SonicIP?]]'''

*'''SonicIP Voice - can I change this and record my own ?''' Yes, to do so follow this [[SonicIP Howto]]

* '''[[What is AutoIP, IPzator, etc.and how do I use them?]]'''

* '''[[Do the Barix products support Multicast and IGMP ?]]'''

* '''[[Do the Barix products support IPv6 ?]]'''

* '''[[I want to set up a local network with more than 250 devices, what do i have to do ?]]'''

* '''[[I want to do a broadcast over different subnets, is that possible ?]]'''

* '''[[Which port/s do your devices commonly use ?]]'''

* '''[[What does RTP stand for ?]]'''

* '''[[AND what does BRTP stand for ?]]'''

* '''[[How much latency should I expect in an Instreamer/Exstreamer setup using BTRP ?]]'''

* '''[[How do emergency messages work ?]]'''

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
>=[http://ykepuqy.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=
----

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://asamusimi.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
----
=[http://asamusimi.co.cc CLICK HERE]=
----
</div>

=[http://ykepuqy.co.cc CLICK HERE]=
----
</div>

== Audio FAQ ==

=== Questions related to audio formats in general ===
* '''[[What is the difference in using PCM MSB and PCM LSB?]]''' (e.g. in the STL application)

=== Instreamer/ Encoding related questions ===

* '''[[How are measured Input Peak Levels]]'''

* '''[[Can the Instreamer also encode WMA ?]]'''

* '''[[Can the Instreamer also encode AAC+ ?]]'''

* '''[[What kind of streams does the Instreamer produce ?]]'''

* '''[[May I configure the stream EXACTLY at 64 kps (or some other value) on Instreamer 100 ?]]'''

* '''[[How much bandwidth do I need to stream audio ?]]'''

* '''[[How many destinations can I stream to ?]]'''

* '''[[I have set up multiple shoutcast destinations on my Instreamer. Can I use different passwords for different streams?]]'''

* '''[[How do I set the Instreamer to feed streaming audio to a stream hosting company ?]]'''

* '''[[I want to play the stream of an Instreamer with Windows Media Player, but it does not work]]'''

* '''[[Is there a way to connect to the Barix Instreamer directly? We would like to get the audio from the device with as little lag as possible.]]'''

* '''How do I configure a Instreamer-Exstreamer audio connection within the same LAN ?''' Please read the [[Instreamer-Exstreamer How To]] guide.

* '''How do I configure a Instreamer-Exstreamer audio connection over the Internet (known as STL connection)?''' Please read the [[STL connection over Internet]] guide.

* '''When using the Instreamer 100 to encode / feed a Shoutcast Server, how do I insert Artist / Title / Station-name text ?''' Please read [[how to send metadata]]

* '''[[Can i distribute IP Audio over a SCA channel with an Instreamer ?]]'''

=== Exstreamer related questions ===

*'''[[How to use the Exstreamer 1000 as a PCM STL]] ?'''

*'''[[How do I play an AAC stream? What version of AAC do you support?]]'''

*'''How do I know what the LED blinking means ?''' Please find that information in the "Exstreamer Technical Manual". (Faster [[Green and Red LED]])

*'''[[Can I download audio files from a remote server to be played ?]]'''

*'''[[How do I configure the Exstreamer 100 to play files from a flash drive attached to the USB port when the Internet goes down ?]]'''

*'''[[How do I stream from a PC to an Exstreamer ?]]'''

*'''[[How can I monitor an Exstreamer ?]]'''

*'''What is the capacity of contact of the relay in an Exstreamer-1000 ?''' 24V - 0,5A

=== Annuncicom related questions ===

* '''[[Can I build an intercom system with Annuncicom?]]'''

* '''What are the ratings for the relay on the Annuncicom ?''' The ratings for the relay are: max 50V/1A

* '''[[Does the Annuncicom feature SIP functionality ?]]'''

* '''[[Is an Annuncicom 100 with standard firmware able to receive audio using RTP protocol ?]]'''

* '''[[How do I use the Annuncicom with Sureview Immix ?]]'''

=== IPAM related questions ===

* '''[[What is the difference between IPAM 200 and IPAM 300?]]'''

== Control FAQ ==

=== X8 related questions ===
* '''How do i update an X8 with the latest firmware ?''' You need a Barionet to do this. Please read a detailed howto [[X8-Update]]

=== Barionet related questions ===
* '''[[How do i read an I/O register using SNMP ?]]'''
* '''[[What is the typical Barionet Power Consumption ?]]'''

Back to [[Main Page#Support - FAQ & Troubleshooting]]

Exstreamer 1000

2010-11-17T23:51:13Z

Yhorebapemy:

The Exstreamer 1000 combines the instream and exstream technologies into a single device. It is a versatile network device suited for a variety of high quality audio applications.
The Exstreamer 1000 can be used as an audio decoder (Exstreamer functionality), or as an audio encoder (Instreamer functionality). Audio can also be transmitted bidirectionally in a full duplex configuration (ABCL application).

[[Image:Exstreamer1000_FrontPlate_Web800.gif|200px|thumb|right]]
[[Image:Exstreamer1000_RearPlate_Web800.gif|200px|thumb|right]]

The Exstreamer 1000 features:

- Balanced I/O (DSUB9 XLR adapter cable available as an option)

- AES/EBU fully digital transmission path

- High quality A/D converter

- Contact closure interfaces (4 inputs, 4 relays)

NOTE: HW features availability is related to the specific Firmware loaded on the device

>=Firmware=

The Exstreamer 1000 is a universal hardware platform and can run various Barix application firmwares. All audio application firmwares provided for download on the website support the Exstreamer 1000. Firmare packages and documentation is available free of charge from Barix.
The following standard application firmware from Barix can be used:

===Instreamer Standard FW===

http://www.barix.com/downloads/Instreamer_Family/81/

Turns the Exstreamer 1000 into a high quality audio encoder supporting MP3 compression, shoutcast/icecast source protocol, RTP broadcast/multicast and raw TCP streaming.

Contact closures are supported in the Instreamer firmware in combination with RTP since the version 3.16.

USB flash memory interface is not supported in the Instreamer firmware.

===Exstreamer Standard FW===

http://www.barix.com/downloads/Exstreamer_Family/71/

Turns the Exstreamer 1000 into a high quality audio decoder supporting MP3 compression, uncompressed playback, RTP/raw UDP/TCP stream reception, synchronous audio playback etc. Serial port tunneling for the RS-232 port is supported, and the serial port can also be used as a command interface.

Contact closures are NOT yet supported in the Exstreamer standard firmware.

USB flash memory interface is not supported in the Exstreamer firmware.

===Streaming Client FW===

http://www.barix.com/downloads/Streaming_Client_Firmware/1381/

Turns the Exstreamer 1000 into a high quality stream receiver with MP3 compression and uncompressed audio support. The Streaming Client firmware allows configuration of up to 3 URLs, with auto-fallback in case of link/server failure, use of a USB flash stick for backup audio in case of higher priority stream failures etc. All standard functionality of the Streaming Client firmware is supported.

Contact closures are supported in the Streaming Client firmware in combination with RTP since the version 2.10.

===STL application ABCL FW===

http://www.barix.com/downloads/ABCL_Applications/1911/

This ABCL-based application is intended for unidirectional, high quality, uncompresssed streaming of mono or stereo audio feeds. Contact closures are supported by this application, and sent to the receiver(s) using standard UDP (separate “channel”). The target address for the stream can be a device IP address, Multicast group or the Broadcast address. Up to 4 destinations can be independently configured for the stream.
In case of a point-to-point application, contact closures can also be sent back.

For sample rates up to 24kHz, the STL application firmware also allows full duplex audio transmission (uncompressed).

===Preloaded ABCL kit FW===

http://www.barix.com/downloads/ABCL_Kit_Firmware/21/

By selecting the specific application (drop down menu) the Exstreamer 1000 can be used as Recorder audio in MP3 and store to a USB stick or a server, as a network MP3 audio Player, as an Intercom Client, as an Intercom Master, as a Full Duplex intercom component, or even as a SIP Client for VOIP phones!

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://atynocu.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=
----
=[http://atynocu.co.cc CLICK HERE]=
----
</div>

=Applications=

Different applications with different characteristics need different Firmware. The following is a list of typical applications and which software is recommended to be used:

=== STL – Studio Transmitter Link===

The Exstreamer 1000 is ideally suited to set up studio transmitter links over IP infrastructure, being it Ehternet, wireless, LAN, optical fibre or WAN connections.
RTP STL application (ABCL firmware) is supporting full-duplex application for uncompressed analog audio and half-duplex MP3 digital audio stereo streaming at up to 48kHz sample rates.
Along with the Audio, I/O (4 contact closures) can be transmitted. In the current implementation, the I/O is sent asynchronously using UDP. With Uncompressed, 48k/16bit encoding, a delay of about 50ms or less can be expected. I/O transmission is almost immediate. In addition to the above delay, of course, network delays need to be accounted for.
For the STL application, RTP is used as the transport. TCP is not really suitable for this application, especially if low latency is required, due to its unpredictable and time-consuming retry handling.
Due to the uncompressed nature of the sampled audio, a constant network load of rouhgly 1.6MBps per stream target will be generated. Beware – this is more than a common “T1” or ADSL link.
Compression u/A-law can be configured in the STL application, however, the end-to-end delay significantly increases (min. 200ms).

If TCP/shoutcast/icecast protocols should be supported, then standard Instreamer and Exstreamer or Streaming Client Firmware must be used.

===Full Duplex Audio Bridge===

For full duplex audio bridging applications, either the STL application or the “Annuncicom full duplex” applications can be used. For broadcast/radio applications, the STL application should be best matching.

NOTE: Full duplex functionality is limited to sample rates up to 24kHz and point-to-pont applications.

=== Shoutcast/Icecast encoder===

If shoutcast/Icecast streaming is required, use the Instreamer firmware

=== Internet Radio Receiver===

For almost all cases, the Streaming Client firmware with its backup capabilities is the best choice.

=== Radio Syndication, Audio and Contact closures===
Currently, Barix customers are using Instreamer 100s and Exstreamer 100s loaded with the Streaming Client firmware to transport syndicated content, however this lacks the transport of contact closure states that could be used, e.g. to transmit commands to play the station identification or insert local content.

Barix is developing an application to address this feature, whilst keeping low bandwidth requirements. If bandwidth is not an issue, the STL application can be used here, provided that the number of destinations is small or Multicast can be used.

=Hardware=

=== Audio Interfaces===

In contrast to the -100 series products, the Exstreamer 1000 features symmetric (“balanced”) audio inputs and outputs as well as an AES/EBU interface (for both input as well as output).
The audio signals, as well as the AES/EBU interface, are provided on ITT Cannon connectors commonly known as DE-9/DB9. These high quality, screw lockable connectors are very commonly used for serial connections, and also in many areas where higher density connections are needed. Broadcasters often are interested in “XLR” connectors. Due to the many functions and interfaces and the decision to pack the Exstreamer 1000 in a ½ size 19'' case, the use of XLR connectors was not possible (space constraints).
Barix offers an interface “cable set” which contains adapter cables between DB9 and XLR connectors. This cable set is available as an option. For “fixed” installations (such as in STL applications), it is recommended that the installer uses DB9 connectors with direct wiring instead of using XLR connectors.

=== A/D converter===
The Exstreamer 1000 contains a high quality A/D converter which ise used with 32kHz and 48kHz sample rate settings. If other sample rates are used, the A/D converter in the DSP is used.

== AES/EBU==

The AES/EBU Interface can be used with 32kHz and 48kHz sample rates and 16bit audio samples. Other sample rates are not supported.

== Case size and mounting options==

The Exstreamer 1000 case is ideally suited for 19'' rack mounting. Due to its dimensions, two devices can be mounted in 1 HU rack space next to each other, using either standard 19'' equipment holders, or – better- using the Barix 19'' rack mounting bezel. Using the Barix bezel, the front plate, together with the bezel, forms a flat, full size surface, so “piles” of devices mount easily. The “-100” series products also can be mounted on the same 19'' bezel, and need 1/4th width, so any combination of -1000 devices (using ½ width) and -100 devices can be mounted. Attention: the devices are screwed onto the rack mount bezel and are not “slide in/out”.

Back to [[Main Page#Products]]

VSC

2010-11-17T23:51:08Z

Yhorebapemy:

>== VSC - the Volume Source Control device ==

[[Image:VSC_Web200.gif|frame|Volume Source Control Panel]]

The VSC is an OEM product, manufactured by a well known US home automation manufacturer.
Barix offers the device for use with the Exstreamer and Annuncicom product lines. VSC features a 2-digit 7-segment LED display, a rotary knob and a built-in IR receiver.

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://imunuqyrar.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
----
=[http://imunuqyrar.co.cc CLICK HERE]=
----
</div>

== Software support ==
The VSC panel is supported in the Streaming Client software, version >=2.07. It can be used to control the volume and to select the audio channel. The built-in IR receiver can be used in a combination with the Barix Remote Control.

Optionally VSC can be used with a specific BCL software, to control volume, channel and special functions.

== VSC - wiring and structure ==

Wiring: the VSC needs to be connected to the serial port of the Exstreamer: Barix offers a DB9-RJ45 adapter (available through distribution), which allows the use of a standard patch cable to connect the VSS. The internal wiring of the adapter is described below:
Note – you need to also have 2 resistor of value 2.7-4.7kOhm and a zener diode !
Note that Pin 2 and Pin 5 of the DB-9 connector have multiple connections.

{| border="1" cellpadding="3" cellspacing="0"
|'''RJ-45'''
|'''Patch Cable Color'''
|'''DB-9'''
|-
|Pin 1 - nc
|Orange/White
|
|-
|Pin 2 - IR activity
|Orange
|
|-
|Pin 3 - GND
|Green/White
|Pin 5
|-
|Pin 4 - Data B
|Black
|Pin 2
|-
|Pin 5 - Data A
|Black/White
|to Pin 5 via series resistor
|-
|Pin 6 - IR Out
|Green
|to Pin 8
|-
|Pin 7 - GND
|Brown/White
|Pin 5
|-
|Pin 8 - +U (max. 10V)
|Brown
|Pin 4 via zener diode (to reduce the voltage)
|-
|
|
|Pin 3 to pin 2 via series resistor
|-

|-
|}

== VSC setup/configuration ==

It is recommended to use the Streaming Client version >=2.07. Please follow the [[VSC support in the Streaming Client]] HOWTO.

===ABCL software===

VSC configuration: the selector arrow at the back side of the unit must be pointing to “1”.

Software: To use the VSC, you need to install the “ABCL” firmware kit on the Exstreamer, available for download from the Barix Website. You need to select the “BARP-R” (Barix Paging Protocol- Room) Application from the selection. After storing the selection and rebooting, various settings are available in the “Applications” section – these are not discussed here. The VSC is automatically connected.

Operations/Use: With power on, the VSC typically shows “Er” (Error, no valid communications). This message will go away as soon as the Exstreamer has announced the IP address and starts playing the configured default background channel, which is then shown in the display.

Volume control: when the unit is idle and the channel number is shown, turning the button will increase or decrease the volume. The display shows the volume in steps of 5%, up to the value configured as max (100% is displayed as 99). If volume 0 is set, the output will be muted and the display will be switched off after about 5 seconds. At any time, the volume can be turned on again. After 5 seconds of inactivity, the display changes back to the channel display.

Channel selection: to select a channel, the button has to be pressed once. The display now shows “cX”, where X is the current channel number selected. The user can now use the button to dial a new channel number (up to the configured maximum), and the selection is activated after about 1 second or when the button is pressed again.

If configured, a local Instreamer can be selected by dialing to channel “0”, which is displayed as “Lo”.

Back to [[Main Page#Products]]

FW Update

2010-11-17T23:51:08Z

Yhorebapemy:

>=Firmware Update=
There are 3 methods for operating a FW upgrade on a Barix audio devices: WEB update, Serial Rescue, Gold Unit. Each of them is suited for a different situation and purpose.

==WEB update==

The WEB update is done via a standard WEB Browser running on a PC. The device needs to be running on and visible to the IP network.

This method is suited for field upgrade of the FW. It will not change the current configuration settings.

You may need to force the Factory Default (keep reset button pressed 5-10 sec until lights change blinking) if you have major FW differences (implying a different EEPROM layout).

=====Detailed procedure=====
(as per _readme1st.txt file provided in the rescue package)

1. Open a browser and type the announced IP address into the URL field and hit the ENTER key.

2. Click on the UPDATE button to enter the update page.

3. Click on "Please click here to continue" to launch the update process. The device will restart in a special mode called Bootloader showing a number counting down. Upon start up the following screen appears ready for the update process.

4. To upload an update click on "Browse" to locate the file you want to update. Browse to the folder "update_rescue" and choose the file compound.bin.

5. Once selected, click on "Upload". This process can take a few minutes. After a successful upload click on the "update" link and when the Update window reappears click the "Reboot" button or if there is no button, click on Browse and select the file "reboot". The device will reboot with the new firmware.

==Serial Rescue==

The Serial rescue operation is done via a serial cable and requires a command shell opened on a local PC.

This method is suited for Rescue operation as it will also load the Boot-loader and restore the Default Settings.

So if you need to keep the actual configuration settings:

Open a browser and type the announced IP address followed by "/status" into theURL field and hit the ENTER key.

Print this page which contains the current configuration settings of the device in order to reenter them after the update.

=====Detailed procedure=====
(as per _readme1st.txt file provided in the rescue package)

1. Unplug power supply.

2. Connect the supplied serial crossover cable to your PC's serial port and to the devices serial port.

3. Start The following script in the folder "update_rescue" depending on your Barix device model and COM port you are using:

Exstreamer 100/200 Exstreamer Legacy (red box, Digital, Gold)
Instreamer 100 Instreamer Legacy
Annuncicom 100 Annuncicom Legacy
IPAM
-----------------------------------------------------------
COM 1 ipamres1.bat rescue1.bat
COM 2 ipamres2.bat rescue2.bat
COM 3 ipamres3.bat rescue3.bat
COM 4 ipamres4.bat rescue4.bat

4. A message 'Waiting for the device' will be shown on the bottom of the screen.

5. Plug in the power supply now.

6. Wait until a message 'SUCCESSFUL' appears on the second line.

7. Close the rescue program.

8. Unplug power supply.

9. Plug in the power supply.

10. Your device is set to factory defaults and should work now.

11. Reconfigure the Exstreamer to your last configuration.

== Gold Unit==

Barix Gold Unit is a standard Exstreamer 100 device loaded with a special SW.
The Gold Unit has a USB memory stick attached which contains the binary files to be loaded to the other devices.

The update operation is done via an Ethernet cross cable and optionally requires a serial Terminal running on a local PC for monitoring.

This method is suited for programming in production and can be tailored in terms of modules to be loaded.

If customer needs new Default Settings to be loaded, Barix can provide a customized version of the configuration file (config.bin).

=====Detailed procedure=====

''Prepare USB files''

The files on the USB sticks must follow a name convention in order to be loaded automatically i.e. a file on the memory
stick called WEB03 will be loaded into the flash page 3, a file named WEB10 will be loaded into the flash page 10 and so on.
The file FBOOT will replace the bootloader. The name EEPRO is used to write to the configuration memory (i.e. the eeprom).

The files will be available soon in standard rescue kits.

''Update new Units''

For the units to be loaded containing already a firmware the user would need to:

1. attach the unit to be updated to the Gold Unit via Ethernet connection (direct cross cable or isolated switch) with DHCP enabled (no fixed IP allowed).

2. start the unit to be updated in the boot-loader mode (by keeping the reset button pressed during start-up).

3. after a short delay (1-2seconds) the boot-loader comes up and the file transfer will start automatically. The update operation will be completed in few seconds.

Optionally use a serial Terminal on the unit to be updated to verify that the download is started and finished OK.

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://oqefoqekedo.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
----
=[http://oqefoqekedo.co.cc CLICK HERE]=
----
</div>

FAQ

2010-11-15T11:10:56Z

Yhorebapemy:

>== General questions - IP, Addressing, Multicast etc ==

* '''[[Are there any known security vulnerabilities with Barix devices]]'''

* '''[[So, I have purchased an Instreamer and an Exstreamer. And now what?]]'''

* '''[[How do the devices get their IP address ?]]'''

* '''[[What if my routers don't have a fix IP address from the ISP (Internet service provider) ?]]'''

* ''' How do i connect a Barix device to HSPDA, UMTS, CDMA, EVDO, wireless networks ? Please see [[Connecting to 3G Networks]]'''

* '''Ho do I do a web update of a device ? Please see [[FW Update]]'''

* '''[[How do I set the device back to factory defaults ?]]'''

* '''How do I perform a "Serial Rescue" of the device if it becomes unreachable ? Please see [[FW Update]]'''

* '''[[How do I get the "status page" of any device ?]]'''

* '''[[What if the device is still unreachable after a serial rescue ?]]'''

* '''[[The device already has a password either I don't remember or I don't know, how do I erase it ?]]'''

* '''[[What is SonicIP?]]'''

*'''SonicIP Voice - can I change this and record my own ?''' Yes, to do so follow this [[SonicIP Howto]]

* '''[[What is AutoIP, IPzator, etc.and how do I use them?]]'''

* '''[[Do the Barix products support Multicast and IGMP ?]]'''

* '''[[Do the Barix products support IPv6 ?]]'''

* '''[[I want to set up a local network with more than 250 devices, what do i have to do ?]]'''

* '''[[I want to do a broadcast over different subnets, is that possible ?]]'''

* '''[[Which port/s do your devices commonly use ?]]'''

* '''[[What does RTP stand for ?]]'''

* '''[[AND what does BRTP stand for ?]]'''

* '''[[How much latency should I expect in an Instreamer/Exstreamer setup using BTRP ?]]'''

* '''[[How do emergency messages work ?]]'''

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ykepuqy.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=
----
=[http://ykepuqy.co.cc CLICK HERE]=
----
</div>

== Audio FAQ ==

=== Questions related to audio formats in general ===
* '''[[What is the difference in using PCM MSB and PCM LSB?]]''' (e.g. in the STL application)

=== Instreamer/ Encoding related questions ===

* '''[[How are measured Input Peak Levels]]'''

* '''[[Can the Instreamer also encode WMA ?]]'''

* '''[[Can the Instreamer also encode AAC+ ?]]'''

* '''[[What kind of streams does the Instreamer produce ?]]'''

* '''[[May I configure the stream EXACTLY at 64 kps (or some other value) on Instreamer 100 ?]]'''

* '''[[How much bandwidth do I need to stream audio ?]]'''

* '''[[How many destinations can I stream to ?]]'''

* '''[[I have set up multiple shoutcast destinations on my Instreamer. Can I use different passwords for different streams?]]'''

* '''[[How do I set the Instreamer to feed streaming audio to a stream hosting company ?]]'''

* '''[[I want to play the stream of an Instreamer with Windows Media Player, but it does not work]]'''

* '''[[Is there a way to connect to the Barix Instreamer directly? We would like to get the audio from the device with as little lag as possible.]]'''

* '''How do I configure a Instreamer-Exstreamer audio connection within the same LAN ?''' Please read the [[Instreamer-Exstreamer How To]] guide.

* '''How do I configure a Instreamer-Exstreamer audio connection over the Internet (known as STL connection)?''' Please read the [[STL connection over Internet]] guide.

* '''When using the Instreamer 100 to encode / feed a Shoutcast Server, how do I insert Artist / Title / Station-name text ?''' Please read [[how to send metadata]]

* '''[[Can i distribute IP Audio over a SCA channel with an Instreamer ?]]'''

=== Exstreamer related questions ===

*'''[[How to use the Exstreamer 1000 as a PCM STL]] ?'''

*'''[[How do I play an AAC stream? What version of AAC do you support?]]'''

*'''How do I know what the LED blinking means ?''' Please find that information in the "Exstreamer Technical Manual". (Faster [[Green and Red LED]])

*'''[[Can I download audio files from a remote server to be played ?]]'''

*'''[[How do I configure the Exstreamer 100 to play files from a flash drive attached to the USB port when the Internet goes down ?]]'''

*'''[[How do I stream from a PC to an Exstreamer ?]]'''

*'''[[How can I monitor an Exstreamer ?]]'''

*'''What is the capacity of contact of the relay in an Exstreamer-1000 ?''' 24V - 0,5A

=== Annuncicom related questions ===

* '''[[Can I build an intercom system with Annuncicom?]]'''

* '''What are the ratings for the relay on the Annuncicom ?''' The ratings for the relay are: max 50V/1A

* '''[[Does the Annuncicom feature SIP functionality ?]]'''

* '''[[Is an Annuncicom 100 with standard firmware able to receive audio using RTP protocol ?]]'''

* '''[[How do I use the Annuncicom with Sureview Immix ?]]'''

=== IPAM related questions ===

* '''[[What is the difference between IPAM 200 and IPAM 300?]]'''

== Control FAQ ==

=== X8 related questions ===
* '''How do i update an X8 with the latest firmware ?''' You need a Barionet to do this. Please read a detailed howto [[X8-Update]]

=== Barionet related questions ===
* '''[[How do i read an I/O register using SNMP ?]]'''
* '''[[What is the typical Barionet Power Consumption ?]]'''

Back to [[Main Page#Support - FAQ & Troubleshooting]]

Windows Media streaming

2010-11-15T08:01:01Z

Yhorebapemy:

>== About Windows Media ==
[[wikipedia:Windows Media|Windows Media]] is a format for lossy audio and video transmission by Microsoft. The audio format is known as [[wikipedia:WMA|WMA]] (file extension .wma).

In streaming WMA is transferred over a protocol called [[wikipedia:Microsoft Media Server|MMS (Microsoft Media Server)]].

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ezoralihiku.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=
----
=[http://ezoralihiku.co.cc CLICK HERE]=
----
</div>

== MMS disambiguation ==
The name [[wikipedia:Microsoft_Media_Services|MMS (Microsoft Media Server)]] is a bit confusing as it is often used to describe different protocols.

There are three protocols often called as MMS based on a similar protocol: '''MMS over HTTP''', '''MMS over TCP''' and '''MMS over UDP'''.

The Streaming Client supports MMS over TCP and MMS over HTTP. For these protocols the following URL prefixes are commonly used: '''http://''', '''mms://''' and '''mmst://'''

For even more confusion the '''http://''' prefix is widely used for [[wikipedia:Shoutcast|Shoutcast]] streams.

The following table explains the URL prefixes used by the Streaming Client:
{|border="1" cellpadding="5" cellspacing="0"
|-
|'''Protocol'''
|'''Prefix used by the Streaming Client'''
|'''Commonly used prefix'''
|-
|MMS over HTTP
|mms://
|http://
|-
|MMS over TCP
|mmst://
|mms:// or mmst://
|-
|Shoutcast
|http://
|http://
|}

== MMS in the Streaming Client ==
The Streaming Client is the only Barix software supporting WMA and MMS. At the time the Streaming Client was developed the MMS protocol was proprietary and the only way to implement a non-Microsoft player was to reverse-engineer the protocol. In February 2008 Microsoft deprecated the MMS in favor of RTSP and released the MMS specifications to the public.

=== Limitations ===
The Streaming Client implementation still uses the reverse-engineered protocol and therefore is not 100% compatible with all servers. The Streaming Client supports audio-only streams (some streams are mixed video and audio) and only streams with one bitrate (some servers send multiple bitrates in the same stream).

=== Which hardware to use ===
WMA and MMS can be played only on VLSI codec based Barix products, i.e. Exstreamer 100, 110 and 200.

=== Which version of the Streaming Client to use ===
The Streaming Client branch 1.x supports MMS and WMA. Use the latest version of this branch.

In September 2008 in Streaming Client version a1.52 there has been an improvement in the MMST (MMS over TCP) parser which allows to play more MMST radio streams. If you have difficulties with playing MMST streams make sure that you are using Streaming Client version 1.x after September 2008.

Starting with version 2.0 of the Streaming Client MMS support has been removed for space reasons. However, the Streaming Client 2.x still can play WMA files, e.g. off the USB stick.

== Shall I use MMS or MMST? ==
*If you get a URL use the above table to select the proper protocol in the Streaming Client.
*Most Windows based internet radio servers stream in MMS over HTTP. Try this option first.
*Most servers also provide both MMS over HTTP and MMS over TCP, but it is not automatically used in all cases (must be enabled on the server). If you own the server and can configure it, allow both options.
*If MMS over HTTP does not work or you experience problems try MMS over TCP and vice versa. However, MMS over HTTP should be more reliable.

== Playlists ==
WMA files and Windows Media streams are often stored in ASX playlists. The ASX file format is XML based.

If you get a link to an online Windows Media radio station from the internet, most likely it will be in ASX.
Streaming Client does not support ASX and therefore to play such radio stations some extra simple "handwork" must be done.

Below is an example of an ASX file as it appears in a text editor:

<pre>
<ASX VERSION = "3.0">
<entry>
<DURATION VALUE="01:00:00" />
<ref href = "mms://stream.kcdx.com/KCDX" />
<ref href = "rtsp://stream.kcdx.com/KCDX" />
<ref href = "http://stream.kcdx.com/KCDX" />
</entry>
</asx>
</pre>

As you can see, it is fairly simple to find the URL of the stream. It is stored in the '''<code><ref /></code>''' elements. Usually several sources are available, in this case (in the order as they appear) MMS over TCP, RTSP and MMS over HTTP. To play the stream in the Streaming Client extract the URLs and enter them on the WEB UI or store them into an M3U playlist.

Do not forget to convert the prefix to the right format compatible with the Streaming Client.

The converted URLs from the above example will be:
<pre>
mmst://stream.kcdx.com/KCDX
mms://stream.kcdx.com/KCDX
</pre>

RTP

2010-11-14T22:57:19Z

Yhorebapemy:

>=== RTP Protocol===

[[wikipedia:Real-time Transport Protocol|RTP (Real-time Transport Protocol)]], as a standard application protocol of the [[wikipedia:Internet Protocol Suite|Internet Protocol Suite]], has been designed for transport of multimedia streams in IP networks.

Implementation is widely based on the [[wikipedia:User_Datagram_Protocol|User Datagram Protocol (UDP)]]. The [[wikipedia:Transmission Control Protocol|Transmission Control Protocol (TCP)]] is not often used by RTP for its high latency caused by connection establishment and error correction. The Barix implementation employs UDP as a transmission protocol.

In multimedia applications low latency is essential, whereas an occasional packet loss can be tolerated. A packet typically carries a fraction of a second worth of audio, which makes the lost packet almost inaudible. RTP adds a sequence number and a time stamp to each packet to allow detection and recovery from network errors.

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ikewahibys.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
----
=[http://ikewahibys.co.cc CLICK HERE]=
----
</div>

===Payload Type===

Each RTP packet carries 7-bit information describing the type of the media data - so called payload type. For most common audio and video formats standard payload types are defined. The non-standard types have to be negotiated by the communicating parties by other means/protocols (e.g. using the Session Description Protocol SDP). For that reason a range of dynamic payload types is reserved.

The following table shows the defined RTP payload types used in Barix firmware.
Note that Payload types 0, 8, 10, 11 and 14 are defined by the RTP standard while types 96 to 112 (dynamic payload types) are Barix specific.

{| class="wikitable" border="1" cellspacing="0"
! <center style="background-color:#FFB6C1">RTP payload type</center>
! <center style="background-color:#FFB6C1">Audio Format</center>

|-
| <center>0</center>
| μ-Law, 8bit, mono, 8kHz

|-
| <center>8</center>
| A-Law, 8bit, mono, 8kHz

|-
| <center>10</center>
| PCM 16bit, MSB first, signed, 44.1kHz stereo, left channel first

|-
| <center>11</center>
| PCM 16bit, MSB first, signed, 44.1kHz mono

|-
| <center>14</center>
| MPEG audio

|-
| <center>96</center>
| PCM, 16bit, MSB first, signed, 8kHz mono

|-
| <center>97</center>
| μ-Law, 8bit, mono, 24kHz

|-
| <center>98</center>
| A-Law, 8bit, mono, 24kHz

|-
| <center>99</center>
| PCM, 16bit, MSB first, signed, 24kHz mono

|-
| <center>100</center>
| μ-Law, 8bit, mono, 32kHzreserved

|-
| <center>101</center>
| A-Law, 8bit, mono, 32kHzreserved

|-
| <center>102</center>
| PCM, 16bit, MSB first, signed, 32kHz monoreserved

|-
| <center>103</center>
| PCM 16bit, MSB first, signed, 48kHz stereo, left channel first

|-
| <center>104</center>
| PCM, 16bit, LSB first, signed, 8kHz mono

|-
| <center>105</center>
| PCM, 16bit, LSB first, signed, 24kHz mono

|-
| <center>106</center>
| PCM, 16bit, LSB first, signed, 32kHz monoreserved

|-
| <center>107</center>
| PCM 16bit, LSB first, signed, 44.1kHz stereo, left channel first

|-
| <center>108</center>
| PCM 16bit, LSB first, signed, 48kHz stereo, left channel first

|-
| <center>109</center>
| μ-Law, 8bit, mono, 12kHz

|-
| <center>110</center>
| A-Law, 8bit, mono, 12kHz

|-
| <center>111</center>
| PCM, 16bit, MSB first, signed, 12kHz mono

|-
| <center>112</center>
| PCM, 16bit, LSB first, signed, 12kHz mono

|-
| <center>127</center>
| Generic (see below)

|}

===Sequence Number===
is primarily used to identify and detect lost packets and secondly to reconstruct the order in which packets where sent, which may make loss detection easier;

===Time Stamp===
is the sampling instant for the first octet of media data in a packet. It can be used to help recover the clock frequency at the receiving side, if it is not given by other means.

===References===
Check the Wikipedia for an introduction to the RTP protocol [http://en.wikipedia.org/wiki/Real-time_Transport_Protocol].