GNOME Bugzilla – Bug 637725
rtspsrc with tcp protocol
Last modified: 2012-10-07 01:38:03 UTC
I'm having problems with an rtsp server if I connect over tcp (udp-unicast works fine), launching rtspsrc with debug=true show something like this: RTSP request message 0x7f19a6c30be0 request line: method: 'OPTIONS' uri: 'rtsp://....' version: '1.0' headers: body: after a short I while I see again RTSP request message 0x7f19a6c30be0 request line: method: 'OPTIONS' uri: 'rtsp://...' version: '1.0' headers: body: and so on. It seems the rtsp server never response (or gstreamer doesn't get this response) while I can see the rtsp response in udp-unicast. After gstreamer send the RTSP request the whole pipeline get stucked (I have to manually kill gst-launch) and the video freeze. If you run the pipeline inside an application the whole application will freeze. Please note that vlc works fine with the same stream in the same network where udp-unicast is not allowed for hour and tcp is the only way to see the stream. Note the tcp-timeout option doesn't help here
wireshark show a zero byte response from the rtsp server
I have a public test stream that I can make available if someone ping me on IRC (nickname: drakkan1000)
Does this still happen with the latest releases (core/base 0.10.36 and -good 0.10.31) or git? Could you attach the wireshark logs from both VLC where it works and GStreamer where it doesn't work?
I'm sorry I have not more access to that camera, if I remember correctly Wim sayed that gstreamer does not handle 0 bytes rtsp responses, Nicola
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!