| View previous topic :: View next topic |
| Author |
Message |
Anonymous
Guest
|
 Posted: Fri Jun 09, 2006 1:50 pm Post subject: fallback-override issue |
 |
|
Hello.
According to the docs for icecast 2.3.1:
| Quote: |
fallback-override
When enabled, this allows a connecting source client or relay on this mountpoint to move listening clients back from the fallback mount.
|
All the mountpoints on my server (running icecast 2.3.1) have /fallback.ogg set as the fallback mountpoint and fallback-override enabled.
When I am listening to a stream and then it stops streaming, I correctly get dropped to /fallback.ogg . When the stream I was listening to reconnects it doesn't move me back to it but it moves me back to a random mountpoint instead.
My understanding is that because of fallback-override it should move me back to the mountpoint I was listening to, which makes sense, although the current behaviour sounds like it's moving me back to the mountpoint that connected immediately after I got moved to the default mountpoint, which doesn't make sense.
I hope I didn't confuse anyone. 
Any suggestions or explanation please? |
|
| Back to top |
|
 |
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Sat Jun 10, 2006 1:16 am Post subject: |
|
|
We can only guess at your situation, but there is definitely no random selection here. If you have a cascading fallback eg A -> B -> C then it will be dependent on whether A or B reconnects first. If you want to isolate certain listeners on one mountpoint from others then introduce local relays eg A -> C and B -> D where C and D are relays (on-demand is ok) of E (the fallback stream). With that you isolate listeners based on the mountpoint selected but they see the same fallback with little overhead.
karl |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
