tel: / Click to dial Webclient without Click2call extension

[alanjmcfL]

Is it still the case that the Web Client requires the Click2Call extension for TEL: link handling?

I've done the following to make this work for me without the extension. One just has to paste this into the browser dev tools console. (The console needs to be opened from a tab with the webclient open.) That registers a TEL: protocol handler that points at the correct Web Client URL

window.navigator.registerProtocolHandler("tel", "https://luma.3cx.uk/webclient/#/call?phone=%s","phone");

We can see details on browser protocol handling at:

• https://developer.mozilla.org/en-US...erProtocolHandler/Web-based_protocol_handlers
• https://developer.mozilla.org/en-US/docs/Web/API/Navigator/registerProtocolHandler

Our CRM-like system produces <a href="tel:12345678"> links for phone number, with the Desktop Client that worked great. I'm uncomfortable installing web browser extensions that require full read/write access to all web pages the browser opens.

 

[alanjmcfL]

Would be great if that could be added to the Web Client behaviour.

 

[alanjmcfL]

I can confirm that this works for external tel: links too. If I do eg "start tel:1234567" in a command-prompt a new tab opens in Edge with 3CX's dialer window open and the number there ready to dial.

You just need to have Edge as the handler for tel: — and it will prompt if not previous set etc.

 

[alanjmcfL]

 

[PeterM]

That works well. Any way to make the 3CX web client to open in a new browser tab?

 

[alanjmcfL]

That works well. Any way to make the 3CX web client to open in a new browser tab?

Yeh, I just noticed myself that that’s an issue (the dialler uses the window the tel: link is in).

I wonder if the 3CX PWA registered the protocol handler in its metadata file[1], then the link would open in the PWA‘s window rather than the current window. I’m away this week, so won’t be able to test.

(Otherwise, I guess 3CX could change the #/call page to launch the dialler elsewhere, and then do history.back.)

Otherwise the user will just need to ctrl+click the link etc.



[1] https://github.com/MicrosoftEdge/MS...r.md#custom-protocol-url-is-used-as-an-iframe
https://learn.microsoft.com/en-us/m...ive-web-apps-chromium/how-to/handle-protocols
https://developer.chrome.com/articles/url-protocol-handler/