Recently, it has been found that many developers are searching for available RTSP test URLS. At present, there are very few RTSP urls that can be tested on the public network. Even if they are available, the resolution and network are very poor, which are not suitable for long-term testing.

In view of this, our suggestion is that it is best to buy a Hikang or DAhua camera directly online. Generally speaking, The RTSP URL format of Hikang Dahua is as follows:

Hikang camera RTSP URL rules

The main stream: RTSP: / / admin: [email protected]:554 / h265 / ch1 / main/av_stream

Subcode flow: RTSP: / / admin: [email protected]:554 / h264 / ch1 / sub/av_stream

RTSP ://[username]:[password]@[IP]:[port]/[codectype]/[channel]/[subtype]/av_stream URL description: username: indicates the username. Password: password; IP: IP address of the network camera. Port: indicates the port number. The default value is 554. Codectype: h264/ H265 / mJPEG; Channel: indicates the channel number. Subtype: indicates the type of the code stream. The main code stream is main, and the sub code stream is sub.

Dahua camera RTSP URL rules

RTSP ://admin:[email protected]:554/cam/realmonitor? channel=1&subtype=0

RTSP ://admin:[email protected]:554/cam/realmonitor? channel=1&subtype=1

RTSP ://[username]:[password]@[IP]:[port]/ CAM/realMonitor?/[channel]&/[subtype] Password: password; IP: IP address of the network camera. Port: indicates the port number. The default value is 554. Codectype: h264/ H265 / mJPEG; Channel: indicates the channel number. Subtype: indicates the type of the code stream. The primary code stream is 0, and the sub-code stream is 1.

How do I generate a local RTSP test URL myself

If you want to capture PC camera or screen, you can also use lightweight RTSP service locally, locally generate an RTSP test URL. Common way, such as VLC streaming, or Daniel live SDK (URL) Windows platform SmartPublisherDemo generation.

This article uses SmartPublisherDemo lightweight RTSP service to collect local cameras as an example to explain how to create a local test RTSP address.

1. The selected camera, and select the need to test the resolution, frame rate, click on the “default value for video bit rate”, get system recommended by the code rate (advanced users can also configure), such as the need to collect audio, see collection microphone or speaker, if both are need to collect, at the same time can be selected (mixing mode).

2. Click Configure view Rtsp Service, and click Start Service in the dialog box that is displayed to start one or multiple groups. Each service has an Rtsp URL.

3. After, click on the “post RTSP stream” button, after the release, generates a RTSP URL, local to the machine as an example, the generated URL is “RTSP: / / 192.168.0.211:8554 / stream1”.

4. Start the player and enter the generated RTSP URL to test it.

5. View server load: Click “View RTSP service Configuration” again to see the number of sessions connected to each service:

6. To stop the service, click “Stop RTSP stream” on the page.

Is it very convenient?

Why do lightweight RTSP services?

The core pain point of the lightweight RTSP service is to prevent users or developers from deploying the RTSP or RTMP service independently, so that local audio and video data (such as cameras and microphones) can be encoded and aggregated to the built-in RTSP service to provide external RTSP urls for pulling streams. The lightweight RTSP service is suitable for Intranet environments. H.264/H.265 and RTSP authentication, unicast, and multicast modes are supported. Considering the bearing capacity of a single service, we can create multiple RTSP services at the same time and obtain the number of current RTSP service session connections.

Design features:

  • [Basic function] Collect camera, screen, window or external customized audio and video data;
  • AAC;
  • H.264, H.265;
  • [Protocol type]RTSP;
  • [Transmission mode] Supports unicast and multicast modes.
  • [Port Settings] Supports RTSP port Settings.
  • [Authentication Settings] The user name and password for RTSP authentication are supported.
  • [Obtaining number of Session connections] The current number of RTSP service session connections can be obtained.
  • [Multi-service support] Supports the simultaneous creation of multiple built-in RTSP services;
  • [H.265 support]Windows built-in RTSP Server supports publishing H.265 videos;
  • [RTSP URL Callback] The configured RTSP URL can be called back to the upper layer through the event.

If you’re interested, you can try it yourself.