Company Phonebook no longer working on Yealink T4x models after upgrade to v20

[PD-SII]

It appears that our local LAN phones are no longer pulling the phonebook when we have https://dnsname as the provisioning URL. If we change the network interface option off the DNS name to the local LAN IP, provisioning URL changes to http://ipaddress and the phonebook begins to work fine. Is there still a way to mass change the network interface on multiple phones (as in a few hundred) without having to touch each phone individually within v20? We had this option in v18, but I can't seem to find it in v20 .. thanks everyone

 

[bitn2]

Did you configure split dns correctly?

 

[PD-SII]

Yes .. phones provision fine inside and outside with the https://dnsname URL. The phonebook is the only issue. Appears it requires http. I was going to try http://dnsname .. but that doesn't appear to be an option. We did try changing Option 66 at one of our sites to the http://dnsname URL and they do provision back fine, but within 3CX it will still show the dnsname as the interface with a https provisioning URL. I haven't tried using http://ipaddress as the provisioning address to see if that makes a difference .. but I honestly don't really want to do that even if it does work..

 

[bitn2]

You didnt answer my question, did you configured split dns correctly.

 

[PD-SII]

Sorry I thought I did answer it .. let me try re-phrasing. The FQDN (which I was referring to as the dns name .. I'll use FQDN in the future) resolves using nslookup to the local LAN IP of the 3CX server. Performing the same nslookup externally resolves to the static public IP. Basically the FQDN resolves correctly both internally as well as externally.

 

[bitn2]

Ok, that's fine. Did you tried to reach the phone book xml in a browser? This should open.

 

[PD-SII]

Yes .. and that's where things get a bit odd

https://fqdn:5001/provisioning/xyz/yealink_phonebook.xml pulls the phonebook correctly in my browser

http://ipaddress:5000/provisioning/xyz/yealink_phonebook.xml pulls the phonebook correctly in my browser

http://fqdn:5000/provisioning/xyz/yealink_phonebook.xml will re-direct to https://fqdn:5000/provisioning/xyz/yealink_phonebook.xml and will not work (I wouldn't expect it to though with https and port 5000)

I feel like I'm missing something simple..

 

[bitn2]

The provision URL must be https. The phone book should work than. If not, check the logs on the phone directly.

 

[PD-SII]

Https is what we are using with the exception of a couple phones I changed manually to http. I will admit I'm a little baffled on this one. Doesn't make sense to me why they would suddenly stop working after the move to v20. Looks like we will need to spend a little time doing wireshark captures and analyzing logs for more information. I'm still thinking there has to be something simple I'm missing..

Back to my original question in my first post though .. is there still a way to change the interface on multiple phones like the option that was in v18? This would be a temporary solution I could use while we investigate. Once we discover and fix the issue, I can then use the same method to change them all back. This would at least allow the users to access the phonebook like before while waiting on me to come up with a permanent resolution

 

[PD-SII]

Is anyone aware of whether it is still possible to the change the interface on multiple phones like the option that was in v18? I'd really like to do this as a temporary solution till I can dedicate the time necessary to troubleshoot further .. thanks everyone

 

[UCSA]

We have the same issue with V20

 

[PD-SII]

I thought we might not be alone, but I was hoping the option in v18 was still available somewhere in the software. Looks like we will just have to touch each phone one by one for the time being till I can dedicate the time necessary to troubleshoot further. I got used to being spoiled with v18