Identify ordinary, fisheye or multi-sensor operation
Milesight’s ordinary-camera examples distinguish main, sub and third streams, while the same document gives separate instructions for other camera families. A two-sensor or multi-directional device needs a sensor-specific selection as well as a stream selection.
Fisheye cameras add a display and transfer-mode decision. The cited user manual discusses primary and secondary stream URLs in relation to bundle-stream mode. Do not assume that a dewarped view in the manufacturer’s application corresponds to a separate RTSP resource in every configuration.
Connect the intended image step by step
- Record the full model, firmware and number of sensors. Identify whether the stream comes from the camera itself, a recorder or a VMS service.
- Sign in to the local camera configuration and check the actual RTSP port, enabled encoders and account permissions.
- For an ordinary supported camera, choose the documented main, sub or third stream. For fisheye or multi-sensor models, consult the matching family section before constructing an address.
- Check any fisheye transfer mode or sensor index that changes the exported image. Preserve the current configuration if another recorder already uses it.
- Add the confirmed local URI and credentials to SmartRTSP, verify the expected sensor image, then test reconnect behavior and a lower-bandwidth enabled stream if useful.
rtsp://<camera-ip>:<configured-rtsp-port>/mainDo not confuse an NVR channel with a camera encoder
Recorder and VMS output can use a different channel-based address. In that case the recorder or server is the network endpoint, and its user permissions and stream mapping apply. The main-camera example above should not be pasted at an NVR address without the recorder’s instructions.
When one image is missing from a multi-camera installation, identify which physical endpoint supplies that image before changing credentials. A recorder account working for one channel may not permit another channel, and a direct camera account may have no meaning to a VMS service.
Diagnose the selected profile before adding features
| Observation | Targeted check |
|---|---|
| Wrong lens or view | Inspect sensor number, fisheye display mode and the family-specific URI. |
| Unauthorized stream | Check credentials and live-view permissions on the device supplying the stream. |
| Black or unstable image | Check the enabled encoder, video compression, frame rate and local connection. |
| Video works but control does not | Verify the model’s separate ONVIF/PTZ capability and the viewer’s implementation. |
Check each feature independently
Start on the same local network with the exact model, firmware and account permissions. A working video stream does not prove support for ONVIF discovery, pan or tilt, two-way audio, events, or every recording feature. Test the features you need in your installed SmartRTSP app.
Keep camera credentials private. Do not expose camera ports to the public internet just to test local viewing. Manufacturer cloud accounts, device accounts and generated sharing links are not interchangeable.
Frequently Asked Questions
Is /main correct for every Milesight camera?
No. It is an ordinary-camera example. Use the specific fisheye, dual-sensor or multi-directional instructions where applicable.
Does a dewarped manufacturer view guarantee the same RTSP view?
No. Check the camera’s transfer and display modes and the media resource actually exposed in that configuration.
What is the verification boundary?
Documentation was checked on 2026-10-18. This guide does not claim physical tests of every model or certification of audio, analytics or PTZ functions.
Official sources and scope
Read the documentation for the exact model before changing settings. Manufacturer menus, firmware and service availability can change. These sources explain the published connection conditions, not independently verified SmartRTSP hardware compatibility.