We are currently running Wowza Media Server 2 and have been since 2010, but have decided to move to the newest version. We have created a new instance and have successfully published our IP cams that stream H.264.
Additionally, we have several older web cams that only stream motion jpeg. In our current setup we have a transcoder that pushes an transcoded H.264 RTSP stream to Wowza. I have set up a test stream that now pushes it to the new Wowza instance.
I can see the stream is active and reaching Wowza when viewing in the incoming stream in Stream Manager. If I use the Adobe RTMP test player to try and play the outgoing stream, the video does not display but the status shows "Playing".
I've enabled DEBUG in /conf/log4j.properties and as much debug and logging as I could fine at the application level, but I am not seeing any more information in the access log. For the other streams that are not being pushed, I can see very detailed information.
My question is, is there some sort of debugging that I have missed that will give me more detailed information about packet loss and such from an incoming RTSP stream? Are there newer/additional input requirements for an incoming stream than in Wowza Media Server 2.
This is the ffmpeg command line that we are currently using.
ffmpeg -er 4 -y -r 2 -g 1 -f mjpeg -an -force_nth_key_frames 2 -i http://user:pass@<IP>/-wvhttp-01-/getoneshot?frame_rate=2000"&"frame_count=0 -vcodec libx264 -vpre fastfirstpass -vpre baseline -b 150k -bt 32k -threads 0 -f rtsp rtsp://user:pass@<IP>:1935/nature/hilton