UI phone list completely empty - no registration after v18

[techguy1]

Hi folks, reaching out for some help to get me past this issue.

System Setup (Currently Running - Restored)

• 3CX Version, Standard Annual 16.0.6.641
• Server OS, Windows Server 2012 R2
• Is the 3CX Server Hosted and where? On-premises
• IP Phone Make/Model/Firmware version, Yealink T22P / 7.73.0.40 (some 7.73.0.50), Yealink T28P / 2.73.0.40
• Provisioning Method: Local
• Trunk Provider or VoIP Gateway Make/Model, Flowroute SIP trunks
• Has the Firewall Checker passed: Yes
• Are custom Phone Templates being used: Yes, although the changes are very basic

Attempted Upgrade:

• 3CX Version, Standard Annual 18.x (whatever version the download was)
• Server OS, Windows Server 2016
• Is the 3CX Server Hosted and where? On-premises

Given the EOL on v16 in November, I was going through the process to upgrade to v18. I ran an in-place upgrade to Server 2016 first. v16 seemed to work fine after that. I then did a backup and installed the latest v18 and restored the backup from v16. After doing that, none of the phones connected to the system. The extensions all showed red dot, and the phones list was empty. The system seemed to work fine at a system level. Inbound calls could be placed, and I received office voicemail greeting immediately, but none of the phones themselves registered. I understand that the phone models I have are not supported anymore and cannot be auto-provisioned, but I thought they would stay provisioned, and I would just have to deal with the manual provisioning if I needed to make some sort of changes?

I got a little panicked because it was getting really late, so I attempted to re-install v16 with an EXE I had from before. I could not connect to the activation server to run the install. I found some posts about the URL changing, but even with changing the hosts file it did not fully complete. It looks like I missed installing a patch prior to February that updated the activation URL on v16. I downloaded the 3CXPhoneSystem16.exe last night that was on the site via direct URL, but I'm not sure what build that was if it was the U8A or not..., but it didn't work either. I ended up restoring the entire VM from a backup I took before getting started. Everything came back up fine.

So basically my question is how can I get these phones to work on v18 when I re-attempt the upgrade? I've read this article https://www.3cx.com/sip-phones/yealink-t20p-t22p-t26p-t28p/ but I'm not sure how I can apply that to the issue I'm having.

Thanks for the help!

 

[CentrexJ]

Since your IP address of Windows likely didn't change the phones should automatically reconnect to your system. Perhaps they got blacklisted? Also make sure the windows firewall didn't turn on.

 

[techguy1]

Correct, the IP was the same. Windows firewall is on, but it had the same rules as were set before. I did not check black list at the time…

I as well thought they should have reconnected, but they didn’t. Is there anything forcing the passwords to be certain length in v18? I did see that warning, but I also have that warning in v16, so I didn’t think that was the issue.