rtsp://[user]:[pass]@[ip]:554/cam/realmonitor?channel=1&subtype=0 rtsp://[user]:[pass]@[ip]:554/h264Preview_01_main Axis rtsp://[user]:[pass]@[ip]/axis-media/media.amp
While the sample URLs listed above are deliberately public, be aware of and ZoomEye . Millions of real, private security cameras are exposed on the public internet with default credentials ( admin:admin ). rtsp sample url
For more in-depth testing, especially for developers, you can use the command-line tool FFmpeg: ffplay rtsp://9627b0bf2a7b.entrypoint.cloud.wowza.com:1935/app-p5260J38/66abe4b9_stream1 rtsp://[user]:[pass]@[ip]:554/cam/realmonitor
– Optional authentication credentials required by most secure IP cameras. rtsp://admin:password@ :554/cam/realmonitor
rtsp://admin:password@ :554/cam/realmonitor?channel=1&subtype=0 rtsp://admin:password@ :554//h264Preview_01_main 5. Tools to Test and Play RTSP URLs
For instance, a common public test URL might be rtsp://wowzaec2demo.streamlock.net/vod/mp4:BigBuckBunny_115k.mov . Dissecting this reveals the protocol's logic. The rtsp:// scheme announces the request type. The hostname ( wowzaec2demo.streamlock.net ) points to the server. The port, often omitted because RTSP defaults to port 554, is implied. Finally, the path ( /vod/mp4:BigBuckBunny_115k.mov ) tells the server which specific stream resource to access.