I had a BUNCH of disconnects recently, too. I think it was on the 30th??
Short Answer:
I'm pretty sure (not certain, mind you, but pretty sure) that ScannerCast is working as designed.
Long Answer (WHY I said the above):
In order to successfully get audio data from your radio to RR's Icecast server, ScannerCast establishes a network connection to the RR Icecast server. ScannerCast then sends packets of data containing your scanner audio and tags (usually, about two per second) to the Icecast server. Anything between ScannerCast and the RR Icecast server that results in excessive loss or delay or damage to a packet on its journey will cause the network connection to have to resend the data.
Too many re-transmissions will result in the connection being "reset" -- ScannerCast detects that the remote connection has gone away and periodically attempts to re-establish the connection.
Remember, the network problem (heavy traffic, some dummy with a backhoe, temporary EMI) can be anywhere along the path between your computer and the RR Icecast server (wherever it's located). Or it could be at the RR Icecast server itself (LOTS of people suddenly connecting... Gordon or Lindsay restarting the server).
I know that's a lot of details... but the bottom line is: It's not at all unusual, in my experience, to see periods of time where the connection "bounces" for a while. As long as the connection returns to stability after a reasonable period of time (say, an hour or two) and then stays up for a reasonable period of time
Thanks for using ScannerCast and I hope the above helps explain what I think was going on,
Peter
K1PGV
