Standards Track A. Rao Netscap - RFC Editor

RFC 2326 Real Time Streaming Protocol April 1998M->C: RTSP/1.0 200 OKCSeq: 4Session: 12345678RTP-Info: url=rtsp://foo/twister/video;seq=9810092;rtptime=3450012C->M: PAUSE rtsp://foo/twister/video RTSP/1.0CSeq: 5Session: 12345678M->C: RTSP/1.0 460 Only aggregate operation allowedCSeq: 5C->M: PAUSE rtsp://foo/twister RTSP/1.0CSeq: 6Session: 12345678M->C: RTSP/1.0 200 OKCSeq: 6Session: 12345678C->M: SETUP rtsp://foo/twister RTSP/1.0CSeq: 7Transport: RTP/AVP;unicast;client_port=10000M->C: RTSP/1.0 459 Aggregate operation not allowedCSeq: 7In the first instance of failure, the client tries to pause onestream (in this case video) of the presentation. This is disallowedfor that presentation by the server. In the second instance, theaggregate URL may not be used for SETUP and one control message isrequired per stream to set up transport parameters.This keeps the syntax of the Transport header simple and allowseasy parsing of transport information by firewalls.14.3 Single Stream Container FilesSome RTSP servers may treat all files as though they are "containerfiles", yet other servers may not support such a concept. Because ofthis, clients SHOULD use the rules set forth in the sessiondescription for request URLs, rather than assuming that a consistentURL may always be used throughout. Here’s an example of how a multistreamserver might expect a single-stream file to be served:Accept: application/x-rtsp-mh, application/sdpSchulzrinne, et. al. Standards Track [Page 67]