On Fri, Oct 17, 2008 at 4:27 PM, Ross Finlayson <[EMAIL PROTECTED]> wrote: > >> >> In other words, once I do the above, what else >> >> do I have to do to clean up in rebuild again in preparation of >> >> streaming the next file? >> > >> > If you want to keep the existingoutput network connections, and continue >> > streaming the next file, then you don't need to make *any* changes to >> > the >> > existing code. In particular, you should *not* be sending any RTCP >> > "BYE" >> > packet in this case. >> >> I am looking at the vobstreamer as a starting model for an application >> that will stream other codecs (H264, MPEG4) such that the next file >> may be very different from the 1st, > > It's not possible to do this within a single RTSP/RTP session, because the > client needs to get new information (SDP) about each new codec. >
This is exactly my point. I wish to trigger the request of a new RTSP session from the client end so it (the client) can get new SDP information. To do this, I want the client to see and RTCP BYE so that it closes the current RTSP session and requests a new one at the same (fixed) PassiveServerMediaSession RTSP url on the server end. So the question is what should be the general construct/destruct procedure for: 0. Forcing an RTCP BYE (using Medium::close() as you advised earlier) 1. (Possibly) closing the existing RTP Sinks and creating new ones. 2. (Possibly) closing the SMS and creating a new one associated with the new sinks. 3. (Possibly) closing the current sources and creating new ones. Thanks. -- B. Gitonga Marete Tel: +254-722-151-590 _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
