Upgraded Systems Unable To Reach Phone Book

[MarkCSUK]

Hi,

On Friday (11/10/2024) we upgraded two on-site systems from v18 to v20 (Version 20.0 Update 3 (Build 806 Release)). Both upgrades went smoothly and without issue.

This morning users of both systems are reporting the same issue. namely that they are unable to access the 3CX phonebook (contacts) on their desk phones (they dont use device or web clients).

System 1 is using Yealink T41S phones
System 2 is using Yealink T46U phones

I have confirmed all 3CX services are running, the phones are registered and provisioned correctly, all other functions are working.

I have upgraded the phones to the latest 3CX recommended/compatible firmwares.

I have turned off the SECURITY>TRUSTED CERTIFICATES>Only Accept Trusted Certificates on handsets on both systems, however this has not helped.

I'd be grateful for any other thoughts or insights.

Mark.

 

[MarkCSUK]

Ok change the "Network Interface" drop down for each phone and pick the FQDN.
If its empty it means that whatever interface they had in V18 no longer exists.
Since you have split DNS it should not be a problem to pick the FQDN.
Click save to apply the setting.

You will need to use the same link in the phone so that it can reconnect back to its provisioning server.

I have tried setting the NETWORK INTERFACE under USER > IPHONE to the IP and the FQDN the AP link just stays as the server IP. I'm not sure if that should change or if I can just the FQDN as the AP path anyway.

 

[JohnS_3CX]

I have tried setting the NETWORK INTERFACE under USER > IPHONE to the IP and the FQDN the AP link just stays as the server IP. I'm not sure if that should change or if I can just the FQDN as the AP path anyway.

You have to save and then re-open the extension to see the updated link.

 

[MarkCSUK]

You only need 1 to test the theory.

Yeah, it'll just be a lot easier on my log'oles to wait until 5 and then fully disconnect someone and reconnect them.

 

[MarkCSUK]

You have to save and then re-open the extension to see the updated link.

Sorry - yes - was clicking without saving

OK some users have emailed me and said its all working for them - now I need to work out what I did XD

anyway thank you everyone for your input - I'm going to let sleeping fixed issues lie

 

[Alphabetic]

audit log

 

[MarkCSUK]

for the benefit of anyone from the future looking at this to find the fix - whilst the AP URL looked the same in both places, I copied and pasted the URL from the 3CX server to the phone, saved it and AP'd the phone and that seems to have been the magic.