SSL Certificate for Web Client/"tel:" vs "http" links

[Thom Hill]

I'm developing a simple CRM for a client in MS Access (please don't suggest SQL Server/Web App/etc). Client wants to click link to call customer when on forms. I tried "tel:" link and it worked fine once, then afterwards the link didn't work if user abandoned call when dialler popped up. 3CX continued running as process so subsequent clicks failed. Clicks didn't work even after killing the process with Task Manager.

So I tried to create a http(s) hyperlink that called the Windows client. This worked but because of the SSL certificate I get the usual security warning about incompatible certificate. I can eventually get to the Browser dialler (Edge since MS Office doesn't recognize default browser) but this is a crappy UX. (see pdf)

Any ideas?

 

[Saqqara]

You need to use the FQDN of the server and not the IP address, to resolve the ssl certificate error.

When you installed 3CX, did you choose spilt dns installation ?

Also look at 3CX Client API if you have Pro or Ent license - https://www.3cx.com/call-center/crm-integration/

 

[Saqqara]

check out Call Trigger CMD plugin https://www.3cx.com/call-center/crm-integration/

 

[Thom Hill]

I didn't install 3CX so not sure how it was set up. Will research the FQDN (whatever that is) and get whomever to resolve it. I'm a humble programmer not a server guru but can generally work through technical stuff. I appreciate all your guidance.

 

[Saqqara]

To check FQDN, within Information tab (top right) within the 3CX management screen you will see fqdn. This will be the correct fqdn to access the server. You will have to setup spilt dns on your dhcp server to point to fqdn to the internal ip address of the server - https://www.3cx.com/docs/creating-fqdn-split-dns/

If you can access the server by the fqdn instead of ip using https without any errors you are ready to go.

Edit each extension, under 'phone provisioning' tab select 3cx client and change the Network interface for registration and provisioning to the fqdn, save settings and resend the welcome email.

Within the welcome email, you will see url now contains the fqdn web address and not ip address