Hey Everyone,
We noticed some unexpected behaviour when it came to fallback streaming with MistServer. MistServer would properly send viewers to the fallback stream, however it would never send them back to the original source if that became available again. So any viewers would need to refresh/reload the stream in order to get to the original stream. Not the biggest of problems as reloading the stream isn't too difficult to trigger, however it's still not wanted behaviour. This should be fixed within our development builds by the time this post should come online.
As some additional information to provide here, within MistServer fallback streams are meant for viewers only & will always provide the stream to the viewer in the following order priority:
Source > Protocol specific fallback > Stream-specific fallback > Server-wide fallback > Stream unavailable message
The guide is available here