Yealink T85W (Router Phone) stuck on "No Service" — no registration attempts appear in Event Log despite confirmed network reachability

Smax

Trial User
Joined
Aug 29, 2026
Messages
1
Reaction score
0
Hi all, hoping someone can help spot what I'm missing. I've been troubleshooting this for a while and have ruled out everything I can think of.


Setup:


  • 3CX Hosted PRO
  • Extension 1004, Yealink T85W
  • Connection type: Router Phone ("Connect directly"), matching 3CX's documentation for cloud deployments

Symptom:


  • Phone permanently shows "No Service"
  • Voice & Chat admin page shows red/inactive status for this device
  • Event Log shows zero entries related to this device or extension, even after multiple manual triggers

What I've already tried:


  • Deleted/recreated the phone entry from scratch (initially had wrong connection type — "Local LAN/VPN" — corrected to Router Phone)
  • Full factory reset of the phone
  • Confirmed MAC address matches exactly in both places (no dashes/colons, per your docs)
  • Confirmed correct date/time on the phone
  • Tested reachability over both wired Ethernet and WiFi — phone gets a valid IP either way, and I can reach the phone's own web UI and my 3CX FQDN fine from the same network
  • Disabled a "DHCP VLAN" setting I found enabled on the phone
  • Manually entered the Auto Provision URL directly in the phone's web UI — phone reports "Operation completed" but still nothing in the Event Log
  • Manually filled in SIP account fields (Account → Register) with the Auth ID/password from the 3CX device page, port 5061/TLS — got "Register failed"
  • Checked if DHCP Option 66 might help — my router (carrier-provided) doesn't expose that setting
  • Confirmed this isn't a licensing/subscription issue — currently on PRO trial (not yet expired), other extensions and the SIP trunk are working fine

Question: Since the phone's own log shows successful local operations (like "Operation completed" after Auto Provision Now) but 3CX's Event Log shows nothing at all, is there a way to check server-side whether requests are even reaching the provisioning endpoint? Could this indicate an issue with the specific device/token entry rather than the phone or network?


Any pointers appreciated — happy to provide more detail.
 

Forum statistics

Threads
111,933
Messages
589,810
Members
164,808
Latest member
jsbjsb