[EAS] EAS: Pinging remote computers

[Greg Folk]

It sounds like you are trying to do what I am using "Is It Up" for 
http://www.tarosoft.com/

I monitor my transmitter site, remote studios, and the main studio from 
my home network and receive an email when a device fails to respond.
I have setup a device on each network that will respond to pings (a 
Barix, a computer, on is some cases the router) and point the program to 
those.
In my case every network is on a static IP, but I believe you can point 
the program to a URL and use something like DynDNS (not so free anymore)

It does use ICMP and is simple, but it works for monitoring 
network/internet up/down status.

Greg

Greg Folk
KTHO Radio
South Lake Tahoe, CA

On 5/8/2013 06:34, Richard Rudman wrote:
> Hi, Neil:
>
> Thanks for chiming in on this.
>
> This is geared towards checking reliability of IP connectivity at remote sites, not for pinging IPAWS. While there is nothing in PArt 11 that requires broadcasters to check this, it seems to many of us that without knowing for sure that an IP connection is up, we cannot truly fulfill the Part 11 mandate for IPAWS OPEN polling for FCC inspection/compliance purposes.
>
> This is not usually seen as a problem if an EAS box is located at a studio and polls IPAWS over a connection that is in use for business purposes. At remote sites, a version of the old Zen "tree falling" line comes into play: What is the sound of a remote IP connection going down when no one is there to hear it?
>
>   Now that your team is providing the EAS community with good information, pinging IPAWS OPEN is not an issue.
>
> Thanks,
>
> Richaerd
>