
Most installers hit the same wall on their first mixed-brand job: the camera works fine on its own app, but the moment they try to pull video into a recorder or a software platform from another vendor, nothing shows up. The fix is almost always a small set of settings around two standards: RTSP and ONVIF.
This guide walks through the complete IP camera RTSP and ONVIF setup process, from what the two protocols actually do to enabling them on the camera and confirming the stream is live. It is written for installers, system integrators, and anyone wiring cameras into a recorder or VMS that did not come in the same box.
By the end you will know how to build a working RTSP URL, turn ONVIF on with the right credentials, pair the camera with an NVR, and verify the whole chain with free tools before you leave the site.
The good news is that neither protocol requires special licensing or proprietary software. Everything in this guide uses the camera web interface, a web browser, and open tools, so the same steps apply whether you are integrating two cameras or two hundred.
What Are RTSP and ONVIF in IP Cameras?

RTSP carries the video stream, while ONVIF handles discovery, configuration, and control between devices from different brands.
RTSP Is the Delivery Pipe for Video
RTSP stands for Real Time Streaming Protocol. In a surveillance system it is the standard way a client asks a camera or recorder to send a live video stream, then receives that stream over the network. It does not record, analyze, or manage anything on its own; it only negotiates and delivers the media.
An RTSP URL usually contains the camera’s IP address, RTSP port, and stream path. A common format is:
rtsp://[username]:[password]@[camera-ip]:554/[stream-path]
For example, a test address may look like:
rtsp://192.168.1.100:554/[stream-path]
The stream path identifies the video channel and stream type. Its format varies by manufacturer and camera model. Check the camera’s web interface or technical manual for the exact main stream and sub stream paths. Avoid sharing RTSP URLs that contain embedded login credentials.
ONVIF Is the Common Language for Device Control
ONVIF is a global standard maintained by the Open Network Video Interface Forum. It defines a set of web services that let cameras, recorders, and software platforms discover each other, exchange settings, and control functions such as pan, tilt, zoom, and event streams, even when the hardware comes from different manufacturers. The specification is organized into profiles, each covering a group of features, so a device can claim conformance to a specific profile rather than to an abstract idea of compatibility.
Think of ONVIF as the handshake layer. A camera that conforms to an ONVIF profile can be found by a compliant NVR, have its media profiles read, and be added to the recorder without vendor-specific drivers. Our article on ONVIF IP camera compatibility covers what to check before you buy hardware for a mixed system.
RTSP vs ONVIF: What Does Each Protocol Do?

The two standards are not competitors; they solve different parts of the same job, and most integrations use both at once.
What RTSP Handles
RTSP is concerned with one task: getting video and audio from the camera to a viewer or recorder in real time. It carries the media, manages start and stop requests, and lets the client choose parameters such as the stream type. It does not know anything about camera settings, users, or events. Because it is transport-level, RTSP is the fastest way to confirm a camera is actually producing video, since it skips everything except the media itself.
What ONVIF Handles
ONVIF covers everything around the stream: device discovery, authentication, network and imaging configuration, PTZ commands, and event notification. When you add a camera to an NVR and the recorder automatically lists the available resolutions and lets you move the lens, that is ONVIF working behind the scenes. The standard keeps the integration layer consistent, so a site with three camera brands can still be managed as one system from a single recorder.
| Aspect | RTSP | ONVIF |
|---|---|---|
| Primary job | Streams live video and audio | Discovery, settings, PTZ and events |
| Address style | rtsp:// URL with channel and stream | Web services over HTTP or HTTPS |
| Typical port | 554 | 80 or 443 (service varies by vendor) |
| Used for | Pulling a live view into a player or VMS | Adding and managing the camera in an NVR |
How the Two Standards Work Together
In practice a single camera serves both at once. The NVR uses ONVIF to find the camera, authenticate, and read its profiles, then receives the actual pictures over an RTSP stream. If either layer is misconfigured, the integration breaks in a different way, so it helps to know which one to check first when something goes wrong.
What You Need Before Setting Up RTSP and ONVIF
A working setup starts with three known values: the camera IP address, a login account, and the correct stream path for that brand.
Camera Network Details
Write down the camera IP address, its HTTP port, and the username and password. Most cameras use a fixed IP or DHCP reservation on the local network. The camera and the recorder or workstation must be able to reach each other, which usually means they sit on the same subnet or have a routed path between them. On larger sites, confirm that no firewall rule blocks port 554 or the ONVIF service ports.
Tools for Verification
- A web browser on the same network to open the camera web interface.
- VLC Media Player to test a raw RTSP URL.
- An ONVIF tool such as ONVIF Device Manager to confirm discovery.
Building a mixed-brand system? Bokysee manufactures ONVIF-compliant IP cameras that drop into Hikvision, Dahua, and third-party recorders, with OEM and ODM support for your own brand.
Talk to the Bokysee team →How to Enable RTSP and ONVIF on an IP Camera

Both features usually ship turned on, but the credentials and stream path are brand-specific, so confirm them before you rely on the feed.
Turning On the Integration Protocols
Log in to the camera web interface and look for a menu named Network, Integration, or Platform Access. Enable RTSP and ONVIF, then set the authentication method. Many cameras default to digest or basic authentication; match this to what the NVR or VMS expects.
While you are there, note the RTSP path shown in the interface, because some vendors expose a ready-made URL you can copy instead of assembling it by hand. On cameras that ship with these features off by default, the toggle is usually a single checkbox, followed by a save and a quick device reboot.
Creating a Dedicated ONVIF Account
Create a separate user with ONVIF access rather than reusing the admin account everywhere. This keeps the password out of every recorder and client, and lets you rotate it later without breaking the main login. It also limits the damage if one recorder is ever compromised, since that credential only exposes camera streams and settings rather than full device administration. A short list of the exact stream paths for common brands is covered in our guide to main stream and sub stream settings.
How to Add an IP Camera to an NVR or Third-Party VMS

An NVR adds a camera through ONVIF in seconds; a software VMS often wants the RTSP URL pasted in directly.
Adding the Camera Through ONVIF
Open the NVR camera management page and run an ONVIF device search on the camera subnet. The recorder lists the discovered device with its IP and model. Select it, enter the ONVIF username and password, and the NVR reads the available profiles and starts recording.
If the search returns nothing, add the camera manually by IP address and protocol rather than waiting on discovery, which can fail on routed or isolated subnets. The full sequence for a specific brand mix is laid out in our Dahua to Hikvision ONVIF walkthrough.
Connecting a Software VMS by RTSP
Platforms such as Blue Iris, Milestone, Synology Surveillance Station, or ZoneMinder accept either ONVIF discovery or a direct RTSP URL. When ONVIF discovery fails, paste the RTSP address and the stream shows up within seconds. This is the fallback that resolves most stubborn integrations. Point the recorder at the sub stream for live wall views and keep the main stream reserved for high-quality recording, so a large site does not swamp its own bandwidth.
How to Verify RTSP Streaming and ONVIF Device Compatibility

Test the raw stream before you troubleshoot anything else; a stream that plays in VLC proves the camera side is correct.
Testing the RTSP URL in VLC
Open VLC, select Open Network Stream, and enter the camera’s RTSP URL. If authentication is required, provide the username and password through the available credential prompt or connection settings. Avoid sharing URLs that contain embedded credentials, and store camera login details securely during project handover.
If VLC displays the video, the RTSP address, authentication details, and stream are working from the test workstation. This does not confirm that every NVR or VMS can decode the same stream. If the recorder still fails to connect, check network access, supported video codecs, authentication methods, and stream settings. If VLC cannot play the feed, verify the RTSP port, URL path, username, and password first.
Confirming ONVIF Discovery
Run ONVIF Device Manager from a workstation on the same network. It performs a multicast discovery and lists every conformant device. Selecting the camera shows its profiles, capabilities, and the streams it exposes. If the camera does not appear, re-check that ONVIF is enabled and that the account has the right permissions, then try a manual add using the camera IP address. The specification itself is published by the ONVIF forum for deeper reference.
Frequently Asked Questions About RTSP and ONVIF Setup
What is the default RTSP port for IP cameras?
The default RTSP port is 554. Most cameras listen on this port unless it has been changed, and a stream URL is addressed to port 554 when no port is specified.
Can I use RTSP without ONVIF?
Yes. RTSP works on its own to pull a live stream into a player or VMS as long as you have the correct URL and credentials. ONVIF is only needed for automatic discovery and device control.
Why does my NVR not find the camera on ONVIF?
The most common causes are a camera on a different subnet, ONVIF disabled in the camera settings, or an account without ONVIF permissions. Confirm the network path and the dedicated ONVIF user before retrying.
How do I find the RTSP URL for my camera brand?
The URL is brand-specific, so check the camera manual or the vendor integration guide. Most follow a pattern that includes the channel number and either the main stream or the sub stream.
What is the difference between main stream and sub stream in RTSP?
The main stream is the high-resolution feed used for recording, while the sub stream is a lower-resolution feed used for live multi-view display. Choosing the right one depends on whether you need detail or bandwidth efficiency.
Does ONVIF work between any two camera brands?
In most cases, yes, because ONVIF defines a shared interface rather than a vendor-specific one. Both devices must support the same ONVIF profile for the features you want to use.
Final Thoughts on RTSP and ONVIF Setup
RTSP and ONVIF turn a pile of cameras from different vendors into one system you can actually manage. RTSP gives you the video pipe, ONVIF gives you the handshake, and together they make mixed-brand installs routine instead of risky. The order that works in the field is simple: enable the protocols, create a dedicated account, add the camera through ONVIF, and fall back to a direct RTSP URL when a platform refuses to discover it.
Once the stream is live and verified, record the URL, the credentials, and the ports in your project documentation. Those three lines save hours on every future service call, because they are exactly the details a technician needs to rebuild the connection from scratch.
Get those four steps right and you leave every site with a verified feed, not a callback. If you are building out a product line that needs to plug into third-party recorders out of the box, talk to Bokysee about ONVIF-compliant cameras and OEM support.
