RTSP Push related information and test software is relatively small, this article describes RTSP push related signaling and testing effects:
1. RTSP push flow.
Mainly divided into two parts: The first part first sends a letter; the second part sends an RTP package.
Signaling process:
1.1 Send Options first, Options is more common, and don't make a detailed description.
1.2 Send Announce, sending Announce mainly transmits the audio and video information to be pushed to the server through the SDP format. Regarding how the SDP information is constructed, please refer to RFC6184 for H264. H265 Please refer to RFC7798. Two examples will be held below.
H264 + AAC Announce:
Announce RTSP: //192.168.0.188: 554 / Livexxx.sdp RTSP / 1.0 Content-Type: Application / SDP CSEQ: 2 User-Agent: xxxyyy Content-Length: 489
v = 0 o = - 0 0 in IP4 127.0.0.1 s = DDDOOKK C = IN IP4 192.168.0.188 t = 0 m = video 0 RTP / AVP 96 a = = = fmtp: 96 packetization- mode = 1; sprop-parameter-sets = Z00AKp2oHgCJ + WbgICAoAAADAAgAAAMBlCA =, aO48gA ==; profile-level-id = 4D002A a = control: streamid = 0 m = audio 0 RTP / AVP 97 a = rtpmap: 97 MPEG4-GENERIC / 44100/1 A = FMTP: 97 Profile-Level-id = 1; Mode = AAC-HBR; Sizelength = 13; IndexLength = 3; IndexDeltaRength = 3; config = 1208 a = Control: streamid = 1
H265 (HEVC) + AAC Announce:
Announce RTSP: //192.168.0.174: 554 / live3.sdp RTSP / 1.0 Content-Type: Application / SDP CSEQ: 2 User-Agent: mmmmd Content-Length: 364
v = 0 o = - 0 0 in ip4 127.0.0.1 s = uvsdewe c = in ip4 192.168.0.174 t = 0 m = video 0 RTP / AVP 96 a = = = control: streamid = 0 M = Audio 0 RTP / AVP 97 A = RTPMAP: 97 MPEG4-Generic / 44100/1 A = FMTP: 97 Profile-Level-ID = 1; Mode = AAC-HBR; Sizerngth = 13; IndexLength = 3; IndexDeltangth = 3 Config = 1208 a = control: streamid = 1
1.3 Send SETUP, this is basically the same as playback, please refer to the playback process.
1.4 After sending Record, Record, the signaling process is completed, and then the RTP package is sent next.
The construction of the RTP package, the H264 reference RFC6184. H265 Refer to RFC7798.
Next, the actual test push effect, from GitHub or Big Live SDK official website to download the RTSP H264 H265 Push Tool and RTSP Play Tool (please download the Windows version test).
1. Open the RTSP push program SMARTPUBLISHERDEMO.EXE (Test H265 Push Please use 64-bit EXE) to configure:
2. After configuring the image above, click the "Push RTSP" button to see the corresponding play address:
3. Copy the player address, then open SmartPlayer.exe, play the play:
4. Push the delay in the use of RTSP, which is very low, can be as low as more than 100 milliseconds, the picture below is a screenshot of the test delay:
It can be seen that the delay is more than 100 milliseconds, I am pushed from my home to the public network server, then pull it again.
Summary:
The advantage of RTSP relative to RTMP is to use UDP to transmit audio and video data. UDP transmission avoids delay accumulation, and of course RTSP can also use TCP to transfer RTP packets, the above push program UPD and TCP transmission support. In addition, the RTSP protocol itself supports H265, unlike RTMP needs to be supported with an unofficial extension. The actual test can be seen that the delay is very low, hundreds of milliseconds, this delay can meet most of the low delay scene requirements. In addition The RTSP protocol itself is a real-time streaming, better compatible with existing monitoring systems. RTSP push more suitable for Internet remote monitoring.
Our other product:
