Sangoma Connect Invalid Certificate

[Russix]

When provisioning the Sangoma Connect mobile app I get prompted with an error stating “Invalid Certificate, The certificate for domain xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.connect.sangoma.com is not valid or has expired.” ABORT or TRUST.

Any suggestions?

[xrobau (Rob Thomas)]

You’ll need to post the actual UUID of the certificate. I had a quick browse through the CT of that domain and nothing jumped out as obviously expired.

https://transparencyreport.google.com/https/certificates?cert_search_auth=&cert_search_cert=p:Y29ubmVjdC5zYW5nb21hLmNvbTp0cnVlOnRydWU6OkNCUVFBUT09&cert_search=include_subdomains:true;domain:connect.sangoma.com&lu=cert_search_cert

[lgaetz (Lorne Gaetz)]

Open a support ticket please. https://wiki.freepbx.org/display/CONNECT/Sangoma+Connect+Feedback

[lgaetz (Lorne Gaetz)]

Hi @Russix

Did you open a support ticket? I think what you’re running into is that the extension you’re trying to register to has the transport set to TLS and is not allowing TCP registrations. TLS is not specifically supported at this time, but it may be possible with Support’s assistance to get TLS signaling working for you. Otherwise, you can set the extension transport to ‘auto’, reprovision the soft client and the registration should succeed.

[Russix]

Setting the transport to auto has fixed the issue. Thank you for your help.