[Live-devel] Using live555 as the RTSP streaming library

[ying lcs]

I am using vlc to tanscode a file in boardcast mode, like this:

vlc -I dummy mask.wmv --sout
#transcode{vcodec=mp4v,vb=400,acodec=mpga,ab=128}:rtp{dst=10.20.20.68,port-video=3444,port-audio=3448,sdp=file:///usr/local/movies/mytest4.sdp}

I think vlc depends os live555 as it rtp transport.

And I have setup a network trace to capture rtp packet sent out:

10.. .... = Version : RFC 1889 Version (2)
..0. ....  = Padding: False
...0 ....  = Extension: False
.... 0000 = contributing source identifiers count: 0
0... .... = Marker: False
Payload type: Unknown (96)
Sequence number: 18499
Timestamp: 719731146
Synchronization Source identifier: 1472073403
Payload: 043D8DF8180F84208524064B ....

My question is why the payload type is 96? If that is the case, how
can the client decode this RTP packet?

Thank you.



On 5/13/07, Ross Finlayson <finlayson at live555.com> wrote:
> >Can you please tell me if live555 sends out RSTP Sender Report when it
> >streams a file?
>
> I think you mean "RTCP Sender Report" (not "RTSP Sender Report").
>
> Yes, our RTSP server implementation (more precisely, the
> "OnDemandServerMediaSubsession" and "PassiveServerMediaSubsession"
> classes) creates "RTCPInstance" objects for each stream, and these
> send out RTCP Sender Report ("SR") packets.
> --
>
> 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
>