There is no default upgrade path for an older apartment intercom. SIP can be appropriate where the building can support the required network architecture and call route. A 2-wire option can be appropriate where the existing cable route passes survey and retaining it reduces access work or resident disruption. The decision is only useful after the building, system boundary and handover responsibilities are defined.
Start With Existing Building Conditions
Survey every entrance, riser, indoor-unit location and comms-room position before selecting a system. Record cable type, route, visible condition, topology, distance, terminations, available power and any access restrictions. A cable described only as “existing 2-wire” is not enough evidence that it can be retained.
Compare Wiring, Network and Installation Requirements
Compare the two routes against the same installation scope. A SIP design normally requires a defined IP network, power and call-routing path. An existing-wiring route needs evidence that the retained bus, endpoints and power arrangement suit the selected configuration. Both routes still require mounting, lock release, resident-device replacement and acceptance testing.
For a comparison of video intercom systems, keep new cable work, switch or gateway equipment, access visits and reinstatement work in the quotation. The lowest hardware price does not describe the installed project cost.
Define Resident and Property Management Requirements
Define how a visitor call reaches each resident, who administers users, how a property team handles staff or service access and what must continue during an Internet or platform outage. Some buildings need indoor monitors as the primary answer route; others may need a documented mobile or PBX path. The selected workflow drives the hardware, network and support scope.
Use the multi-unit access control project brief to list entrances, user groups, credentials, lock-release responsibilities and handover evidence.
Confirm Interoperability at Model Level
SIP, ONVIF and other interface labels are not a project acceptance result. Name the exact intercom model, firmware, PBX, NVR or VMS, access controller and required actions. Then verify registration, video, audio, events and door-release behaviour in the proposed route.
For a shared entrance, review the TD-D801 technical page and request confirmation against the selected project configuration. For a residential retrofit kit, review the proposed wiring and optional interfaces before ordering.
Evaluate Supplier Support and OEM Flexibility
Supplier support should be defined as deliverables: model record, wiring material, configuration checklist, sample process, destination-market documentation and an escalation contact. For branded programmes, OEM/ODM manufacturing may include branding, language, accessories or regional configuration, subject to model capability and project scope.
Do not treat an unverified integration, certification, delivery schedule or custom software request as included because it appears in a generic product category. Put it in the written scope or mark it as pending validation.
Run a Pilot Test Before Full Deployment
Use a pilot at a representative entrance and apartment. Test call setup, image and audio quality, door release, resident administration, recovery after power or network interruption, commissioning time and the proposed handover record. A pilot is also where the project team should verify any retained cable route and the actual installation sequence.
- Named hardware and firmware recorded.
- Selected call and answer route completed.
- Lock release and fallback behaviour witnessed.
- Video, audio and events checked where required.
- Resident-unit replacement process timed at a real location.
- Open issues assigned before rollout.
Decision Path: Survey First, Then Choose the Route
The route is chosen by evidence from the survey, not by a product category. Work through the questions below for each riser; different risers in the same building can reach different answers.
| Cost and risk line | Existing-wiring (2-wire) route | SIP route |
|---|---|---|
| Main risk | Cable condition, topology and power at the farthest unit. | Network points, switch capability, addressing and call routing. |
| Main field work | Verify and terminate retained cable; replace endpoints. | Install network points, power and endpoints; configure the call route. |
| Resident disruption | Often lower where cable is retained, but only after it passes survey. | Depends on whether new cable or network work enters apartments. |
| Who must be named | Commissioning owner and cable verifier. | Network owner, PBX or platform administrator. |
| Evidence to request | Survey record, wiring diagram, sample result. | Registration, video, event and release test on the named configuration. |
Neither column is a ranking. See SIP vs analog video intercom for the architecture comparison, PoE vs Wi-Fi for MDU for the power and signal trade-off, and Video Intercom Total Cost of Ownership for pricing the comparison.
Frequently asked questions
Is SIP or 2-wire better for an MDU retrofit?
Neither is the default. SIP suits buildings that can support the network architecture and call route; a 2-wire route suits buildings where the existing cable passes survey and retaining it reduces access work. The survey decides.
Can existing 2-wire cable always be retained?
No. “Existing 2-wire” is not evidence of reuse. Record cable type, route, condition, topology, distance, terminations and available power, and verify the route with a sample test.
What project inputs should be collected first?
Unit count, entrance count, resident access windows, existing door-release wiring, available network points and the party responsible for commissioning.
Does SIP or ONVIF support mean it will work with my PBX or VMS?
Not by itself. Name the exact intercom model, firmware, PBX, NVR or VMS and the required actions, then verify registration, video, audio, events and door release on the proposed route.
What should a pilot test?
Call setup, image and audio quality, door release, resident administration, recovery after power or network interruption, commissioning time and the handover record, at a representative entrance and apartment.
Can OEM or custom features be assumed to be included?
No. Branding, language, accessories, integrations and custom software depend on model capability and project scope. Put them in the written scope or mark them pending validation.
Plan the Retrofit Scope Before Ordering
Planning a multi-unit retrofit project? Share your building type, existing wiring, unit count and required functions to receive a suitable product recommendation.
Request a Project Recommendation