Streams Not Pubishing On Shoutcast Directory

[RadioRookie]

It appears that the stream publications on Shoutcast has been very rocky in the past couple months. Some of our streams are either not publishing at all or they are showing incorrect stream titles. I also noticed a lot of shows in the latest Shoutcast TTSL lists are also showing 0 Tune ins as well. We were on their last month, but the stream name was missing some info.

At any rate, verify why this stream is not being published on the shoutcast directory.

http://s5.voscast.com:7386/index.html?sid=1

Thanks.

[DrO]

there are issues with the ttsl report - what adn why it's indicating 0 tune-ins for a large number of stations i don't know and i won't be able to answer until i'm not on holiday (yet am still having to keep an eye on things here).

as for why the station is not appearing, all i can say is to check the DNAS's logs and look for anything explicitly relating to messages starting with [YP2] as there is nothing in any of my reports relating to the DNAS you've provided a link for despite it indicating that it's got a 'YP connection'.

so i have to assume some error has happened and the DNAS is not able to communicate with the YP but what, i do not know and cannot attempt to check the YP logs at the current time and so you looking and posting back any errors from the DNAS log will make it easier to determine the cause of the issue.


and did http://forums.winamp.com/showthread.php?t=345137 ever get resolved as there was never any reply back...

-daz

[jaromanda]

Inception Radio appears 3 times on shoutcast directory ... 2 x 128kbit MP3, 1 x 64kbit MP3

178.159.0.80:7486
188.165.229.150:35458
208.53.183.150:8118

those three seem to be playing the same as

96.44.147.234:7386/stream/1/ (the one link provided)

so the station seems to be listed, just not that one stream


I'd say there's some sort of conspiracy, but that would be redundant

[DrO]

or it's stemming from the name being different from the authhash but the with the DNAS version being used it hasn't been restarted (or source re-connected) for the change to be applied.

either way it's just us having to guess at things which isn't too helpful for anyone really.

-daz

[RadioRookie]

I don't have access to the logfile unfortunately because the stream providers don't give out that access.

However, I do have to say that the stream was publishing just fine right before I created the post and then it just disappeared after I reconnected from a different source. It's been over 24hrs since it has not published, but one you figure by now that the shoutcast directory should have picked it up. The yp connection would indicate that it should be published and the stream provider said it's out of their hand at this point.

Could this be related to any of the other issues such as the tune-ins not publishing correctly or the fact that even one of my broadcasting streams don't even show the correct stream IDs?

[DrO]

based on what you've said, you would need to contact your host provider and get them to check things on their end as there is nothing i can do from this side of things (especially when the stream is now down as per the status message on the public stream summary page).


one thing that does jump out is you're saying it disappeared after connecting a different source - maybe it wasn't set to be public or there is a configuration issue with your DNAS as in some cases it is possible for the authhash associated with a stream to not be recognised on a source change - though that would require knowing what is in the config file which you don't have access to so we're still at a loss.


but really without anything from logs / input from your host there's nothing specific to say to do as it could be a number of things causing the listing issue (ignoring the stream being stopped at the time of this reply) which i'm sure you're not going to like but there's generally little i can do to see why a station is not-listed without log output.

-daz