I need a lot more detail (encoder being used, Wowza version…) as much detail as possible.
Charlie
It sounds like there may be an issue with the camera. The timebase must be set to 0 which is going to be a problem. You might try a different AVSync Method in conf/rtplive/Application.xml to see if that helps.
Charlie
Again, it is most likely not a wowza issue but more likely an issue with the camera. We can take a quick look at the camera if you send us the direct RTSP URL to the camera on teh Internet. Can’t help with anything short of that.
Charlie
Wowza does not support the video and audio codec being used by this camera. This camera uses MPEG-4 and ULaw. The camera output must be transcoded to H.264, AAC or MP3 to work properly with Wowza.
Charlie
You might also try:
MComms TV, a commercial stream-to-stream transcoding solution
http://www.mcommstv.com/products/mcomms-transcode
Ripcode, a commercial hardware sol ution with DSPs powering the transcoding
http://www.ripcode.com/solutions/rtst.php
Charlie
There seems to be missing data in teh SDP data. Your SDP video data looks like this:
m=video 0 RTP/AVP 99
c=IN IP4 0.0.0.0
a=control:rtsp://10.0.0.50/live:video:2
a=rtpmap:99 H264/90000
a=framesize:99 352-288
There should be additional data that describes the H.264 stream.
Charlie
I do not know that solution. It looks like you are pulling a stream using RTSP. Is there anything on the Internet to test against? If you send an RTSP/RTP stream to support@wowza.com that is available on the Internet we can take a look at it. Be sure to reference this forum thread.
Charlie
Download and install this patch:
WowzaMediaServer2.2.4-patch2.zip
It fixes a small problem with RTSP/RTP header parsing. Be sure you set the the forceInterleaved MediaCaster/Properties to true and I had to set the RTP/AVSyncMethod method to systemclock to make it work.
Charlie
Great, happy to hear it is working.
Charlie
We do send back packets but I think they are mostly empty.
Charlie
If using udp the rtcp packets will flow over port one greater than video port or one greater than audio port. It is not possible to send your own packets.
C
No short term plans.
Charlie
No short term plans.
Charlie
Hi Charlie,
You can change the starting port number. It is defined in [install-dir]/conf/Server.xml. The setting is RTP/DatagramStartingPort. I don’t think this is the problem since the port number are determined by the RTSP negotiation. But see if this helps.
I already changed the starting port number to 6990 because the server is also running Darwin Streaming Server. I think the problem is the ending port number. If I change the starting port number to 55300 to try and include the ports which this particular Axis cam seems to want to stream its data on, I still get no working stream.
Further more: We have several Axis cams “hooked up” to this server and all of them “play nice” regarding the UDP port range (starting at 6990 in our case).
Is a firewall and/or router at the location of this cam possibly causing trouble?
Regards,
Rudo
Take a look at :input-slave=dshow://… or a variation of that option.
You can do NetStream.setBufferTime(0)
But take a look at this post first:
http://www.wowza.com/community/t/-/588
Richard
With JW player, you can set buffertime with Flashvar “bufferlength”.
&bufferlength=0
Richard
I don’t know Flowplayer yet.
Richard
Maybe the bitrate of the stream coming from the camera is too high?
Richard
I am using the M1031-W model, and it works great for me. You should get a model that natively supports h.264, for example: M1011(-W), M1031-W, P3301(-V), Q1755.
The biggest problem I had was my router, which needed firmware update.
You have to put the camera in the router DMZ, or setup pass-thru for ports tcp 554 and udp 6970-9999.
Richard
