The pilot phone won’t register
Observed symptoms
An extension dialled from the 3CX app did not ring the desk phone. Before the reset, the desk phone made an outbound call with clear two-way audio. Which phone system carried that call was unconfirmed. After a factory reset and a vendor-guided provisioning retry, the handset displayed “Registration failed.”
Environment and evidence
The handset MAC address was confirmed. The handset and the 3CX Session Border Controller (SBC) were on different subnets. Reachability between them was untested. The original incident was still unresolved at the last confirmed check.
Suggested diagnostic checks
- Match the handset MAC address and assigned extension to the device entry in 3CX.
- Compare the handset IP, gateway and VLAN with the approved pilot design. Verify reachability to the intended SBC using an approved test on the handset segment.
- Confirm the SBC is connected and review provisioning and registration logs. Record evidence that supports or rules out each hypothesis.
Diagnostic notebook
Reveal the simulated resolution
In the simulation, the handset is connected to the approved network, reaches the intended SBC, and registers successfully after provisioning. The original ticket remained unresolved. Different subnets alone can be valid when routing and policy permit the required traffic.
Verification tests
- Confirm the phone shows as registered to the expected extension in the new 3CX system.
- Call the desk phone from the 3CX app and call back from the desk phone. Confirm ringing, answer and clear two-way audio for both calls.
- Check the new system’s call records to confirm both calls went through it.
