An ONVIF compliant video intercom is one whose specific model and firmware conform to one or more ONVIF profiles, so that an NVR or VMS can discover it and use the functions that profile defines. "ONVIF compliant" on its own does not say which profile, which firmware or which functions, and it never covers door release by default. This guide explains which profiles matter for an intercom, how to check a conformance claim, and how to test video, audio, events and door release with the named recorder. It is written for distributors, integrators and property teams defining a written project scope.
What "ONVIF compliant" means for a video intercom
ONVIF is an industry forum that publishes interface specifications for IP security products. A product is described as conformant to a profile, not to ONVIF as a whole, and the claim applies to the model and firmware that were declared. Each profile groups a set of functions; a client such as an NVR or VMS can only rely on the functions that both the intercom and the client implement for the same profile.
For a buyer this means three questions, in this order: which profile does the recorder need, does the exact intercom model and firmware declare that profile, and has the required function been tested on the named recorder.
Which ONVIF profile does the project need?
The profiles below are the ones most often raised in intercom projects. Use the table to decide what to ask for, then confirm each function with the target NVR or VMS. Profile scope is defined by ONVIF; check the current profile specifications at onvif.org rather than relying on a datasheet summary.
| Profile | What it is used for in an intercom project | What to test on the named recorder |
|---|---|---|
| Profile S | Basic video streaming and device configuration. This is what most "add camera via ONVIF" workflows use for the panel's camera. | Discovery, authentication, live view, recording, stream after reboot. |
| Profile T | Advanced video streaming, including newer codecs and richer event handling. Ask whether the recorder needs it before treating it as a requirement. | Selected codec and resolution, event delivery, audio if declared. |
| Profile G | Edge storage and recording retrieval, relevant only if the panel stores recordings locally. | Browse and retrieve recordings, behaviour after a network interruption. |
| Profile M | Metadata and analytics events, relevant when the VMS consumes analytics from the panel. | Named event types arrive with the expected labels. |
| Profile A / C | Access-control configuration and door control. Most video intercoms do not declare these; door release normally follows a separate relay, controller or API path. | Only if declared: door command, permissions, failure behaviour. |
How to check an ONVIF conformance claim
- Ask for the exact model, hardware revision and firmware the claim applies to.
- Ask which profile or profiles are declared for that firmware.
- Check the claim against ONVIF's public list of conformant products at onvif.org, or ask for the declaration document.
- Name the recorder model and version, and test the required functions on it. Conformance on both sides improves the odds; it does not replace the test.
Procurement checklist
Before selecting an ONVIF-enabled intercom device, verify:
- Required ONVIF profile and firmware version.
- Video stream and codec requirements.
- NVR or VMS model compatibility.
- Door release and event integration requirements.
- On-site testing and commissioning process.
Connect the intercom to the NVR or VMS
Step 1: Network Discovery
Confirm the network path and discovery method required by the selected intercom and NVR/VMS. If automatic discovery is unavailable, add the device using the documented address and credentials, then record the result.
Step 2: Credentials
Confirm the authentication method and account permissions required by the selected intercom and NVR/VMS. Use a dedicated connection account where supported and record the permissions used in the acceptance test.
Step 3: Stream Configuration
Request the available RTSP stream details and configure the named NVR/VMS to the model's documented codec, resolution and bitrate limits. Record the selected stream and verify live video, recording and recovery.
Step 4: Define the door-release connection path
Treat video connection and door control as separate acceptance tests. The NVR or VMS may receive video from the panel through ONVIF or RTSP, while the door-release command follows a separately documented connection path.
Review one of the following methods against the named panel, firmware and NVR/VMS version:
- Controller or I/O relay: the NVR/VMS triggers an approved relay or access-control controller.
- Documented device API: the NVR/VMS or its approved module sends a command only where the manufacturer provides the API and authentication method.
- Supported ONVIF function: use an ONVIF output or access-control function only where the exact device and client document it and the proposed connection has been tested.
Before handover, test operator permissions, command logging, relay duration, fail-safe or fail-secure behaviour, network-loss behaviour and the approval workflow. Video streaming support does not by itself confirm a door-release connection.
Step 5: Event Rules
Define the required recording trigger, duration and event label with the named NVR/VMS. Test the button, motion, door and recovery events on the exact model rather than assuming a standard event name.
Test the connection with the named NVR or VMS
| Target system | Connection checks | Door-release review |
|---|---|---|
| Named NVR/VMS | Discovery, credentials, stream and codec | Documented event or relay path |
| Target firmware | Audio, metadata and event scope | Authentication and failure behaviour |
| Acceptance record | Live view, recording and recovery | Release test witnessed and documented |
Test two-way audio separately
Two-way audio is the most variable feature in an ONVIF connection. Confirm the required audio direction, codec and backchannel behaviour with the named NVR/VMS, then test it separately from video discovery before committing the project specification.
Frequently Asked Questions: ONVIF Video Intercom Connection
Request the ONVIF connection details, RTSP streams, codec limits and event scope for the selected model and firmware. Confirm which features the named NVR or VMS accepts, then run discovery, authentication, video, audio and relay tests before approval. Profile labels are not a substitute for a device-level acceptance test.
No. An ONVIF label does not guarantee the same features on every NVR or VMS. Stream encoding, authentication and event handling can differ by firmware. Always test the selected intercom with the named NVR or VMS before deployment.
The door-release path depends on the selected intercom, controller and NVR/VMS. Review the documented device function, controller or I/O relay, and dry-contact wiring with the project team. Test permissions, release duration and failure behaviour on the named equipment before approval.
Two-way audio support varies by the selected intercom, firmware and VMS. Confirm the required audio direction, codec and backchannel behaviour with the named equipment, and test it separately from video discovery.
Confirm the network path, discovery method, credentials, firewall rules and stream ports required by the selected intercom and NVR/VMS. If automatic discovery is unavailable, document the manual device-add process and test recovery after a reboot or address change.
An ONVIF connection can be reviewed for a named NVR or VMS. Add the device using the method documented by that system, provide the requested address and credentials, and test video, audio, events and door release on the exact firmware before deployment.
Request the model-specific ONVIF record, stream details, credentials, audio direction, event scope and door-release method. Ask for a connection check with your NVR or VMS model and firmware, then record the acceptance result before purchase.
It means the specific model and firmware conform to one or more ONVIF profiles, so a recorder that supports the same profile can use the functions that profile defines. The claim should name the profile and firmware. It does not cover door release unless an access-control profile is declared and tested.
Most NVR connections use Profile S for the panel's video stream. Profile T is relevant when the recorder needs advanced streaming or event handling, Profile G when recordings are stored on the panel, and Profile M when the VMS consumes analytics metadata. Ask the recorder side which profile it requires before writing the specification.
Ask for the exact model, hardware revision, firmware and declared profiles, then check them against ONVIF's public list of conformant products at onvif.org or the declaration document. Finally, test the required functions on the named NVR or VMS, because conformance on both sides does not replace a project test.
ONVIF Video Intercom Systems — OEM & Wholesale
Trudian SIP 2.0 video intercom panels can be reviewed for an ONVIF connection with a named NVR/VMS. Confirm the model, firmware, stream, audio and event requirements before approval. The TD-D801 datasheet lists IP65 and a 2MP camera; CE documentation is confirmed by model and destination. OEM and private-label scope starts at 500 units.