- Joined
- Apr 24, 2018
- Messages
- 3
- Reaction score
- 0
Hello everybody,
I have already read a few existing posts on this topic, but nothing really worked.
First, I have to say that the maintenance of my 3CX has expired. It is also interesting that I suddenly get a SSL error with the 3CX-FQDN of my 3CX system. By entering the IP address and the port 5001 in the browser, I come on it but with a warning...
It works so far, however, the YeaLink phone is no longer able to download the external phonebook from 3CX. There is always the message External phonebook can not be downloaded. If I enter the URL XML in the browser with the FQDN link, I will not get an XML file. Probably because of the SSL error! However, if I enter the Provisionierungslink with the IP address instead of the FQDN it goes in the browser, with a SSL warning, but it shows me the contacts. But the YeaLink phone does not manage with either IP or FQDN. SNOM M300/M25 there it works with the Phonebook
Could the problem of the telephone book lie with the faulty 3CX-SSL FQDN? As a next step, I would try to extend the maintenance.
Any Ideas ?
Best Regards
I have already read a few existing posts on this topic, but nothing really worked.
First, I have to say that the maintenance of my 3CX has expired. It is also interesting that I suddenly get a SSL error with the 3CX-FQDN of my 3CX system. By entering the IP address and the port 5001 in the browser, I come on it but with a warning...
It works so far, however, the YeaLink phone is no longer able to download the external phonebook from 3CX. There is always the message External phonebook can not be downloaded. If I enter the URL XML in the browser with the FQDN link, I will not get an XML file. Probably because of the SSL error! However, if I enter the Provisionierungslink with the IP address instead of the FQDN it goes in the browser, with a SSL warning, but it shows me the contacts. But the YeaLink phone does not manage with either IP or FQDN. SNOM M300/M25 there it works with the Phonebook
Could the problem of the telephone book lie with the faulty 3CX-SSL FQDN? As a next step, I would try to extend the maintenance.
Any Ideas ?
Best Regards