This HTTP test attempts to connect to your stream in the same way that a new listener would. If this test passes, listeners will be able to connect to your stream.
For this check to succeed, an HTTP response code of 200 or 301 must be returned by the streaming server. Note that for Shoutcast 1.x servers, we also accept ICY response headers.
Some reasons why this test could fail are:
If the HTTP test fails, Radio Mast will run further diagnostics to attempt to determine why it failed. The streaming server will be pinged to see if its still accessible from the internet. If it is not accessible, it is likely that the entire server is offline.
If the ping check fails, it could mean:
Radio Mast can also detect silence on your stream, to alert you when you're accidentally broadcasting silence. If several consecutive seconds of silence are heard, this test will fail. This test runs once per minute, and is designed to detect prolonged periods of silence.
By default, the silence detector parameters are as follows:
Recordings of any detected silence are archived and available to be listened to from the stream's "Monitoring" tab.
NEW Adjustable Threshold and Duration
The silence detector can be configured on a per-stream basis from the "Configuration" tab within the Radio Mast interface, with the following options:
To defer alerts until an even longer duration of silence has been detected, edit your Alert Policy and reduce the sensitivity to a longer duration (eg. 10 minutes).
We're looking for ideas for additional tests that we can add to Radio Mast. If you have any specific audio quality checks that your radio station needs, or other ideas, please let us know!