[Live-devel] Get a buffer from a sink

[Andrey Filippov]

Ross,

We'll look into this problem. Thanks for the explanations.

Andrey

On Fri, Feb 24, 2012 at 8:57 AM, Ross Finlayson <finlayson at live555.com> wrote:
> Your email indicates a lot of confusion, and a lot of unnecessary flailing
> around.  It's better to ask questions one-at-a-time, in chronological order,
> as they arise.
>
> The first question you should be asking is: Why is "testRTSPClient" failing
> when it tries to receive a stream from your server?  Fortunately, the
> debugging output from "testRTSPClient" helps tell you the answer:
>
> Sending request: SETUP rtsp://192.168.0.12 RTSP/1.0
> CSeq: 3
> User-Agent: ./testRTSPClient (LIVE555 Streaming Media v2012.01.13)
> Transport: RTP/AVP;unicast;client_port=46636-46637
>
>
> Received 100 new bytes of response data.
> Received a complete SETUP response:
> RTSP/1.0 200 OK
> CSeq: 3
> Session: 47112344
> Transport: RTP/AVP;unicast;destination=0;port=46636
>
>
> [URL:"rtsp://192.168.0.12"]: Failed to set up the "video/JPEG" subsession:
> Missing or bad "Transport:" header
>
>
> So the problem here is that your server (your "Elphel NC353L camera") is
> returning a bad "Transport:" header in its response to the RTSP "SETUP"
> command.  It is incorrectly including a "port" parameter for a unicast
> stream.  The "port" parameter (as noted in RFC 2326, section 12.38) is
> supposed to be used for a multicast stream.  For a unicast stream - such as
> this one - the server should be including a "server_port" parameter instead.
>
> You should contact your camera's manufacturer (Elphel), to check if they
> have a firmware upgrade.  If they don't then please tell them about this
> problem, and ask them to fix it.
>
>
> 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
>