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 2.0 version, transport, codecs, registration limits and DTMF behaviour.
- Name the target Asterisk, 3CX or other 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 confirm unlock control.
3. Check ONVIF and NVR/VMS fit
Request the ONVIF connection details, 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. A profile name is 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.
SIP / ONVIF / PBX compatibility checklist
Before requesting a quotation, provide the PBX or registrar, extension count, codec and transport, ONVIF or NVR/VMS target, PoE budget, VLAN and firewall rules, door-control interface, firmware version and acceptance tests. This gives the supplier one review boundary instead of a protocol label.
- PBX or registrar: Asterisk, 3CX or another named platform and version.
- Call flow: entrances, extensions, groups, mobile endpoints and fallback route.
- Video path: NVR/VMS model, ONVIF profile, RTSP streams, codec and event scope.
- Network: PoE class, switch or injector budget, VLAN, firewall, NAT and backup power.
- Door control: relay, Wiegand, RS-485, OSDP, controller or lift interface.
- Evidence: model, hardware revision, firmware, sample test and acceptance owner.
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.
Model mapping and document route
Use the SIP product page for the TD-D801 model record and connection scope. The TD-R50 indoor monitor page covers the TCP/IP indoor-unit route. Download the available data sheets from Resources → Downloads and put the exact model, revision and destination in the RFQ.
Decision matrix for SIP and ONVIF projects
Use the following record before comparing a product-family claim. It turns the selection into a reviewable brief and keeps the PBX, recorder, network and door-control owners aligned.
| Question | Evidence to request | Release condition |
|---|---|---|
| Who receives the call? | Entrances, units, extensions, groups, mobile endpoints and fallback route. | The call flow is tested on the named PBX or registrar. |
| What does the recorder need? | NVR/VMS model, ONVIF profile, RTSP stream, codec, events, audio and retention owner. | Discovery, authentication, stream and required events pass on the exact firmware. |
| How is the site powered? | PoE class or injector, cable route, switch budget, VLAN, backup and recovery owner. | Power and network loss tests have a named pass result. |
| How does the door release? | Relay, Wiegand, RS-485, OSDP, API or separate controller; voltage and emergency path. | Normal, denied and emergency behaviours are witnessed independently of video. |
| Which record is approved? | Model, hardware revision, firmware, documents, sample result and unresolved changes. | The quote names one configuration and a person who closes each open item. |
Model evidence to attach to the RFQ
| Model route | Listed reference | Boundary |
|---|---|---|
| TD-D801 SIP route | SIP 2.0, IEEE 802.3af Class 3, Wiegand 26/34-bit and RS-485. | Confirm firmware, option set, PBX/NVR/VMS and door-control test. |
| TD-R50 indoor route | 10.1-inch display, 1024 × 600, TCP/IP and up to 8 sensors. | Confirm sensor type, management-center path, power and site topology. |
| Document route | Model-specific data sheet and revision record. | Attach the selected revision and destination scope to the quotation. |
Use the TD-D801 model record for a model-specific interface review, the TD-R50 indoor monitor page for the TCP/IP endpoint route, and the Downloads library for the document revision. These pages are starting evidence; final compatibility still belongs to the selected model, firmware and project test.
Close the review with four witnessed events
Before purchase approval, capture a normal call, a video or audio failure case, a door-release event and recovery after a power or network interruption. Record the test owner, date and exact configuration. If a requested feature is not in the evidence pack, leave it open or scope it out instead of treating the protocol name as approval.
SIP and ONVIF questions
Does SIP guarantee ONVIF or NVR/VMS compatibility?
No. SIP registration and an ONVIF label do not guarantee the same video, audio, event or authentication behaviour on every NVR or VMS. Test the selected model, firmware and named recorder before acceptance.
What should be checked before connecting Asterisk or 3CX?
Record the PBX version, transport, codecs, registration limits, DTMF, authentication, NAT, TLS or SRTP requirements and door-release behaviour, then test the selected model and firmware on that PBX.
What belongs in a SIP video intercom RFQ?
Include building scale, entrances, extension count, PBX, NVR or VMS, network and PoE budget, door-control interface, firmware, destination market, document scope and the acceptance tests required before handover.
Send the unit or door count, target PBX/NVR, network condition, interfaces and destination market.
Request a SIP/ONVIF review WhatsApp