ONVIF vs RTSP: compare the functions
Choose ONVIF for the supported camera services your NVR needs. A manual RTSP connection can suit a stream-only integration when both devices support it. ONVIF and RTSP can work together; adding a stream alone does not establish complete camera compatibility.
| Task | ONVIF | RTSP connection |
|---|---|---|
| Find a camera | Device discovery where supported and enabled. | Use a known stream URI; RTSP alone does not provide ONVIF discovery. |
| Video setup | Request supported settings and a stream URI. | Control the media session; media normally travels over RTP. |
| PTZ and events | Check services, profiles and both devices' support. | Not guaranteed by working video; a separate supported integration is needed. |
| Audio | Verify codec, direction and device/client features. | Possible with a supported audio stream and decoder; two-way talk needs its own check. |
An NVR can obtain the stream URI through ONVIF, then use RTSP to start the session. A stream may also include ONVIF metadata, but the receiver must understand it before it can act on an event. See the ONVIF Streaming specification and RTSP 1.0 specification. Choose and check the NVR connection.
Match the device and the client
The camera usually supplies video as a device; the NVR or video management software receives it as a client. Look up both products in the ONVIF conformant products database, and record the listed role, profiles and firmware or software version. A similar model name is not an exact match.
If a listing cannot be found, keep the supplier's interoperability claim separate from official conformance. Working video can demonstrate one tested function, but it does not create a conformance record.
Add the camera to an NVR: choose and check the connection
- Confirm the network path. Record the models and firmware. Check camera reachability from the NVR's intended camera network; its private PoE network can differ from the site LAN. Preserve current address settings.
- Try the supported ONVIF integration. Match both products and required profiles. Use the documented ONVIF service, account and permissions. If discovery fails, check reachability and whether discovery is supported and enabled; use a known address only if the NVR supports manual ONVIF addition.
- Use manual RTSP where supported. Obtain the exact stream URI from the manufacturer. Confirm the RTSP version, authentication, codec and transport the NVR accepts. RTSP 2.0 is a separate revision; do not assume it works with a 1.0-only device. Keep credentials out of shared URLs and screenshots.
- Compare the results. If RTSP video works but ONVIF addition fails, check the ONVIF service, account and profile match. If neither produces video, check the network path, credentials and selected stream. If video works but events or PTZ do not, check those integrations separately; changing the stream URI alone is not a fix.
Verify a new recording and playback using the chosen connection, then test required audio, events and controls separately. Keep authentication enabled. Discovery uses a separate mechanism described in the ONVIF Core specification; RFC 7826 defines RTSP 2.0.
Select profiles by the required function
| Requirement | Profile to examine | Combination to verify |
|---|---|---|
| Video streaming | Profile T; Profile S for existing integrations | Device/client support, codec, stream settings and required controls. |
| Access to recordings on a device | Profile G | Recording configuration, retrieval and playback in the intended client. |
| Analytics metadata and events | Profile M | The specific event or metadata, and what the receiving software can do with it. |
Profiles contain mandatory and conditional features. Profile T covers advanced streaming, including H.264/H.265 and related functions, but do not infer every audio, PTZ or event feature from its name. Confirm the implemented features on both sides. ONVIF metadata support also does not establish AI detection accuracy.
Profile S transition for existing systems
ONVIF lists March 31, 2027 as the final date for new Profile S product conformance submissions. This is not a date when installed cameras automatically stop working. Its Profile S page and transition Q&A explain the change.
For a new selection, evaluate Profile T and the manufacturer's supported authentication and update path. For an existing integration, confirm the effect of firmware and authentication changes before rollout. The Q&A advises moving away from the older username-token authentication method; an existing Profile S listing alone is not a security assessment.
Video works, but event recording does not
Find where the event chain stops
Create a controlled motion test during an active detection period. Check the camera's detection first, event arrival at the recorder second, and a saved clip third.
| Observed result | Next check |
|---|---|
| No detection at camera | Enabled detector, area and active period. |
| Detection, no recorder event | Supported event type, account permissions and event communication. |
| Event arrives, no clip | Recorder event action, channel schedule and storage. |
Profile T includes motion-alarm and event-handling functions. It does not guarantee that proprietary person/vehicle classifications transfer between every camera and recorder. See the Profile T specification, sections 7.7 and 7.20.
Audio or another camera function is missing
Follow audio through the selected stream
Confirm the microphone or audio input, then compare camera-local audio, recorder live audio and a new saved clip. Check viewer audio permission and mute settings. If local audio works but recorder audio fails, compare the selected profile and supported audio encoding.
Audio streaming is conditional in the Profile T specification, section 8.9. Two-way talk needs a separate check of output and client support. The Axis audio troubleshooting reference explains path checks; its settings belong to Axis equipment.
If a camera cannot be discovered, check reachability from the recorder's intended camera network. Its private PoE network may need a different connection path from the site LAN. Preserve address settings before changes; confirm the path, camera account and supported connection method with the installer. Discovery alone does not establish compatibility.
For no picture, check reachability, ONVIF account/permissions and a supported stream. For missing PTZ or a multi-sensor view, check exposed controls/streams and channel assignment on the exact pair. Follow documented setup without disabling authentication or exposing the camera to make discovery work.
Record a result for each required function
Use the intended camera, recorder, firmware and user role. Check live view, scheduled recording, playback and export. Then trigger each required event and test an audio sample, PTZ or edge-recording retrieval where relevant. Record video, event clip and audio as separate passed, failed or not-tested results, keeping a clip or log for each. Before a proposed firmware fix, confirm the exact hardware, release notes, backup procedure and maintenance window.
Repeat affected checks after an upgrade. Include the equipment list and required functions when you request a compatibility review. For the recorder's channel and load limits, use the NVR sizing guide.