Feed drops out

[KokomoScanner]

I am also on audio1.radioreference.com now.

 

[Chrome69]

Well i am getting fed up with it, to the point of shutting down my feed. It just happened again 3 minutes ago and this time it knocked 27 listeners offline. Tired of complaining into deaf ears!

I'd send another help ticket in but i will get the same reply as the other times. Its probably your modem so try using Ping Plotter or they will switch the audio sever yet again. BTW i replaced my modem with a new one and same deal. Switched from a Motorola to Thomson and the same thing! Really!

 

[KokomoScanner]

I am sorry to hear that, i hope they can get you fixed up.

 

[Chrome69]

Thanks for all the support Broadcastify and Lindsay! 80 listeners just got booted from my feed!

 

[GordonE]

The problem's not on our end, if it was everyone on the server you're connected to would be affected. The fact that the problem happens no matter which audio server you're connected to also indicates that the problem isn't on our end.

 

[Chrome69]

And yet the second feed is online and running fine, wanna explain that one!

 

[GordonE]

My guess is that there's a problem on your end which is preventing the computer you're using from providing the audio for two feeds.

 

[Chrome69]

Well Gordon please remove both my feeds as i am done with it! I am not spending any more money or switching ISP!

 

[GordonE]

Both feeds will be removed automatically after they've been offline for 3 weeks.

 

[Chrome69]

one is a TAC feed so it wont be automatically removed.

 

[GordonE]

one is a TAC feed so it wont be automatically removed.

Thanks, I fixed it (so that it's no longer marked as being a tactical feed).

 

[Chrome69]

Thanks, I fixed it (so that it's no longer marked as being a tactical feed).

Yup your good at that, don't solve the real problem. :roll:

 

[Chrome69]

K I will try another computer on the peel police feed... This is really driving me nuts...

 

[KokomoScanner]

Ok, i had a big disruption this morning. I really do not know what i am looking at in the pingplotter software? Help??

The problems you're having aren't associated with any of the audio servers, they're all three running identical software, are on the same network, and none are anywhere near capacity.

Most likely the problem exists somewhere along the network path between your computer and our servers. The majority of the time the problem is with the volunteer's cable or DSL modem even when you don't notice other problems related to your connection due to the fact that your connection to our server will drop if there's anything more than a small interruption in the flow of audio data.

I usually recommend that people download the trial version of Ping Plotter and have it ping one of our audio servers, then, when the problem happens again, take a look at the information it recorded to determine where along the network path your connection is being interrupted.

 

[Eng3ineer]

KokomoScanner, I've had issue this morning as well and was wondering myself as just started using ping plotter.

I'm not 100% but this is a screen shot of ping plotter to audio9 that I just did. From reading i'm figuring that the numbers 1-12 is the number of steps it takes for your feed/data sent to get to the radio reference server. So in looking at this it appears my problem is around the Dallas,Tx area. seeing how it's showing ERR and the long red line.

Hope this helps as not 100% myself. Hopefully will get the right answer soon

 

[KokomoScanner]

This is what i had, went away on its own. Knocked about 90 listeners off.

 

[Eng3ineer]

Going by what Gorden said a few post back about the red lines. I'd say looks like the problem starts very close to your end. Using my photo as reference and as I know what I have hooked up in series. I'm think my #1 is my hard wired router. #2 My DSL modem from the phone company #3 No Clue ( Maybe the good size Junction box about mile down road) #4 & 5 is my phone company DSL #6 No clue and then the rest are in Dallas.

So i'm thinking whatever #2 starts the process and it snowballs from there. I'd look at your router or modem to start.

Sorry can't be more help, but i'm just learning this ping stuff myself.

 

[GordonE]

Going by what Gorden said a few post back about the red lines. I'd say looks like the problem starts very close to your end.

Correct, in KokomoScanner's image I can see that the problem was definitely between 10.0.0.1 (which is probably your cable or DSL modem) and the network device it communicates with (which is probably a piece of network equipment owned by your ISP which is at the street or in your neighborhood).

I could tell this by seeing at what point every single hop was failing.

Using my photo as reference and as I know what I have hooked up in series. I'm think my #1 is my hard wired router. #2 My DSL modem from the phone company #3 No Clue ( Maybe the good size Junction box about mile down road) #4 & 5 is my phone company DSL #6 No clue and then the rest are in Dallas.

#2 is most likely not your DSL modem but is probably a piece of network equipment owned by your ISP (based on the fact that it's IP address resolves to a hostname which includes their domain name).

In your case, PingPlotter doesn't help in locating where the problem is. It's mostly useful when there are cases where the graph at the bottom of the screen contains red lines (like in KokomoScanner's image) and indicating that ping packets sent to our server weren't returned. Anytime you see those red lines and they represent more than 30 seconds or so of packet drops, that's enough to cause your audio feed to drop.

The fact that a couple of routers along the path didn't return 100% of the pings that were sent to them can be ignored, they key is whether or not pings sent to our servers didn't make it. When ping's don't make it to our server, use the graphs to see at what point along the path pings stopped getting returned. When doing this, it helps to double-click on the different rows in the table to add additional graphs to the bottom of the screen (indicating the ping times for each node).

 

[KokomoScanner]

Seeing as it corrected its self, guessing Cable Modem? This assumption based on it doing it on 2 separate computers. One is hardwired, other is wireless. Both did it.

 

[GordonE]

That's my guess (unless your ISP had a problem with the device at the street).