Trudian
Home›Knowledge Center›SIP and ONVIF selection
Product Selection & Integration

How to Choose a SIP Video Intercom with ONVIF

A SIP and ONVIF label is only a starting point. Select the system by mapping the PBX, NVR/VMS, network, door-control interface and acceptance evidence to the actual project.

Updated 23 August 2026 · Reviewed for MDU, business-center and commercial-building planning
Short answer: Name the building scale and call flow first, then verify SIP registration on the target PBX, ONVIF profiles and streams on the target NVR/VMS, PoE and network conditions, door-release interfaces, firmware and the acceptance tests required before purchase.

1. Start with the building and call flow

Record unit or tenant count, entrances, controlled doors, indoor stations, mobile endpoints, reception routes and lift or gate requirements. For a business center or mixed-use office, a multi-tenant project may route one entrance call to a resident, commercial suite, receptionist or SIP group, so directory and exception rules belong in the brief.

2. Check SIP and PBX fit

  • Confirm SIP version, transport, codecs, registration limits and DTMF behaviour.
  • Name the target Asterisk, FreeSWITCH, 3CX, hosted or enterprise PBX and test the actual firmware.
  • Record authentication, NAT, TLS/SRTP, simultaneous ringing, mobile push and door-release behaviour.
  • Separate the call-signalling path from the lock or controller path; SIP support alone does not certify unlock control.

3. Check ONVIF and NVR/VMS fit

Request the supported ONVIF profiles, RTSP streams, codec limits and event scope for the selected model and firmware. Test discovery, authentication, live video, audio, time sync, motion or door events, relay events and recovery on the named NVR or VMS. Profile names are not a substitute for a device-level acceptance test.

4. Check PoE, network and power resilience

  • Confirm IEEE 802.3af/at class, switch or injector budget, cable route and backup power.
  • Define IP addressing, VLAN, firewall, NAT and remote-support boundaries.
  • Test reboot recovery, loss of connectivity and the behaviour expected when the PBX or cloud path is unavailable.

5. Map the door-control interface

Specify whether release uses a dry relay, Wiegand, OSDP, RS-485, API or a separate controller. Confirm voltage, direction, credential authority, bus addressing, authentication, emergency release and failure behaviour against the named controller, smart lock, gate or lift equipment.

6. Require an evidence-backed quotation

The quotation should name the model and hardware revision, firmware, PBX/NVR/VMS targets, interfaces, certificates, sample terms, acceptance scenarios, document set and owner for unresolved changes. Do not treat a generic compatibility list, product-family claim or profile badge as project approval.

Need a model-specific selection review?

Send the unit or door count, target PBX/NVR, network condition, interfaces and destination market.

Request a SIP/ONVIF review