Support
Aiphone Door Station Is Not Calling the Monitor or App
Call Routing
Summary
Follow the four stages below to diagnose an Aiphone entrance button does not ring its intended indoor station or phone without losing evidence, configuration or device ownership.
Applies to
- Aiphone door/entrance stations
- Indoor monitor and mobile-app destinations
Difficulty and time
Difficulty: Advanced
Estimated time: 25 to 60 minutes
What you will need
- The exact model and current firmware or app version
- Administrator access where authorised
- A photo or screenshot of the current status
- One controlled test case and its exact time
What this guide covers
- Preserve and reproduce the fault
- Open the correct diagnostic screen
- Correct the proven cause
- Verify and document the result
Use this page when an Aiphone entrance button does not ring its intended indoor station or phone. It includes the menu or screen to look for, the status that matters and a repeatable proof test.
Exact labels can differ between recorder, controller, app and firmware versions. If the named screen is not present, do not guess at destructive options; note the model and current version for support.
Before you start
Protect the current system and record a baseline before changing anything.
- Write down the exact symptom: the visitor presses Call but no monitor/app rings, or the wrong tenant receives it.
- Photograph the current status, error text, wiring or timeline as applicable.
- Record the last known working time and anything changed immediately before the fault.
- Export or photograph station and tenant assignments before reprogramming.
Prove local call routing before rebuilding app registrations
Deleting tenants or stations can affect every resident. Correct one known destination first and test it.
If the required option is missing or the result does not match this guide, stop and identify the exact model before continuing.
What usually causes this
- Door station lacks power/network
- Call destination is wrong
- Tenant/app registration expired
- Phone background rules suppress ringing
Step 1: Preserve the current state and reproduce the fault
Begin with a repeatable baseline so you know whether a later change genuinely helped.
- Reproduce the problem once and record: the visitor presses Call but no monitor/app rings, or the wrong tenant receives it.
- Note whether every device or user is affected, or only one.
- Compare one working path with the failing path if a comparison exists.
- Export or photograph station and tenant assignments before reprogramming.
Step 2: Open the correct screen and inspect the evidence
The primary diagnostic location is Aiphone configuration/management > Station or Tenant Association > Call Destination, then app registration status. Do not change anything until the displayed state is recorded.
- Open Aiphone configuration/management > Station or Tenant Association > Call Destination, then app registration status. Menu wording can vary by model and firmware; use the nearest equivalent label.
- Confirm the door station powers and acknowledges the button press.
- Record the station/tenant identifiers and intended destination.
- Check whether the indoor monitor rings even if the phone does not.
Step 3: Correct only the cause you proved
Use the matching correction below. Make one change, save it, then repeat the same test.
- Correct station-to-tenant/resident call assignment.
- Restore network/2-wire bus connectivity and power before cloud/app work.
- Refresh an expired or incorrect mobile registration for the correct tenant.
- Correct phone notification/background permissions only after local call routing works.
Step 4: Verify, monitor and document the handover
A saved setting is not proof. Test the real outcome locally first, then test any app, cloud or client path separately.
- Call each programmed destination from the physical button.
- Confirm the correct monitor and intended phones ring.
- Answer, verify two-way audio and end the call normally.
- Test unlock under observation and check the event/call log.
Controlled support test
Situation: The reported symptom was: the visitor presses Call but no monitor/app rings, or the wrong tenant receives it.
Solution used: The current state was recorded in Aiphone configuration/management > Station or Tenant Association > Call Destination, then app registration status, one matching correction was made, and the same test was repeated.
Why this was chosen: This separated the proven cause from unrelated settings.
Installation notes: The final screenshot and test time were saved with the handover record.
Official reference used for this guide
Menu names differ between releases. Confirm model-specific behaviour in Aiphone Support Service Information before firmware, reset, storage or security-sensitive work.
Common mistakes
- Changing several settings before repeating the original test.
- Using a factory reset, initialise or format option as an early troubleshooting step.
- Treating an app symptom as proof that the local hardware or recording has failed.
- Failing to record the model, version, exact error and test time before escalation.
- Assuming similar-looking models use identical menus or features.
Troubleshooting table
| Symptom | What to check | What to do next |
|---|---|---|
| the visitor presses Call but no monitor/app rings, or the wrong tenant receives it | station offline, wrong tenant/destination mapping, expired app registration or phone notification suppression | Open the named diagnostic screen, record the displayed state and use the matching correction above. |
| The named menu is not visible | Different firmware, permissions or model capability | Do not substitute a destructive menu. Capture the model and version and use its official manual. |
| The change saves but the fault remains | The selected cause was not the root cause | Undo the change if appropriate, return to the baseline and compare the failing path with a working one. |
| Local test works but app or client test fails | Account, permission, cloud or remote-network path | Keep the proven local configuration and diagnose the remote path separately. |
| Problem returns later | Intermittent power, cable, storage, network or schedule condition | Record the new failure time and status; correlate it with logs, events and the last known working interval. |
When to contact support
Contact SecurityWholesalers support when the station registers the press but no correctly assigned local destination rings, or tenant mappings are inconsistent.
Send the order number if available, exact model, firmware or app version, screenshot of Aiphone configuration/management > Station or Tenant Association > Call Destination, then app registration status, the failure time, and the result of the local proof test.
Related support guides
- Aiphone Intercom Support Guides - Browse every guide in this support area.
- All Technical Support Guides - Return to the complete support library.
Related buying guides
- Intercom Buying Guide - Intercom planning guide.
Relevant product categories
- Aiphone Intercoms - Aiphone intercom products.
- Intercom Products - All 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
-
Where should I click first for Aiphone door station not calling?
Start at Aiphone configuration/management > Station or Tenant Association > Call Destination, then app registration status. Record the existing state before changing it because labels and available options can vary by model and firmware.
-
What should I look for on that screen?
Look for station online state, button/call destination, tenant identity, registered endpoints and call log result.
-
What must I avoid changing during the first check?
Deleting tenants or stations can affect every resident. Correct one known destination first and test it.
-
How do I prove the correction worked?
Each physical call button should ring only its assigned destinations and complete audio/unlock tests.
-
Why might my menu names look different?
Recorder, controller, camera, app and firmware releases can use different labels. Use the closest equivalent only when its function is clear; otherwise record the model and version for support.
-
Should I factory-reset the device?
Not as an early step. A reset may erase users, network settings, recording configuration, licences or cloud ownership. Back up the configuration and confirm the recovery plan first.
-
What should I send technical support?
Send the exact model and version, screenshot of Aiphone configuration/management > Station or Tenant Association > Call Destination, then app registration status, exact error text, failure time, what changed before the fault and the result of the controlled local test.
-
Can configuration changes recover data or events that were never recorded?
No. A correction can restore future operation, but it cannot recreate footage, alarm events or access transactions that were never stored.