YP mixing me up with another Station

[hot977]

Hey guys, ok now. my stream is getting mixed up with another station. If you search for me Hot 97.7 I sometimes come up, but also 96.3 Vip is showing my stats with his. Also sometimes clicking on his listen live will go to my station. We have the same database center but our ips and ports are different.

96.3 VIP IP : http://216.59.35.39:8030/

Hot 97.7 (Mine) http://216.59.35.35:8028

Does anyone know of a fix for this? Please advise

[dotme]

We've heard of this issue before, but without the additional detail you provided. The fact that both stations are in the same DC makes me wonder if that DC is using a firewall that makes all outbound traffic/requests appear to come from the same IP. Can you ask them?

[SnowHow]

This is happening to me also. My station is being mixed with a Spanish music station and I an having to manually direct traffic from one server to another to prevent my listeners from being directed to the Spanish station.

My setup is:

Source -> (main) 74.50.106.82:9725 -> (backup) //:9731 and //:9739

The spanish station is completly different:

64.120.141.178:6443

Here is the most recent shoutcast log from my source server:

09/13/10@10:26:19> [yp_tch] new backup server 64.120.141.178:8443
<09/13/10@10:26:19> [yp_tch] yp.shoutcast.com touched!
<09/13/10@10:36:20> [yp_tch] new backup server 64.120.141.178:8443
<09/13/10@10:36:20> [yp_tch] yp.shoutcast.com touched!
<09/13/10@10:40:31> [dest: 207.105.138.226] starting stream (UID: 3931)[L: 4]{A: WinampMPEG/5.57, Ultravox/2.1}(P: 0)
<09/13/10@10:41:21> [dest: 79.224.46.64] starting stream (UID: 3932)[L: 5]{A: WinampMPEG/5.50}(P: 3)
<09/13/10@10:43:51> [dest: 79.224.46.64] connection closed (150 seconds) (UID: 3932)[L: 4]{Bytes: 1081344}(P: 3)
<09/13/10@10:46:21> [yp_tch] new backup server 64.120.141.178:8443
<09/13/10@10:46:21> [yp_tch] yp.shoutcast.com touched!
<09/13/10@10:56:22> [yp_tch] new backup server 64.120.141.178:8443
<09/13/10@10:56:22> [yp_tch] yp.shoutcast.com touched!
<09/13/10@11:06:22> [yp_tch] new backup server 64.120.141.178:8443
<09/13/10@11:06:22> [yp_tch] yp.shoutcast.com touched!
<09/13/10@11:16:23> [yp_tch] new backup server 64.120.141.178:8443
<09/13/10@11:16:23> [yp_tch] yp.shoutcast.com touched!
<09/13/10@11:26:24> [yp_tch] new backup server 64.120.141.178:8443
<09/13/10@11:26:24> [yp_tch] yp.shoutcast.com touched!
<09/13/10@11:36:24> [yp_tch] new backup server 64.120.141.178:8443
<09/13/10@11:36:24> [yp_tch] yp.shoutcast.com touched!
<09/13/10@11:46:25> [yp_tch] new backup server 64.120.141.178:8443
<09/13/10@11:46:25> [yp_tch] yp.shoutcast.com touched!
<09/13/10@11:56:25> [yp_tch] new backup server 64.120.141.178:8443
<09/13/10@11:56:25> [yp_tch] yp.shoutcast.com touched!
<09/13/10@12:06:26> [yp_tch] new backup server 64.120.141.178:8443
<09/13/10@12:06:26> [yp_tch] yp.shoutcast.com touched!
<09/13/10@12:16:26> [yp_tch] new backup server 64.120.141.178:8443
<09/13/10@12:16:26> [yp_tch] yp.shoutcast.com touched!
<09/13/10@12:26:27> [yp_tch] new backup server 64.120.141.178:8443
<09/13/10@12:26:27> [yp_tch] yp.shoutcast.com touched!


My servers are not showing up for redirection at all. What could be causing this?

Thanks!
SnowHow
A-1 Radio - The Variety Channel
www.a-1radio.com

[SnowHow]

Sorry for bumping an old topic, but we figured out what was happening in our case and I would like to share our story so that other broadcasters can watch out for what we found:

What was happening was that another website had been relaying our stream with their server. They had set their server to "public" and the Shoutcast Directory grouped their server with ours as a backup server.
If that wasn't bad enough, it got worse from there. They eventually stopped relaying our stream with their server and started broadcasting Spanish language music with it, but the Shoutcast directory still had us grouped together so that when the main server got full and looked for a backup to hand off to, if their server was up in the rotation, our listeners would be connected to their server.
We tried everthing we could think of to shake this server from our rotation including changing our bitrate, going "private" for extended periods (which meant we had to manualy monitor and redirect traffic from server to server), pointing an encoder directly at the first server, changing IP's from where the encoder originated, shuffling which server was the primary and which were backups, and no matter what we tried, the Shoutcast Directory (yp.shoutcast.com) INSISTED on grouping their server with ours.
We finally rid ourselves of it by abondoning the servers we had and getting new ones. We also had to have our host provider delete those servers because they had been hopelessly "contaminated" by the unwanted server and we had to reconfigure our source server to a different port to get rid of it.

After going through all of that, I am left with the thought that if this could happen to us, then this could happen to anyone, so that begs the question -- Is there a way to disassociate yourself from a server like this in the above scenario? Why would the Directory continue to group servers together like this even if they are no longer relayed off of each other? Is this an intentional part of the design of the Shoutcast Directory or is this a bug?

In any event, if you are a broadcaster, pay close attention to your logs and ACT IMMEDIATELY if you find an unauthorized server connected to your server by kicking and banning the IP and hope the Directory didn't group you with that server or else you will probably have to go through what we did.

Hope this helps someone --

SnowHow
A-1 Radio