Solved Click to Call in V18

Status
Not open for further replies.

David Schumann

Silver Partner
Joined
Mar 27, 2019
Messages
50
Reaction score
7
Hello,
We are still on V16 with most our customers due to the changes in the web interface which have made it quite a bit less pleasant to use. It is our hope that this will be improved in future releases.
Whilst changes in the User interface can be unpleasant, lacking functionality and complicated workflows to do basic processes is something that our customers are not willing to accept. Therefore, one of the problems which I would like to solve asap is the functionality of click to call from a web browser. The web browser most of our customers use is Google Chrome.
It seems the 3CX Click2Call Chrome extension is still necessary in order to have click to call functionality. I have it installed and configured as seen in the screenshot below.

1639049276389.png

The problem which we are having is that ever since the update to 3CX v18, Chrome has started opening the following popup whenever a tel link is clicked. I want to be able to set a default device which is used whenever a tel link is clicked. This dialogue also appears if there is only one option.
The default app to be used for a tel link or a callto link are set to the new 3CX app in windows. This message seems to be Chromes doing.

1639049664628.jpeg

I have found the following solution to the problem. This didn't work for me though. None of the options stated in the solution were visible on any of the devices I checked.
https://support.google.com/chrome/t...-a-call-from-popup-when-clicking-on-tel?hl=en

I apreciate any help.

Kind regards,
David Schumann
 
Hi @David Schumann,

This isn't a 3CX specific issue. This is a Chrome specific issue. I've searched several forums and many users have encountered this when using a whole range of clients that assimilate the tel link information. None seem to offer a solution short of editing registry data. I encourage you to give it a google.
 
I don't understand 3CX not working with Google for changes like this. I have 75 people, 50 of which use that extension and it isn't working. Even the desktop app seems to be affected by the update to v18. It is a nightmare that frankly has cost us money. Who has time to do another's company's job in reaching out to Google? This is a complete loss of time and money. We are using this system because we thought it would be better but things like this should have been handled a little better. It should have been tested across the board on browsers and Google should have been part of the process considering the number of users that would be using it. Telling us to reach out to Google is like saying, call the president. The 3cx team should be reaching out to Google and asking what's what. I believe that would be more effective.
 
  • Like
Reactions: kaivonderchromit
Hi @lynnie820,

I never mentioned that anyone should reach out to Google on our behalf. I mentioned that if you run a google search you'll find similar threads non-specific to 3CX. If you run that search you'll find forum threads which mention a possible registry hack that may make it work, but I can't suggest that as it's a registry hack. I've provided the information as best I could, will close this thread now as there is nothing 3CX can do about this but wait for Google to implement changes already suggested to them (in the forums I mentioned above).
 
To stop the popup, the first issue is to go to:
chrome://flags/#click-to-call-ui

and disable "Enable click to call feature signals to be handled on desktop"

This will then change the prompt that opens when you click a number.

To stop this second popup from occurring, you need to re-establish the "Always open" checkbox in the external protocol dialog box.

This can be done via group policy for chrome or via regedit - more details here:
https://admx.help/?Category=Chrome&...:ExternalProtocolDialogShowAlwaysOpenCheckbox

If you still don't see see the always open checkbox, you are probably linking from an unsecure website.
Go to chrome://flags/
and register the site as "Insecure origins treated as secure"

I hope this helps
 
  • Like
Reactions: VasilisV_3CX
Thanks for the update @eagle37!

Please note however, that the flag chrome://flags/#click-to-call-ui no longer exists. This means we're back to square one, but still this hingest on Chrome, and not 3CX.
 
Last edited:
  • Like
Reactions: eagle37
Status
Not open for further replies.

Forum statistics

Threads
112,025
Messages
590,367
Members
164,977
Latest member
jasimbutt82