Analysis of RTSP-RFC2326 protocol formats 3-DESCRIBE requests
The customer initiates a DESCRIBE request to the server. In order to get the Session Description (SDP), the following is what I actually got from the Live555 server. The content is as follows: DESCRIBE rtsp: // 10.45.134.29: 8554/hsf-esvideotest RTSP/1.0 // method resource ID protocol and version CSeq: 2 // User-Agent ID of the current request: testRTSPClient.exe (LIVE555 Streaming Media v2013.10.25) // use the client information Accept: application/sdp // The form of response content that can be understood in this request ~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ RTSP/1.0 200 OK // response success mark CSeq: 2 // response Date: Fri, Nov 01 2013 05:56:34 GMT // time Content-Base: rtsp: // 10.45.134.29: 8554/hsf-esvideotest // URI Content-Type: application/sdp // Content Type Content-Length: 520 // Content Length v = 0 bytes Protocol version o =-1383285089523051 1 IN IP4 10.45.134.29 // format = <User Name> <session ID> <version> <network type> <address type> <address> s = Session streamed By "testOnDemandRTSPServer" ------------------ session name I = hsf-esvideotest listener session information t = 0 0 listener session start time and end time a = tool: LIVE555 Streaming Media v2013.10.25 -------------------------- tool a = type: broadcast description of tool a = control: * a = range: Treaty = 0 ----------------------------------------------------------- length of streaming media a = x-qt-text-nam: Session streamed by "testOnDemandRTSPServer" --- description a = x-qt-text-inf: hsf-esvideotest protocol description information m = video 0 RTP/AVP 96 --------------- video port transfer protocol payload Type c = IN IP4 0.0.0.0 B = AS: 500 bytes // audio bitrate a = rtpmap: 96 H264/90000 --------------- sample is 90000 a = Fmtp: 96 packetization-mode = 1; profile-level-id = 42C033; sprop-parameter-sets = parameters =, aM48gA = a = control: track1 for live555, the code for obtaining H264 information is located in hsf-videostreamparser: parse.