incorrect url using SC_Serv 2.2.2

[WizardX]

Hi there,

I run the following setup:

samcast encoders -- old 1.9.8 server (private) for internal distribution -- shoutcast2 as a relay.

The icy-url on the old internal distribution servers are okay, but within shoutcast2 I see the following:

http://deep.fm/inux
and
http://deep.fm/inux</port></url><id>690219</id><authhash>ksaf7syheahhjga9vzip</authhash></cmd></yp

I don't know if this is authhash or shoutcast2 related problem but my Directory ID is: 66131 (128kbit mp3) and 544294 (320kbit mp3) and 674798 (64kbit aacp)

Thanks in advance
Vince

[DrO]

what am i meant to be looking at? what is actually wrong?

and as the authhash has been publically posted, i've now had to delete it as it's deemed compromised.

[WizardX]

The url should be http://deep.fm/ and not all the other stuff which is placed behind the trailing slash

[DrO]

see my comment in the other thread you'd also posted in on what to do until it can be triaged.

[WizardX]

Generated 3 new hashes and will update the config with the advise you gave us. Thanks! By the way, the DNAS is running actually very good. Could be a little bit better concerning CPU usage, but we have quite big machines, so for now no worries and the 2.2.2 runs in production. (Didn't I mention I'm happy with the new build?)

[DrO]

better CPU usage in what way? as compared to the early 2.0 beta builds its already a lot better than it was - there might be some extra room for optimisation but it's unlikely to be anything dramatic (especially as it can all vary between different setups, OS versions, bit-compiles, etc).

[DrO]

it seems like this is something which has gone wrong with the creation of the authhash which relates to the change over to use libcurl in the 2.2.2 release (which has also caused a few other minor problems).

as the issue is just affecting the website value from what i can tell (due to it generally being the final parameter received), it is most likely going to require any authhash affected to be updated (either manually or with a newer fixed DNAS release).


so what i've suggested should just be temporary measures before the next update is released.

and i'm also going to look to filter out such problem values from the YP side which will mean that what is returned when the DNAS is running normally will most likely end up being the default of 'shoutcast.com' whilst any affected values are fixed prior to a DNAS update.

[WizardX]

UPDATE: I got it fixed by streaming directly from encoder to shoutcast2 server and not via an old shoutcast 1.9.8 "hub" server.

I suggest it might reside in the relay part of the code.

Anyways our problems are solved for now

[DrO]

even with the configuration change? as relayed metadata is not messed with when pulled from the source, it is only on the transmission to the clients that it is provided or not (as per that configuration option).

[WizardX]

The metadata in the player got the right information during the previous setup. The way shoutcast presents the url in the interface was just incorrect and the way it was being used by the streamredirect options.

[DrO]

that's not making much sense to me.