Icecast Streaming Media Server

[Revolution Radio]

I have 10 seperte staions running.
i currently have them all runing on one port with mulitpule mount points but lately ive been getting some very strange bleedover issues - when a staion frt goes live it will bleed into any other staion thats online at the time unless they refreash thier client

what i would like to do is give each staion its own socket/port
assuming it must be something with the ports streams mixing at client side

ive tried adding
<port>7000</port> into each mount point - dosntwork
ive tried the

<listen-socket>
<port>7000</port>
<mount-name>/hackme</mount-name>
</listen-socket>
and i end up with the new port but all staions are on both ports at this point.

not sure what the heck im doing wrong here

id like to be able to do this with out having 10 seeprate insances of ice cast running at the same time on the server

[karlH]

The only time clients can migrate across to another stream is if you are using a fallback/override. If the audio is getting mixed then it is not down to icecast, so the source client is getting that mixed content.

If the issue is because of fallback handling then using separate ports for the stream will not matter.

To answer the specific question posed then you use alias for placing listeners on certain streams based on the port. All icecast-aware source clients provide a mountpoint to stream on, only shoutcast style source clients do not which is why the <shoutcast-mount> setting is used.

Maybe you should describe the layout of your streams and the fallback/override relationship, or at least the intention.

karl.

[Revolution Radio]

<hostname>ipaddress</hostname>
<server-id>Total Truth Brodcasting Network</server-id>
<fileserve>1</fileserve>

<listen-socket>
<port>7000</port>
<bind-address>ipaddress</bind-address>
</listen-socket>

<paths>
<basedir>./</basedir>
<logdir>./logs</logdir>
<webroot>./web</webroot>
<adminroot>./admin</adminroot>
<deny-ip>C:\bans\ban.txt</deny-ip>
<alias source="/" dest="/status.xsl"/>
</paths>

<logging>
<accesslog>access.log</accesslog>
<errorlog>error.log</errorlog>
<loglevel>2</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
</logging>

<mount>
<mount-name>/live</mount-name>
<password>Revradio1</password>
<max-listeners>500</max-listeners>
</mount>

<mount>
<mount-name>/blackwell</mount-name>
<password></password>
<max-listeners>500</max-listeners>
<fallback-mount>/live</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
</mount>

<mount>
<mount-name>/awakened</mount-name>
<password></password>
<fallback-mount>/live</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
<max-listeners>500</max-listeners>
</mount>

<mount>
<mount-name>/blowupthenet</mount-name>
<password></password>
<max-listeners>500</max-listeners>
</mount>

<mount>
<mount-name>/undergroundsounds</mount-name>
<password></password>
<max-listeners>500</max-listeners>
<fallback-mount>/live</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
</mount>


<mount>
<mount-name>/onthepath</mount-name>
<password></password>
<max-listeners>500</max-listeners>
<fallback-mount>/live</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
</mount>

<mount>
<mount-name>/ameriplan</mount-name>
<password></password>
<max-listeners>500</max-listeners>
<fallback-mount>/live</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
</mount>

<mount>
<mount-name>/youradio</mount-name>
<password></password>
<max-listeners>500</max-listeners>
</mount>

<mount>
<mount-name>/unspoken</mount-name>
<password></password>
<max-listeners>500</max-listeners>
<fallback-mount>/live</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
</mount>

[Revolution Radio]

basicaly when anyone that has a fall back set comes on air it grabs the listners on all the stations until the client is refreashed

[karlH]

As I said previously, you have a common fallback for all your streams. So that is expected behaviour. You can isolate the listeners by relaying (on-demand 127.0.0.1) /live to something specific for each stream, eg /blackwell-fallback and you fallback to that mountpoint instead of /blackwell

karl.

[Revolution Radio]

awesome thanks

[Revolution Radio]

is it possible to fall back to another stream?

<fallback-mount>http://1.1.1.1:8000</fallback-mount>

[karlH]

generally no. That sort of fallback could only ever work on a connection start, before any content is sent. There is nothing we can send to a player midstream that will redirect it elsewhere. I do have some code in the kh tree for redirecting listeners in certain cases like when the mount is full (so instead of a 403 response) but I'm unsure of what case you are wanting there.

karl.

[Revolution Radio]

ok
well the basic scenario is i have one 24/7 yalk radio station and
around 15 hobby talk radio staions that are only on aoccasionaly
i have the fall backs cascading down to the /live feed so when the part time staions are off air - they are not dead air
but when ever on the the other stations come on air its grabs all the listners from all the stations into thier mount, until the client is refreashed on the hijacked feed

i tried aliasing /sample.ogg = /shoutcastfeed but that just seems to freak the whole thing out.
im almost possitive im just screwing up the config in some manner, f

[karlH]

As already mentioned, you don't want a common fallback in such cases. You can use a local relay to maintain a mountpoint that isolates fallback listeners.

Yes you cannot assume a player can dynamically switch from one codec to another half way through, that is why intros and fallbacks have to be in the same format and the stream and use similar settings.

karl.