FYI: 3CX - SSL - Namecheap\Comodo - Yealink

[Mike Hammett]

When setting up the cheapest ($8/year) Namecheap SSL certificate, DO NOT just upload the certificate file as presented to you by Comodo. Open up the crt file and append the ca bundle to the end of the file.

The 3CX web interface will work in your web browser, but it will not work in a Yealink phone.

I remember there's a problem with certificates when building a new PBX, but I never remember what it is until I'm trying to troubleshoot problems later during provisioning. Hopefully: A) I remember this on my own, B) I find this post when I go looking next time, or C) I can help someone else with this problem.

 

[Saqqara]

The reason it does not work with yealink phones, as the phones does not recognise the ca root certificate

if you want it work, you have to disable ‘Only Accept Trusted Certificates" via the phone web frontend

 

[Mike Hammett]

That is not necessary if you do as I described in my original post.

My original post was a how to, not a request for help.

 

[AWS2P]

IMO the simplest way is to use LE cert natively included with 3CX, nothing to pay more and have no headaches to be set as it is automated.

 

[Mike Hammett]

IMO the simplest way is to use LE cert natively included with 3CX, nothing to pay more and have no headaches to be set as it is automated.

I love Let's Encrypt elsewhere, but until 3CX supports LE with custom FQDNs, that's a non-starter.

Also, let's keep the thread on-topic.

 

[ConvergiaDaniel]

I had opened a ticket with Yealink support and supposedly they will be adding support for Sectigo CA (owner of Comodo CA) in their list of trusted root CAs in Q1 2020. I'm disappointed that it's taken them about a year to consider supporting them again (Comodo was rebranded as Sectigo in November 2018), but I hope they actually deliver it.