IP STL codecs
Send and receive levels on both channels, path delay, WAN in and out, errors and ping.
Open the STL demoIP codecs, RF STLs and remote codecs carry the program to the transmitter. BNM reads both ends — levels, path delay, jitter, loss and link state — so a link that’s getting worse shows up before it drops.
Illustration: jitter and packet loss climb on the IP path to the transmitter site, BNM emails and texts, then the site codec stops answering and BNM calls the on-call list until someone acknowledges.
Send and receive levels on both channels, path delay, WAN in and out, errors and ping.
Open the STL demoForward and reflected power and VSWR on the STL transmitter, with the receiver at the other end of the hop.
Whether the link is connected, audio present on it, and the dropout history.
The encoders feeding your streams and STLs, watched alongside the rest of the chain.
Every codec’s link, packet loss, jitter, round trip and bit rates, a 24-hour audio level history, emergency audio and the relay board.
More on AirCodecPick which readings raise an alert and how loud. A short blip gets logged; a link that’s really gone calls your phone.
Recovery is logged too — you see when the link came back and how long it was down.
Most monitoring only asks a Barix whether it answers ping, and a Barix keeps answering long after its stream has stopped. BNM reads the stream itself and calls you the moment it stops.
Tell us how your stations are fed. We’ll point a demo at both ends of your STLs and wire a test call to your phone.
IP codecs, Barix boxes, RF STLs and remote codecs carry the program to the transmitter. BNM reads both ends — levels, path delay, jitter, loss and link state — so a link that’s getting worse shows up before it drops.
Illustration: jitter and packet loss climb on the IP path to the transmitter site, BNM emails and texts, then the site codec stops answering and BNM calls the on-call list until someone acknowledges.