Solved Provisioning Link in Version 20

[forrestdean]

Is there some reason we have to use the IP address of the PBX instead of the URL in the provisioning link now? I always used the URL address in the provisioning link in version 18, but now in version 20 when I do a factory reset on the Yealink T48s phones they do not connect to the network unless the provisioning link is using an IP address.

 

[Alphabetic]

Is there some reason we have to use the IP address of the PBX instead of the URL in the provisioning link now? I always used the URL address in the provisioning link in version 18, but now in version 20 when I do a factory reset on the Yealink T48s phones they do not connect to the network unless the provisioning link is using an IP address.

Other way around, you have to use the FQDN instead of the IP now.

If your PBX is on the same LAN as your phones then you will need to configure split DNS.

 

[forrestdean]

Unfortunately, it won't let me use FQDN. The phones will only work if the provisioning link is using an IP address. Our PBX is on the same LAN as our phones and I am already using split DNS.

 

[Alphabetic]

What are the phones? Old yealinks? You'll have to turn off "only accept trusted certificates" on the security tab.

 

[forrestdean]

I'm using Yealink T48S. I checked the security tab and the "only accept trusted certificates" is turned on. I turned the option off and the phones will connect now, but now the phone book does not show up. The phone book is empty, and whenever I try to update the phone book I get an error message saying "Cannot download remote phonebook!"

 

[Alphabetic]

Are your phones on the latest 3CX supported firmware and are you running default templates?

 

[forrestdean]

We are currently upgrading the firmware now as most of them are out of date, and we were using custom templates but we are going to move them back to default templates. I'm going to start with my phone first to see if that works, and then I'll update what happens. Thank you for your help so far.

 

[forrestdean]

I've switched my phone back to default template, and I am using the latest firmware version of 66.86.0.15, and unfortunately, I still cannot access the remote phonebook. I can only access the phonebook if I go back to using the IP address in the provisioning link.

 

[AWS2P]

So this means your FQDN is not properly resolved by your split dns
What do you get when you send a nslookup +FQDN on the LAN, is it the LAN IP from the PBX ?
if you do the same nslookup + FQDN + 8.8.8.8 do you get the public IP of your router's location?

 

[forrestdean]

Ok, I finally got it to work. I went back to the Security tab again and didn't notice from the first time that there is a "Phone CA" tab. I only disabled the "Only Accept Trusted Certificates" option under the "Custom CA" tab. I went back and now have the option disabled in both tabs and now the phonebook will open up on the Yealink phone.

Thank you very much for your help with this. I would not have figured that part out, at least not for a very long time, lol.

Thanks again,

Forrest Dean