Icecast Streaming Media Server

[kai4711]

Hey guys,

I have a problem with a fallback-mount. When the "normal" mount is started all listeners of the fallback mount (and not only that listeners which came from the "normal" stream) are put back to the "normal" stream.

The detailed situation:

I have a fallback-mount called /fallback.mp3 which gets 24h music from a ezstream-instance on the server.

I have a "normal" stream-mount called /stream.mp3 with "Fallback-override" activated.

The /fallback.mp3 is relayed by another server which uses it as fallback, too, but for a totaly different programm.


The problem:

When stream.mp3 comes back every listener which is on fallbackmp3 gets switched to stream.mp3 not only that ones which came via stream.mp3 (and hear that as fallback.).
So ie. the relaying server gets the stream.mp3 programme and not the fallback-programm ....
But when someone points to the /fallback.mp3 when /stream.mp3 is active than he hears the /fallback-music.

So I think its definitely a ovveride-problem....
Is there a solution?

Thank you guys,
Kai

[karlH]

If A and B both fallback to C then any override will kick in at the time the stream kicks in. If you want to isolate listeners from an override then setup a local relay of C, lets say D. Now A fallback/override D, D is a relay of C and B still relays C without any issue of being moved. All listeners will be kept on A or D and won't be confused with the relay B. I'm guessing you don't want C or D to be a publically advertised point of access for listeners.

karl.

[kai4711]

local relay really with the relay-function and ie localhost as host?
Not alias or something like that?


So I understand right, I open a fallback-source mount ie B and for every mount ie A a second fallback mount ie A-fallback which relays B?

If I have a totally different mount C which I want to isolate, then I create a C-fallback which relays B too?

Thank you!

Kai

[kai4711]

Yeah I managed it, but only with a little trick:

You have to set

[karlH]

Relays are rechecked every 2 mins by default but you are right in that the first relay check will fail as a source client will probably not be connected. With on-demand set it will stop some extra processing when it's not needed as well.

karl.

[kai4711]

Is it possible to change that 2 minutes value?

kai

[karlH]

use <master-update-interval> specified in seconds

karl.