Hi all
I’m trying to connect a new IP camera model to wonza and re-stream the media using rtsp interleaved. Unfortunately, the rtsp camera implementation is still buggy, and crash if the CSeq header doesn’t follow the request line…
So… I coded a little java “proxy” that checks the CSeq header position and fix it if is necessary. ffplay and mplayer can now get the camera’s stream, but when I use wonza I get timeout:
2012-09-16 08:38:31 COT comment server INFO 200 - RTPMediaCaster.streamTimeout[1506367663:rtplive/_definst_:31.stream]: timeout:12000 diff:12013 reason:101 - - - 576.908 - - - - - - - - - - - - - - - - - - - - - - - - -
2012-09-16 08:38:31 COT comment server INFO 200 - RTPMediaCaster.resetConnection[1506367663:rtplive/_definst_:31.stream]: - - - 576.909 - - - - - - - - - - - - - - - - - - - - - - - - -
2012-09-16 08:38:31 COT comment server INFO 200 - RTPMediaCaster.closeRTPSession[1506367663:rtplive/_definst_:31.stream] - - - 576.909 - - - - - - - - - - - - - - - - - - - - - - - - -
2012-09-16 08:38:31 COT comment server DEBUG 200 - *** RTSPMessageSend ***
TEARDOWN rtsp://192.168.99.2:5554/live/av0?user=admin&passwd=admin RTSP/1.0
Session: 31692174
CSeq: 5
I can confirm that the audio and video streams are delivered inside the tcp connection from the camera trough the “proxy” to wowza. I can see this in the logs:
2012-09-16 08:38:21 COT comment server DEBUG 200 - rtp[rtsp://192.168.99.138:554/audio0:652] {80 88 33 ba 74 e0 0c 8d 50 63 23 22 d6 d6 d1 d0 } - - - 567.633 - - - - - - - - - - - - - - - - - - - - - - - - -
2012-09-16 08:38:21 COT comment server DEBUG 200 - rtp[rtsp://192.168.99.138:554/video0:173] {80 e0 ec 34 16 ae b8 59 50 63 23 22 41 9a ee 0a } - - - 567.633 - - - - - - - - - - - - - - - - - - - - - - - - -
2012-09-16 08:38:21 COT comment server DEBUG 200 - SINGLE: end:true tc:380549209 sz:161 - - - 567.634 - - - - - - - - - - - - - - - - - - - - - - - - -
2012-09-16 08:38:21 COT comment server DEBUG 200 - rtp[rtsp://192.168.99.138:554/audio0:652] {80 88 33 bb 74 e0 0f 0d 50 63 23 22 51 d5 d0 dc } - - - 567.715 - - - - - - - - - - - - - - - - - - - - - - - - -
2012-09-16 08:38:21 COT comment server DEBUG 200 - send[1844165295]: size:0:0 filter:7 time:251 tOffset:0 rwrt:true - - - 567.718 - - - - - - - - - - - - - - - - - - - - - - - - -
Those look like packets right ? So, I’m a little loss here. I know that is not a wowza problem, but maybe you can give any clue about what to do. Do you think I have to “fix” the IP address inside all the messages coming from the camera ? (ffplay and mplayer doesn’t seem to care about it) 192.168.99.2 is the “proxy”, and 192.168.99.138 is the camera:
2012-09-16 08:38:19 COT comment server INFO 200 - RTPSessionDescriptionDataProviderBasicRTSPWorker.sessionStart: PLAY: rtsp://192.168.99.2:5554/live/av0?user=admin&passwd=admin - - - 564.809 - - - - - - - - - - - - - - - - - - - - - - - - -
2012-09-16 08:38:19 COT comment server DEBUG 200 - *** RTSPMessageSend ***
PLAY rtsp://192.168.99.2:5554/live/av0?user=admin&passwd=admin RTSP/1.0
Session: 31692174
CSeq: 4
Range: npt=0.000-
- - - 564.812 - - - - - - - - - - - - - - - - - - - - - - - - -
2012-09-16 08:38:19 COT comment server DEBUG 200 - RTPSessionDescriptionDataProviderBasicRTSPWorker.send: command:PLAY
PLAY rtsp://192.168.99.2:5554/live/av0?user=admin&passwd=admin RTSP/1.0
Session: 31692174
CSeq: 4
Range: npt=0.000-
- - - 564.812 - - - - - - - - - - - - - - - - - - - - - - - - -
2012-09-16 08:38:19 COT comment server DEBUG 200 - *** RTSPMessageReceive ***
RTSP/1.0 200 OK
response: OK
protocol: RTSP/1.0
range: npt=0.000-
session: 31692174
cseq: 4
status: 200
date: Sat, 15 Sep 2012 15:32:58 GMT
uri: RTSP/1.0 200 OK
rtp-info: url=rtsp://192.168.99.138:554/audio0;seq=13210;rtptime=1960819853,url=rtsp://192.168.99.138:554/video0;seq=60462;rtptime=380338249