RTSP Client Streamer

[David Wells]

Using rtspt:// does work, but TCP tunneling does not require the NAT Hole punching as UDP does, and by-passes the problem completely.

I submitted to Bugzilla. Bug 754534

Thank you for your time.


-----Original Message-----
From: gstreamer-devel [mailto:gstreamer-devel-bounces at lists.freedesktop.org] On Behalf Of Sebastian Dröge
Sent: Thursday, September 03, 2015 2:49 AM
To: Discussion of the development of and with GStreamer <gstreamer-devel at lists.freedesktop.org>
Subject: Re: RTSP Client Streamer

On Do, 2015-09-03 at 10:11 +0300, Sebastian Dröge wrote:

> This is the error here, receiving packets from the UDP socket failed 
> for whatever reason. The error message is not very helpful as UDP is 
> connection-less :) If I understand this correctly from the PCAP log, 
> the problem is that we're sending data via UDP to the server in the 
> beginning on the ports that would be used for receiving data from the 
> server... the server replies via ICMP that those ports are 
> unreachable, and then the socket fails with the above error on the 
> receiver side. Not sure what exactly we're sending to the server 
> there, it's not proper RTP and I don't think we should send anything 
> there at all at this point.

What is sent there are 5 200 byte packets with random data to open up NATs, so that we can actually receive back UDP packets for NATs that have UDP "connection" tracking.

Unfortunately the server is not listening on that port, and we're using the same socket for receiving UDP packets and sending these dummy packets... so on the next time a packet is received, the socket reports an error.

Please report this in Bugzilla? Thanks!

--
Sebastian Dröge, Centricular Ltd · http://www.centricular.com