Re: [Live-devel] Server getting confused with RTCP message before PLAY command (when using RTP over TCP)

2013-05-30 Thread Ross Finlayson
Stanley, I haven't had time yet to review and respond to your emails. You should note, however, that the old 'synchronous' "RTSPClient" interface has now been removed completely - as of the latest version (2013.05.30) of the code - and is no longer supported, at all. (This old interface has b

Re: [Live-devel] ProxyServerMediaSession not working correctly for more than one client per stream

2013-05-30 Thread Ross Finlayson
> We did some investigation with few older versions of live555 source base we > have in store. It seems, the issue was not there in version 2013.04.21. It > seemed to have first appeared in 2013.04.23. I diff-ed these two versions of > source codes. Most of the changes did not appear to be relat

Re: [Live-devel] Server getting confused with RTCP message before PLAY command (when using RTP over TCP)

2013-05-30 Thread Stanley Biggs
Ross Finlayson writes: > > >Or perhaps the client code shouldn't be allowed to send RTCP > >messages until after the PLAY command has been issued. > > You're right - it shouldn't. You've discovered a bug. > > >PS. I should probably note my code isn't like openRTSP in that it > >doesn't do D

Re: [Live-devel] RTSP Client sending RR messages before Play command is issued

2013-05-30 Thread Stanley Biggs
It seems that it may not be RR packets. It is some other RTCP or RTP packet that the client sends. On Tue, May 28, 2013 at 10:36 AM, Stanley Biggs wrote: > Hi > > I am experiencing the same problem as described in this thread: > http://lists.live555.com/pipermail/live-devel/2012-August/015750.ht

Re: [Live-devel] ProxyServerMediaSession not working correctly for more than one client per stream

2013-05-30 Thread Subhankar Saha
Hi Ross, This is assuming, of course, that you haven't modified the code at all. If you have modified the code, then all bets are off... No, we have not made any modification to the code at all, except changing "win32config" for TOOLS32 (to put correct VC path) and LINK_OPTS_0