Trying to use wowza to stream media between users over RTSP. Found that after exactly 5 minutes, the stream will fail (only via RTSP- RTMP works fine). The relevant error that VLC logs is
“live555 warning: no data received in 10s, eof ?”
Thought that it could be something wrong with our configuration, but the term “300000” does not appear in our configuration anywhere, and most importantly, opening VLC Media Player and playing the wowza example stream results in the same 5 minute failure.
I also found a link describing a similar issue that might be relevant, but it is pretty dated.
I also tried looking at the traffic in wireshark and saw both RR and SR RTCP traffic. But when the five minute mark hits, UDP traffic halts, and ten seconds later I get a “Goodbye” RTCP RR, seemingly with no other relevant traffic before or after. In other words, Wowza stops sending stream data after exactly five minutes, and live555 rightfully shuts down.
In the engine manager, the source stream never stops or goes down. but I see that outgoing connections stop after five minutes. If I set the client up to reconnect, I can see in the engine manager that the outgoing streams goes up and down every five minutes on-the-dot. It is perfectly consistent.
Why is wowza timing out after five minutes? Is it ignoring the RR’s from live555? If so, is this 5 minute timeout configurable? If not, is live555 failing to do something that wowza requires in order to acknowledge that it is still listening to the stream?