After v20 upgrade, updates to Yealink T42S & T43U phones are not taking

[Thiek]

On-prem 3CX v18 Windows server, patched to the latest version before upgrading to v20, and after upgrading I installed the latest patches (Version 20.0 Update 4 (Build 487 Release)) but then noticed an issue with Yealink phones. They work, internal calls, external calls, but if I try to update the BLF keys, Ring Tone, Time Format, etc. it is not updating to the phone. I have tried rebooting the phones via admin console, even unplugging the patch cable and plugging back in (reboot), and finally did a factory reset which results in the phone not working at all. After a factory reset the phones sit with a blank keys the display says Warning – No Service. The only way to fix, that I know of, Reset the extension which then requires someone to unplug/reconnect the phone.

Prior to the upgrade, all phones were at the latest firmware, and the registration credentials for the phones were properly set to 10 characters and a combo of upper, lower, and numbers. Also, the admin password for the phones, they too are 10 characters, upper/lower and yet I’m not able to remote into the phones, login simply won't take which is very odd. I was thinking if nothing else, I could try rebooting after remote login to the phones... which is still a lot of work.

My question, am I doing something wrong, I’d like to prevent this going forward with upcoming v20 upgrades.

 

[SteveITS]

Were the phones using the FQDN or the LAN IP? They should be using the FQDN: https://www.3cx.com/docs/creating-fqdn-split-dns/

 

[JohnS_3CX]

1. Check the config URL in the extension IP phone tab, and compare it to the one stored currently in the phone.

2. Also as SteveITS said, you need to have split DNS for V20 (if using on-premises with local phones).

 

[UCSA]

were you using port 5001 on the V18 install. My upgrade to V20 defaulted back to normal 443 and as a result my phones worked but could not be provisioned/blf changed until factory reset and re joined back to 3CX on the new port.

I had assumed that the backup restore from 18-20 would have restored the port 5001 config but it didnt.

 

[SteveITS]

Yes good point, the port is set during the initial install/config. (Linux upgrades aren't a reinstall so keep the port)

 

[Thiek]

Thank you everyone for the quick responses. It appears at many of our sites, under Users > Phone Provisioning, the "Interface" selected is the IP address as to FQDN, I'll get those changed to FQDN for each ext. and reboot each phone before upgrading. I did check a few phones and their setting were reflecting ext@IP:registered but once I changed the interface and rebooted, it now shows ext@fdqn:registerd

I did notice at some of our 3CX installs the Provisioning Link (under Users>Phone Provisioning) shows the IP address whereas some sites show the FQDN. Not sure how to change that before upgrading to v18 or if it even matters. Does it??

As for the fqdn-split-dns, recall reading this prior to upgrade, went over it again and ran step 3, the test, and I got the IP address of the host I specified, so this checks. But as for UCSA's comment, port 5001 reverting to 443, where do you see this, where should I check?

 

[SteveITS]

It's been a while since I've worked in v18, but I think it used to have a dropdown for how to provision the phone? Or I may be misremembering that with the SBC choice dropdown since our clients are all hosted externally. If nothing else they could be deleted, reset, and re-added.

re: 3CX web port, When you connect in your browser you should see :5001 in the URL, or not if it's using the default web server port 443.

 

[Thiek]

Yes, all our URLs (each 3CX Installation) has 5001 in the URL and I noticed those links no longer work but do if 5001 is removed.

As for the provisioning link, it looks like this and I figured out how to change the provisioning link to reflect the FQDN. I tested this earlier and it did not work but now it is... hmm? If I change the "Select Interface" value to the FQDN and save, then come back into the extension, the link changes. I think I'm ready to restore (snapshot) back to v18 and test.

 

[SteveITS]

Be aware the license key may not be valid in v18 anymore after upgrading to v20.

If you're trying to change back to port 5001 you could also do a backup in v20, install while changing the port in the .xml file, and restore.

There have been a handful of other threads over the last year or so about changing ports...IIRC ideas included port forwarding :5000 to :80 and :5001 to :443, but that's harder if using a LAN IP and not an FQDN.

If it was just a matter of changing the interface for the phone I think it should work to set that and reprovision the phone...? As long as the phone can connect on the IP/port, of course, to pick up the change.

 

[Thiek]

Oh yes, well aware that the license will fail as I find that sort of crazy there's no way to fail back if needed. Hence why so much testing on a dev system. I'll restore to v18 which has the IP in each extension's link. I'll factory reset each phone to pick up those v18 settings. Then change to the interface value to FQDN, reboot the phones, and upgrade to v20 to see what happens.

 

[JohnWoodCC]

When i upgraded to v20, i forgot to change the HTTP from 80 to 5000 during the installation (I updated the HTTPS port to 5001). Because of that, I had several phones I could not update or provision until I went into the phone web interface and updated the provisioning URL to https and port 5001. Once I did that, I could update firmware and re-provision the phone within 3cx.

 

[Thiek]

On our development system I re-installed v20 and noticed the below which I originally missed. Glad SteveITS mentioned it, made a big difference second time around as 5001 was used on v18.