The short answer
A controlled local source is more useful for repeatable diagnosis than an unknown public camera URL. Use a clip you own with an RTSP server, then verify both server output and decoded client video. This site does not host a public test stream or promise that third-party demos stay online.
Work through the checks
Choose a short, non-sensitive video you are allowed to use. Check its codec so a later decoder failure is not confused with an unreachable server.
Run an RTSP server such as MediaMTX using its documented local configuration. Decide whether the viewer runs on that host or another machine on your trusted LAN.
Publish the clip to the configured RTSP endpoint. The example uses localhost and port 8554; replace them if your server uses a different listening address or authentication.
Open the published endpoint in a reference client and verify changing frames. A process running in a terminal is not proof that the server has accepted a source.
Try the same endpoint in your intended viewer. On another computer, use the server’s reachable LAN address rather than 127.0.0.1, and check the relevant firewall rule.
ffmpeg -re -stream_loop -1 -i own-clip.mp4 -c copy -f rtsp -rtsp_transport tcp rtsp://127.0.0.1:8554/testWhat to verify
Compare first image, reconnect and error logs, then stop the publisher and server after the test. Keep this result separate from compatibility with a real camera.
Sources and scope
AeoCam is available for Windows. Camera settings below describe protocol preparation, not a certification of a particular camera or a promise of every feature in every app version. Check the installed build and the Microsoft Store listing for current availability.
Vendor documents describe the camera or protocol. No physical-camera compatibility test is claimed here. Menus and capabilities can change with model and firmware.