[Live-devel] openRTSP

[Andro Debevere]

>OK, the problem is that the *client* port numbers are the same for both 
>streams.  I don't know why the server does this, but in any case it's 
>not something that we currently support in our code (to do so would 
>require that we demultiplex based on SSRC, which is something that we 
>don't do).

Just to make things clear, it is the client (openRTSP) that initially
proposes the client port numbers to the server, not the other way around
(why would a server choose ports on a client?, it doesn't have any idea
which ports are already used on it). See the SETUP message from the client
(openRTSP) to the server. In the server response the client port numbers are
just copied and the server port numbers are added.

Sending request: SETUP rtsp://test/test.mp4/trackID=6 RTSP/1.0
CSeq: 4
Transport: RTP/AVP;unicast;client_port=61426-61427
Session: 6993324177280988772
User-Agent: openRTSP.exe (LIVE555 Streaming Media v2009.09.28)

Received SETUP response: RTSP/1.0 200 OK
Server: DSS/6.0.3 (Build/526.3; Platform/Linux; Release/Darwin Streaming
Server;  State/Development; )
Cseq: 4
Session: 6993324177280988772
Last-Modified: Tue, 02 Feb 2010 13:14:41 GMT
Cache-Control: must-revalidate
Date: Mon, 08 Mar 2010 08:02:05 GMT
Expires: Mon, 08 Mar 2010 08:02:05 GMT
Transport:
RTP/AVP;unicast;source=157.193.213.35;client_port=61426-61427;server_
port=6970-6971;ssrc=6F6104C5

Because the groupsock library uses the SO_REUSEADDR option as default,
there's a chance that creating sockets will result in two socket pairs using
the same port numbers, and the recording will fail as explained in my
previous post.

-----Original Message-----
From: live-devel-bounces at ns.live555.com
[mailto:live-devel-bounces at ns.live555.com] On Behalf Of Ross Finlayson
Sent: Saturday, March 06, 2010 6:26 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] openRTSP

>For the first track the client port numbers proposed are "39616-39617" and
>the server port numbers are "6970-6971". For the second stream, the client
>port numbers are also "39616-39617", but now the server port numbers are
>"6972-6973"

OK, the problem is that the *client* port numbers are the same for 
both streams.  I don't know why the server does this, but in any case 
it's not something that we currently support in our code (to do so 
would require that we demultiplex based on SSRC, which is something 
that we don't do).
-- 

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
live-devel at lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel