If you need to test an older codec or a generic RTSP transport stream:
Public samples rarely require auth, but your cameras do. Ensure the URL includes username:password@ before the IP. Note that special characters ( @ , : , # ) in passwords must be URL-encoded (e.g., @ becomes %40 ).
⚠️ Public test streams are provided by third parties and are often unreliable. They can be taken offline, changed, or become slow due to high demand. Therefore, they are only suitable for temporary, initial testing and should not be relied upon for ongoing use.
| Parameter | Description | Common Values | | :--- | :--- | :--- | | | Specifies the camera channel on a multi-channel device. | 1 , 2 , 3 | | subtype | Selects the stream profile (main, sub, etc.). | 0 (Main Stream), 1 (Sub Stream) | | profile | Applies a specific quality profile. | profile1 , profile2 | | session | A unique key used by NVRs to group multiple channel connections. | Any unique string, e.g., session=123abc | rtsp sample url
Since every manufacturer uses a different path, here are common examples for popular brands: Sample URL Format Generic/Test rtsp://server.example.org:8080/test.sdp rtsp://admin:12345@192.168.1.210:554/Streaming/Channels/101
Open a second terminal window and run:
Excellent for client testing, but not for web deployment. If you need to test an older codec
When constructing an RTSP URL for secure networks, you must handle authentication correctly. RTSP handles credentials in two main variations:
sudo snap install rtsp-test-server
Consequently, studying default RTSP sample URLs teaches a critical lesson in security hygiene. The very convenience that makes rtsp://username:password@ip easy to test also makes it a gaping vulnerability if left unchanged. The sample URL thus serves as a double-edged sword: a tool for learning and a warning sign of misconfiguration. ⚠️ Public test streams are provided by third
Let's break down each component:
The network location of the camera or media server (e.g., 192.168.1.100 or ://stream.com ).