Trudian
Products ↳ Video Intercom↳ SIP 2.0 Video Intercom↳ Villa Video Doorbell↳ 2-Wire Retrofit System ↳ Smart Locks↳ Smart Lock Display ↳ Access Control Solutions ↳ Multi-Tenant Video Intercom ↳ Apartments & MDU ↳ Apartments & MDU ↳ Offices ↳ Villas ↳ Government ↳ Co-Working Markets ↳ Middle East ↳ Europe ↳ United States OEM & ODM Distributor Program Insights Request a Quote
SIP video intercom ONVIF manufacturer · TD-D801 · SIP 2.0 · RFC 3261

SIP 2.0 Video Intercom Manufacturer for MDU and Commercial Entry

Use the TD-D801 for MDU or commercial entrances that need a SIP 2.0 door panel. The PBX, ONVIF/NVR path, firmware, credentials and destination requirements must be checked against the proposed configuration before quotation.

Request a SIP 2.0 Model Review Review document scope WhatsApp
SIP 2.0 / RFC 3261
ONVIF connection review
Server design: up to 9,999 extensions
Wiegand 26/34
CE / FCC / RoHS documentation review
IP65 / IK08
TD Series / D801 SIP 2.0 TD-D801 SIP 2.0 video call panel with face recognition and RFID
ONVIF S/TPoEWiegandIP65
TD-D801SIP 2.0 entrance panel · Trudian

Deployment Fit for MDU and Commercial Entry

Use SIP 2.0 when a door station must register to an existing PBX or share a call plan across multiple entrances. The PBX, network and lock interface set the final design.

SIP registration

Register the TD-D801 as a SIP endpoint on the named PBX. Verify transport, codecs, DTMF, authentication and door-release behaviour against the server configuration.

Unit and dial-plan capacity

The specification lists up to 9,999 apartment extensions in a SIP server design. Final capacity depends on the server, directory, entrance count and call-flow rules across towers, floors and mixed-use units.

PBX connection review

The TD-D801 can be reviewed for connection with Asterisk, 3CX or another PBX. Map the call flow to the target server and check licensing, mobile-answering and simultaneous-ringing rules before approval.

Power and network

PoE 802.3af carries power and data when the switch or injector has sufficient budget. Check the cable route, port allocation, VLAN, firewall and local backup-power requirement in the site design.

Video recording path

The panel can be reviewed for an ONVIF connection with a named NVR/VMS. Confirm the required stream, codec and event set, then test discovery, authentication, video, audio and relay events on the target firmware.

Transport security

SIP over TLS and SRTP are conditional on the selected firmware and PBX. Define certificates, cipher policy, NAT handling and logging requirements before commissioning.

SIP 2.0 Deployment & Connection Checklist

Before quotation, record the items below against the selected model, firmware and target infrastructure.

SIP / PBX

Record SIP 2.0, transport, codecs, registration limits, DTMF and inbound/outbound call tests for Asterisk, 3CX or the named PBX.

ONVIF / RTSP

Record the ONVIF request, RTSP streams, firmware and target NVR/VMS. Test discovery, authentication, video, audio, events and door-release workflow.

PoE / VLAN

Check the 802.3af power budget, cable route, IP plan, firewall and NAT. VLAN deployment is possible when the site policy and switch configuration permit it.

OEM / ODM Handover

For standard supply, OEM/private label or ODM scope, request the model-specific datasheet, configuration guide, sample terms, change-control record, certifications and acceptance checklist.

Use the SIP and ONVIF selection guide for product choice, the multi-tenant planning guide for entrances and units, the ONVIF connection checklist for NVR/VMS testing and the video intercom projects FAQ for buyer questions.

TD-D801 — Model Specification

The TD-D801 is a full-IP SIP 2.0 door panel with PoE, IK08 housing and optional Face ID and RFID access. Confirm the option set in the quotation.

UnlockingFacial recognition, password, card, QR code, indoor monitor and cloud platform remote control
Appearance size258 × 135 × 22.5 mm
MaterialLuxurious pure aluminium and tempered glass
Screen display8-inch LCD capacitive touch screen
Screen resolution800 × 1280
Camera2 million pixels
Operating systemLinux
CPUARM Cortex A7, 4 cores
Random access memory1G
Flash8G
Facial recognitionUp to 20,000 faces; liveness detection
Network modeTCP/IP
Reading distance0-6 cm
Card capacityUnlimited; read and write sectors
Power supplyDC 12V
Operating current550 mA
Standby current290 mA
Working temperature-40°C to +70°C
Working humidity10%-90%
Installation methodWall-mounted or embedded
Wall buried size246.6 × 117.2 × 13.5 mm
IP ratingIP65
FunctionsVideo call, camera surveillance, elevator control and smart advertising playback
Visitor messagePhoto and video
AlarmAutomatic detection of door opening and closing status
Remote online upgradeSupported
Trudian Community Management Center PlatformSupported
SIP protocolSIP 2.0 (RFC 3261)
Audio codecG.711 PCMU/PCMA, G.722 and G.729
Video codecH.265 / H.264
PoEIEEE 802.3af Class 3; up to 15.4 W
ONVIF / RTSPConnection available for review by model and firmware
Wiegand26-bit and 34-bit output
RS-485Multi-drop bus for elevator-control integration
Door releaseDry relay; 12V/1A output
SIP server capacityUp to 9,999 apartment extensions in a SIP server design
Request TD-D801 Datasheet & Model Review Download PDF Certification review

PBX Connection Review

The patterns below are starting points, not certification statements. Bench-test the named PBX, firmware and call flow before issuing a purchase order.

Asterisk / PBX
Confirm on target
3CX / hosted PBX
Confirm on target
Cloud SIP service
Confirm on target
Enterprise IP-PBX
Confirm on target
Existing IP-PBX
Confirm on target
RFC 3261 server
Standards-based

SIP Configuration Requirements

  • SIP 2.0 account on the named PBX or SIP server
  • Confirm transport, authentication and firewall rules on the target server
  • Confirm media ports and NAT behaviour for the site network
  • Verify DTMF, codec and door-release behaviour on the selected firmware
  • Record the acceptance tests for Asterisk, 3CX or another PBX

SIP Registration Example (sip.conf)

[d801-lobby]
type=friend
host=dynamic
secret=YourPassword
context=intercom
dtmfmode=rfc2833
nat=force_rport,comedia
qualify=yes
codec=ulaw,alaw,g722

NVR/VMS Connection Review — ONVIF & RTSP

The panel can be reviewed for an ONVIF or RTSP connection to a named NVR/VMS. Confirm the model, firmware, codec and event requirements, then test discovery, authentication, streams and relay behaviour during site acceptance.

Connection details to request (TD-D801)

Main Stream (1080p H.265)
rtsp://[device-ip]/stream0
Sub Stream (720p H.264 — mobile)
rtsp://[device-ip]/stream1
ONVIF Device URL
http://[device-ip]/onvif/device_service

NVR / VMS connection checklist

Named ONVIF NVR/VMS (verify target)
Required profile and codec
Main and sub-stream details
Credentials and authentication
Audio, event and relay scope
Device-level acceptance test
Connection scope: confirm motion, metadata, audio and door events with the target VMS; event mapping depends on firmware and target support.

Access-Control Interfaces — Wiegand & RS-485

The TD-D801 provides Wiegand and RS-485 outputs for third-party access-control panels. Check voltage, card format, bus addressing and relay behaviour against the existing controller before installation.

Wiegand Output Specifications

Format26-bit & 34-bit
Voltage level5V DC TTL
Max cable length150 m (26-bit) / 100 m (34-bit)
TriggerCard tap / PIN entry / Face ID
Panels for reviewnamed Wiegand access-control panels, subject to interface test

RS-485 Output & Elevator Control

  • RS-485 multi-drop bus — up to 32 devices on one bus
  • RS-485 connection route for BMS, subject to interface test
  • Elevator floor control: restrict resident access to their floor only (common in GCC/China MDU)
  • Connect to elevator controller relay boards via RS-485
  • Max RS-485 cable length: 1,200 meters (120Ω termination resistor recommended)
  • Baud rate: 9600 / 19200 / 38400 / 115200 bps (configurable)

Capacity Planning — Up to 9,999 Extensions in a SIP Server Design

Use these bands to scope the server, directory, entrance count and call-flow rules. They are planning ranges, not a single-device capacity guarantee.

Small
50–200 Units
  • 1× TD-D801 door panel (or per entrance)
  • Hosted SIP server (cloud or NAS)
  • Resident mobile app (iOS/Android)
  • 1 admin account for property manager
Medium
200–2,000 Units
  • Multiple TD-D801 panels (main + car park + side gates)
  • Dedicated SIP server
  • Floor-sub-controller for elevator relay
  • ONVIF NVR recording all panels
  • Property management portal
Large
2,000–9,999 Units
  • Matrix SIP dial plan across towers/blocks
  • High-availability SIP cluster (active/passive)
  • Elevator floor control per resident group
  • PSIM / BMS external-system connection review
  • External interface route for property ERP workflow

Regional Documentation

🇪🇺 Europe
CE RED · CE LVD · UKCA · RoHS 3 · WEEE · EN 50131 · GDPR (EU cloud option)
🇺🇸 United States
FCC Part 15 Class B · ANSI/BHMA Grade 2
🇸🇦 Saudi Arabia
SASO IEC 62368-1 · SASO IEC 60839-11 · CoC per shipment
🇦🇪 UAE
TRA Type Approval · CE · ISO 9001

Request a Model-Specific SIP 2.0 Quote

Send the model, quantity, entrance count and target PBX/NVR for an itemized quotation. Include OEM, private-label or ODM scope when it applies.

Submit RFQ WhatsApp
FAQ

SIP 2.0 — Technical & Commercial Questions

The TD-D801 can be reviewed for connection with Asterisk, 3CX or another PBX. Verify registration, transport, codecs, DTMF, authentication and door-release behaviour on the named server and firmware before approval.

The specification lists up to 9,999 apartment extensions in a SIP server design, with a unique SIP URI for each unit. This is not a single-panel limit; final capacity depends on the server, directory, entrance count and call-flow requirements.

The TD-D801 can be reviewed for an ONVIF connection with the named NVR or VMS. Confirm the model, firmware, stream, codec and event requirements, then test discovery, authentication, video, audio, events and relay behaviour.

The interface is specified as 26-bit and 34-bit Wiegand at 5V DC TTL. Stated cable limits are 150 m for 26-bit and 100 m for 34-bit. Confirm the controller electrical level, card format and cable route before installation; RS-485 is a separate interface for supported elevator-control designs.

Define the storage model, data region, retention period, controller/processor roles, DPA, resident notices or consent workflow and access logging. On-premise NVR and cloud designs have different responsibilities; record the selected model in the project documents.

IEEE 802.3af Class 3, up to 15.4 W, is specified over Cat5e or Cat6. Typical TD-D801 draw is approximately 8–10 W. Select the switch or injector by power budget, class and cable run, then verify the final values against the model datasheet.

Resident smartphone calling is possible when the selected SIP server and app support push delivery, live video and the approved door-release command. Confirm the app, network path and remote-release behaviour in the acceptance test; latency depends on the site and mobile networks.

SIP boundary

SIP signalling does not certify a lock-control path.

A smart-lock SIP system needs more than call signalling: identify the receiving endpoint, authorisation source and approved command interface. Smart-lock SIP connection is confirmed only for the named intercom, lock, firmware and control route. The same rule applies to video-intercom SIP connection in a multi-door project. A video-intercom SIP system still requires a topology, account plan and acceptance test for the named devices.