RTSP server only adding client the first time it requests a connection

[Sebastian Dröge]

On Mo, 2014-01-06 at 14:28 -0800, Frank M. wrote:
> I've constructed the following pipeline on the server:
> 
> souphttpsrc location=http://127.0.0.1:50000/stream0.mjpeg name=src
> do-timestamp=true !
> multipartdemux ! image/jpeg,framerate=5/1,width=640,height=480 ! queue !
> rtpjpegpay name=pay0 pt=96
> 
> The first time a client requests a connection the rtsp server adds the
> client:
> 
> 0:00:07.493875376 15932  0x9a2fd20 INFO rtspclient
> rtsp-client.c:2491:gst_rtsp_client_set_connection: client 0x9a326f0
> connected to server ip 10.10.10.222, ipv6 = 0
> 0:00:07.493907872 15932  0x9a2fd20 INFO rtspclient
> rtsp-client.c:2494:gst_rtsp_client_set_connection: added new client
> 0x9a326f0 ip 10.10.10.220:38703
> 
> The client then continues to send OPTIONS and DESCRIBE request to the server
> and plays the stream successfully. After closing the client any new instance
> of a client is not being added to the server anymore (the rtsp server
> doesn't even seem be aware of connection attempts by any client ).

Can you provide the code of your server or some kind of test application
to reproduce the problem?

Do you have the rtsp media factory in the server set to shared? In that
case it will only create a pipeline for the very first client and reuse
that for future clients.

But I assume with not being aware of any connection attempts you mean
that the server does not even see the new connections. Can you check
with something like wireshark if at least something is sent over the
network from the client to the server?

-- 
Sebastian Dröge, Centricular Ltd - http://www.centricular.com
Expertise, Straight from the Source
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 966 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20140107/7bf131b0/attachment-0001.pgp>