What should I check first with IP or 2-wire intercom setup problems?

Start by deciding which system type you actually have and then prove the local call path before touching cloud or app settings. IP and 2-wire faults often look similar but start in different places.

What usually goes wrong on IP versus 2-wire intercom jobs?

IP intercom faults usually start around network path, PoE, addressing, or device assignment. Two-wire faults usually start around cabling condition, distributor path, polarity where relevant, distance, power distribution, or monitor and door-station assignment.

When should I contact support?

After you have confirmed the model, the symptom and the basic local checks and still cannot resolve the issue.

Should I test locally before changing more settings?

Yes. A local test usually tells you more than an app symptom alone.

What should I send support if I am still stuck?

The order number if available, the product model, screenshots or photos of the current status, and a short note describing what you already tested.

Support

IP Intercom vs 2-Wire Intercom Setup Problems

IP and 2-wire intercom problems often look similar from the customer's side, but they usually fail for different reasons. The safest path is to identify the architecture first and then test it in the right order.

Technical Support Guide

Summary

Use this guide when an intercom system is installed but the monitor, door station, app, or unlock path is still not behaving properly.

Applies to

IP intercom systems
2-wire retrofit intercom systems
Mixed jobs where installers are unsure whether the fault is network, cabling, or configuration

Difficulty and time

Difficulty: Moderate

Estimated time: 15 to 40 minutes

What you will need

Model details
Access to the door station and monitor locally
Access to the switch or 2-wire distributor
One clear call test
Photos of the cabling path if the layout is unclear

What this guide covers

Identify whether the system is IP or 2-wire
Check the matching cabling and power path
Confirm monitor and door-station assignment
Test app and unlock only after local calls work

This guide is written for customers, installers and site managers who need a practical order of checks rather than guesswork.

The quickest way to waste time here is to start on the mobile app before the local monitor and door station are even proven to belong together properly.

Before you start

Write down the current behaviour before making changes. A clean baseline makes support much easier.

Note the exact brand and model of the door station, monitor, and any 2-wire switch or distributor.
Take photos of the cabling and power path if the layout is messy.
Know whether the local monitor currently rings or not.
Test one known door-station call at a time.

Important

Do not guess your way through support changes

Change one thing at a time and test it properly before moving on.

Collect the model details and a clear symptom description if support needs to step in.

What usually causes this

On IP systems: wrong switch port, no PoE, wrong VLAN or subnet, bad patch lead, or devices never assigned to the same site or residence correctly.
On 2-wire systems: cable joins, old cable condition, incorrect distributor path, power drop, excessive run length, or the monitor and door station not matched correctly.
On both: the installer moved to app setup before proving the local door-station-to-monitor path.

Step 1: Identify the architecture and prove the local call path

Before changing settings, make sure you know what kind of system you are actually testing.

If each device runs back to a PoE switch, treat it as IP.
If it relies on existing 2-wire cable and a 2-wire distribution path, treat it as a 2-wire job.
Press the door station and confirm whether the monitor rings locally.
If the local call path is not working, do not jump ahead into app or unlock testing.

Simple comparison diagram

IP path:
Door Station -> PoE Switch -> Router
Indoor Monitor -> PoE Switch -> Router

2-wire path:
Door Station -> 2-wire distributor/switch -> indoor monitor(s)
                                   
                                    -> uplink/router path if app calling is used

Step 2: Check the cabling and power path that matches the system type

IP and 2-wire faults usually start in different physical places.

On IP systems, check PoE switch power, patch leads, uplink to the router, and whether devices appear on the network.
On 2-wire systems, check the distribution module, cable joins, power path, and any polarity requirements for that system.
If the run is long or the cabling is old, do not assume the path is clean just because a device powers up once.
Take photos if the topology is unclear and support may need to help.

Step 3: Check monitor, room, residence, and door-station assignment

Even with correct cabling, the system still fails if the logical assignment is wrong.

Confirm the door station and monitor belong to the same home, room, or residence path.
On multi-monitor systems, confirm which monitor is the master and which are extensions.
On multi-door systems, confirm each entrance is calling the intended monitor group.
If the app is involved, do not test it until the local monitor routing is proven.

Step 4: Test the app and unlock path separately after local calls work

App calling and door release should be tested as separate layers, not assumed together.

Once local calls work, test app calling on mobile data.
Then test strike, maglock, or gate release separately.
If door release fails, check relay type, separate lock power, and NO or NC wiring logic.
If it still fails, collect photos of the device assignment and cabling path for support.

Worked example

2-wire monitor powers up but never rings

Situation: An older apartment retrofit had a powered monitor and powered door station, but the monitor never rang.

Solution used: The distributor path and residence assignment were checked first. The real issue was not the app or internet. The door station and monitor were not assigned to the same logical unit correctly.

Why this was chosen: The local call path has to work before the cloud path matters.

Installation notes: Once local calls worked, app calling and unlock testing became straightforward.

Common mistakes

Treating a 2-wire retrofit like a normal IP network job.
Testing app calling before the local monitor path works.
Assuming powered devices are also configured correctly.
Mixing up master and extension monitors.

Troubleshooting table

Symptom	What to check	What to do next
Door station powers up but monitor never rings	Room or residence assignment, cabling path, local call routing	Prove the local call path before touching app settings.
IP system devices come online but still do not call correctly	Master or extension logic, door-station assignment, LAN path	Check the logical device assignment, not only the switch link lights.
2-wire system is intermittent	Old cable quality, joins, distance, distribution path	Check the physical 2-wire path carefully and photograph the topology if needed.
Unsure whether support is needed	Not enough evidence collected yet	Take screenshots, model details and one clear symptom description before escalating.

When to contact support

Contact SecurityWholesalers support when you have the model details, one clear symptom description, and the basic local and settings checks have already been completed without solving the issue.

Related support guides

Tech Support Guides - Browse the wider support section.
Intercom Support Guides - Return to the relevant support sub-hub.

Related buying guides

Intercom Buying Guide - Intercom planning guide.
Access Control Buying Guide - Door hardware and egress planning guide.

Relevant product categories

Intercom Products - Intercom categories.

Still stuck?

Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.

Frequently asked questions

What should I check first with IP or 2-wire intercom setup problems?
Start by deciding which system type you actually have and then prove the local call path before touching cloud or app settings. IP and 2-wire faults often start in different places.
What usually goes wrong on IP versus 2-wire intercom jobs?
IP intercom faults usually start around network path, PoE, addressing, or device assignment. Two-wire faults usually start around cabling condition, distributor path, distance, power distribution, or monitor and door-station assignment.
When should I contact support?
After you have confirmed the model, the symptom and the basic local checks and still cannot resolve the issue.
Should I test locally before changing more settings?
Yes. A local test usually tells you more than an app symptom alone.
What should I send support if I am still stuck?
The order number if available, the product model, screenshots or photos of the current status, and a short note describing what you already tested.