Support
Aiphone Mobile App Registration and Call Setup
Mobile App Setup
Summary
Follow the four stages below to diagnose an Aiphone mobile app must be registered to receive intercom calls without losing evidence, configuration or device ownership.
Applies to
- Supported Aiphone mobile-app systems
- Resident and commercial tenant registration
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 mobile app must be registered to receive intercom calls. 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 app is unregistered, the site is missing or door calls do not reach the phone.
- Photograph the current status, error text, wiring or timeline as applicable.
- Record the last known working time and anything changed immediately before the fault.
- Record the existing tenant/device assignment before deleting registrations.
Use the app documented for the exact Aiphone series
Aiphone app support and registration workflows vary by system. Do not substitute an older app or expose registration QR codes publicly.
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
- Wrong Aiphone app is installed
- Invitation/QR expired
- Tenant is not assigned to entrance
- Phone suppresses calls/notifications
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 app is unregistered, the site is missing or door calls do not reach the phone.
- Note whether every device or user is affected, or only one.
- Compare one working path with the failing path if a comparison exists.
- Record the existing tenant/device assignment before deleting registrations.
Step 2: Open the correct screen and inspect the evidence
The primary diagnostic location is Aiphone system management/tenant portal > Mobile App Registration, then supported Aiphone app > Scan/Register. Do not change anything until the displayed state is recorded.
- Open Aiphone system management/tenant portal > Mobile App Registration, then supported Aiphone app > Scan/Register. Menu wording can vary by model and firmware; use the nearest equivalent label.
- Confirm the exact Aiphone series and currently supported app for the phone OS.
- Confirm the resident/tenant and entrance station are assigned correctly.
- Check network/internet status and whether an invitation/QR has expired.
Step 3: Correct only the cause you proved
Use the matching correction below. Make one change, save it, then repeat the same test.
- Create or confirm the tenant/resident in the authorised management workflow.
- Generate a fresh supported registration invitation/QR and complete it on the intended phone.
- Allow notifications, microphone, local network and background activity as requested.
- Assign only intended entrances/unlock permissions and remove obsolete phones.
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.
- Place a real call from the assigned entrance.
- Answer with the phone locked and verify two-way audio.
- Test unlock only under safe observation.
- Switch between Wi-Fi and mobile data and confirm the intended remote behaviour.
Controlled support test
Situation: The reported symptom was: the app is unregistered, the site is missing or door calls do not reach the phone.
Solution used: The current state was recorded in Aiphone system management/tenant portal > Mobile App Registration, then supported Aiphone app > Scan/Register, 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 Mobile App Registration Guide 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 app is unregistered, the site is missing or door calls do not reach the phone | wrong app/series, expired registration, tenant not assigned, phone permissions or network path | 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 correct current app is registered to the correct tenant but a proven entrance call does not reach it.
Send the order number if available, exact model, firmware or app version, screenshot of Aiphone system management/tenant portal > Mobile App Registration, then supported Aiphone app > Scan/Register, 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 app setup?
Start at Aiphone system management/tenant portal > Mobile App Registration, then supported Aiphone app > Scan/Register. 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 supported app/OS, tenant assignment, registration state, entrance permissions and invitation validity.
-
What must I avoid changing during the first check?
Aiphone app support and registration workflows vary by system. Do not substitute an older app or expose registration QR codes publicly.
-
How do I prove the correction worked?
A real entrance call should ring the locked phone, support two-way audio and permit only the intended unlock action.
-
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 system management/tenant portal > Mobile App Registration, then supported Aiphone app > Scan/Register, 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.