Security integrators increasingly need video intercom panels to appear inside the same VMS interface as the rest of their CCTV cameras. ONVIF compliance is the key — but "ONVIF-compliant" covers a wide range of capabilities depending on which profiles and features are implemented. This guide explains exactly what to look for and how to configure the integration.
ONVIF Profile Overview
ONVIF defines standardised interfaces for IP security products. For video intercom integration, the relevant profiles are:
Profile S — Live Streaming
The baseline profile. Enables the NVR or VMS to discover the intercom on the network, subscribe to its RTSP video stream (H.264 or H.265), and control PTZ if present. This is the minimum required to see the intercom's camera feed inside a VMS like Milestone, Genetec, or Hikvision iVMS.
Profile T — Advanced Streaming
Extends Profile S with H.264/H.265 streaming, motion detection events via ONVIF Events interface, on-screen display, and metadata overlays. Required if the VMS uses motion triggers from the intercom camera for recording rules.
Profile G — Edge Storage
Enables the VMS to browse and retrieve recordings stored on the intercom's SD card. Useful for sites where the intercom has local recording but the NVR is not always reachable. Optional for most integrations.
Profile A — Access Control
Maps door-release (relay output) to an ONVIF access point event. Enables the VMS operator to press a button in the VMS interface to unlock the door, and to see access events in the VMS event log. Not all intercoms implement Profile A — often the relay is exposed separately via HTTP API or dry contact wiring.
Integration Steps: Connecting to NVR or VMS
Step 1: Network Discovery
Ensure the intercom panel and the NVR/VMS server are on the same network segment, or that ONVIF WS-Discovery UDP multicast is allowed across VLANs. In the VMS, use "Add Camera by Network Discovery" or "ONVIF Device Discovery" — the intercom should appear automatically. If not, add it manually by IP address and select ONVIF as the driver.
Step 2: Credentials
ONVIF requires a username/password. The intercom's web interface should have a section for ONVIF user accounts separate from the general admin account. Create a dedicated ONVIF user with appropriate permissions. Some VMS platforms require the ONVIF account to have "Administrator" role on the device to access all capabilities.
Step 3: Stream Configuration
Configure the RTSP stream to match the VMS requirements: H.264 Baseline or Main profile, resolution typically 1080p for main stream and 720p or D1 for sub-stream. Set the bitrate within the VMS recording bandwidth budget. For intercoms with a wide-angle lens (typical 140–170° for door panels), enable digital dewarping in the VMS if supported, or accept the fisheye view.
Step 4: Door Release Integration
There are three common methods:
- ONVIF Profile A (Output Relay): VMS sends an ONVIF relay output command. The intercom triggers its relay to release the door. Most integrated and seamless method.
- HTTP API: VMS calls a custom HTTP endpoint on the intercom (e.g.,
GET /cgi-bin/relay?action=open&token=xxx). Requires VMS scripting support (available in Milestone and Genetec via custom plugins or HTTP trigger modules). - Dry contact wiring: VMS connects a relay output board to the intercom's door release input. Simple and reliable but requires additional hardware and cabling.
Step 5: Event Rules
Set up recording rules: start recording when the intercom button is pressed (ONVIF Event: "InputEvent" or "ButtonPress"), record for 60 seconds, and flag as a bookmark. This gives operators a searchable clip for every visitor event without continuously recording idle footage.
VMS Compatibility Notes
| VMS Platform | ONVIF Support | Door Release Method |
|---|---|---|
| Milestone XProtect | Profile S/T/G via ONVIF driver | Output relay via ONVIF or I/O module |
| Genetec Security Center | Profile S/T via Omnicast driver | ONVIF Profile A or Synergis AC module |
| Hikvision iVMS-4200 | Profile S/T native | Relay via iVMS alarm linkage |
| Dahua DSS/CSS | Profile S/T native | Relay via Dahua alarm linkage |
| Nx Witness / Nx Meta | Profile S/T via ONVIF auto-detection | HTTP API soft trigger or relay |
Two-Way Audio in VMS
Two-way audio is the most variable feature in ONVIF intercom integration. ONVIF defines audio backchannel via the ReceiveAudioSink service, but VMS support is inconsistent. Milestone XProtect supports audio backchannel with ONVIF Profile T devices using the "Push to Talk" interface. Genetec requires an Intercom plugin from the Synergis Access Control module. Hikvision and Dahua VMS support backchannel natively for their own panels. For third-party intercoms, test two-way audio specifically before committing to a VMS choice in a project spec.
Frequently Asked Questions: ONVIF Video Intercom Integration
Profile S is the minimum requirement for live video streaming from an intercom to an NVR or VMS. It enables network discovery, RTSP stream subscription (H.264 or H.265), and basic camera control. Profile T adds motion detection events and metadata overlays, required if your VMS uses motion triggers from the intercom for recording rules. Profile A is needed only if you want to control door release directly from the VMS interface. Most integrations require Profile S at minimum; Profile T is recommended for feature-complete integration.
No. ONVIF compliance means the device passes conformance tests for the declared profile, but interoperability between specific devices is not guaranteed. Implementation differences in stream encoding parameters, authentication methods, and event formats cause compatibility issues even between ONVIF-certified products. Always test with your specific NVR or VMS before deployment. Major VMS platforms — Milestone XProtect, Genetec Security Center, Hikvision iVMS-4200, Dahua DSS — publish compatibility lists; check these before purchasing intercom hardware.
There are three methods depending on the intercom's capabilities. ONVIF Profile A maps the door relay to an ONVIF access point, allowing VMS operators to trigger door release via a button in the VMS interface. HTTP API allows the VMS to send a GET or POST request to the intercom's local API endpoint to trigger the relay — requires VMS scripting support. Dry contact wiring connects the intercom's relay output directly to the VMS I/O module, triggering door release via a hardware signal. HTTP API is the most flexible and does not require ONVIF Profile A support.
Two-way audio support in VMS integrations varies significantly by platform. ONVIF Profile S includes audio streaming (G.711 or AAC), but many VMS platforms only implement one-way audio (listen only) from the camera feed. Full two-way audio — where the VMS operator can speak back to the visitor — requires the VMS to support ONVIF backchannel audio or a separate SIP integration. Genetec and Milestone support two-way audio for ONVIF devices that implement it correctly; verify with your VMS vendor before specifying intercom hardware.
The intercom and NVR/VMS server must be on the same network segment for ONVIF WS-Discovery (automatic device detection) to function — WS-Discovery uses UDP multicast which does not cross router boundaries by default. If they are on different VLANs, either configure multicast routing between VLANs or add the intercom manually by IP address in the VMS. Required open ports: TCP 80 or 8080 (ONVIF service), TCP 554 (RTSP stream), UDP 3702 (WS-Discovery). Assign a static IP to each intercom to prevent stream loss after DHCP lease renewal.
Yes, third-party intercoms can be added to Hikvision iVMS or Dahua DSS via ONVIF Profile S for video streaming. Go to the NVR's device management section, select "Add Device" and choose ONVIF as the protocol, then enter the intercom's IP address, port, and credentials. Note that Hikvision and Dahua NVRs are optimized for their own proprietary protocol (Hik-Connect / DMSS) and may not support all ONVIF features — particularly two-way audio and door release events — for third-party devices. Test door release and event trigger functionality specifically before deployment.
Verify: declared ONVIF profile (S, T, G, A) and whether the device is formally ONVIF-certified (check onvif.org conformant products database) or merely claims compatibility. Request the RTSP stream URL format and test it with VLC before purchase. Confirm two-way audio support if required. Ask for the HTTP API documentation for door release if Profile A is not supported. Request a compatibility confirmation for your specific NVR or VMS model and version. Avoid purchasing based on "ONVIF compatible" claims alone without testing — the spec allows significant implementation variation.
ONVIF Video Intercom Systems — OEM & Wholesale
Trudian SIP video intercom panels support ONVIF Profile S/T for NVR/VMS integration. CE certified, IP65, 2MP 1080p, H.264/H.265, RTSP. Available for OEM branding or white-label. Contact us for integration documentation and wholesale pricing.