I can get the “video”, “video-source” , “video-audio” streams using all protocols.
But behind the scene something strange happens when I call “video” and “video-audio” using RTSP or RTMP
It works showing the expected content o the player, but Wowza keeps a MediaCaster instance “video” or “video-audio” trying to connect a stream source. I can see it because Mediacaster events I am logging and because of logging I have in resolveStreamAlias. As this method do not have a valid replies for “video” and “video-audio” I return the name (I’ve tried return null too). it causes logs of MediaCaster connectFailure.
As the the streams named “video” and “video-audio” are already running correctly (I can see it through the player and WowzaStreamEngineManager), it should not start the MediaCaster, right?
Using HLS protocol something similar happens, but instead start a media caster I get successive calls on resolvePlayAlias.
Here is a resume of my logs:
- After start video-source on App
- After connect video-source using RTSP or RTMP client - THIS STREAM RUNS AS EXPECTED
but then no data being send to it. This will be why it is constantly trying to reconnect. If there is no data, then Wowza will drop the connection and reconnnect, it may be doing this as the stream is empty.