G
Guest
We use many WMS 4.1 boxes to multicast streams with. My
question is about the unicast rollover URL in the .nsc
station definition file. When we provide a unicast URL to
rollover to in the event of mulitcast issues, it only
works if the station is 'playing' / green and working. If
the unicast source stream to the station stops for any
reason we are hosed all around...is this behavior
normal/designed? It looks like everything depends on that
source stream for the station to do anything at all. Any
info is appreciated - thank you!
Also, I have a devilishly hard problem with WMS 4.1
multicasting.
Does anyone know if there is a way to make source streams
(unicast pulls from other servers) redundant? We keep
getting hosed because of unwanted 'stops' telling us the
network connection has failed (even if it has not).
Pressing 'play' again always corrects the problem but the
multicast stream is down until 'play' is pressed manually
again. Is there a known bug that I can not find in the
KB? Out of ideas on this one....yes layer 3 is SOLID -
this is not a network issue - monitoring and continuos
pings have proved that. Station stops randomly it
seems....help! Thanks!
question is about the unicast rollover URL in the .nsc
station definition file. When we provide a unicast URL to
rollover to in the event of mulitcast issues, it only
works if the station is 'playing' / green and working. If
the unicast source stream to the station stops for any
reason we are hosed all around...is this behavior
normal/designed? It looks like everything depends on that
source stream for the station to do anything at all. Any
info is appreciated - thank you!
Also, I have a devilishly hard problem with WMS 4.1
multicasting.
Does anyone know if there is a way to make source streams
(unicast pulls from other servers) redundant? We keep
getting hosed because of unwanted 'stops' telling us the
network connection has failed (even if it has not).
Pressing 'play' again always corrects the problem but the
multicast stream is down until 'play' is pressed manually
again. Is there a known bug that I can not find in the
KB? Out of ideas on this one....yes layer 3 is SOLID -
this is not a network issue - monitoring and continuos
pings have proved that. Station stops randomly it
seems....help! Thanks!