BTW while digging in the specification RFC 2326 I found that section 3.4
says that the session Identifiers MUST be chosen randomly and MUST be at
least eight octets long to make guessing it more difficult. Yet a fast
look at the live555 library code seems to show that is doesn't choose a
random se
oun...@ns.live555.com [mailto:live-devel-
>boun...@ns.live555.com] On Behalf Of Ross Finlayson
>Sent: Thursday, January 7, 2010 5:36
>To: LIVE555 Streaming Media - development & use
>Subject: Re: [Live-devel] TrackId= Vs track in a=control:
>
>>I have an RTSP client (not live555)
I have an RTSP client (not live555) that complains of the
a=control:track format used by the RTSP server (live555 application)
implementation of the live555 library. When I change the code of the
library to use a=control:trackID= the RTSP client doesn`t complain
anymore. The examples in the RTS
I have an RTSP client (not live555) that complains of the
a=control:track format used by the RTSP server (live555 application)
implementation of the live555 library. When I change the code of the
library to use a=control:trackID= the RTSP client doesn`t complain
anymore. The examples in the RTSP sp
