Click2Call extension too aggressive on web pages

[drenda]

Hi,
we developed a PMS for opticians in cloud and some customer have the 3CX click2call extension. Lately in many view of the application, some label are considered as phone numbers even if they are not.
I attach an example where you see the company address and a product item are considered as phone number. This create some problems because our click action on the product, for example, is prevented from your extension.

This anomalous behaviour is something new (maybe an update of your plugin).

Do you have some suggestion in order to instruct the plugin to not consider some elements of the page, or better avoid that it consider as phone numbers values that are not phone numbers?

Thanks for your support

 

[Constantinos Constantinou]

Hello @drenda ,

The extension has the option to configure pages that will be excluded from parsing and creation of hyperlinks.

Is this an option that fits your case?

Thank you.

 

[drenda]

We made an integration with 3CX CRM, so we like the click2call function. We would like our customer can use your softphone to make calls from our SaaS software. What's wrong here is something that is not a phone number is considered like that.

I don't think we can exclude only "some" pages because this can happens in many many pages of our software (we are speaking of hundreds of pages).

Do you have some suggestions? Why did the extension worked differently before; can we do something to prevent the wrong parsing?

Thanks

 

[Evolute IT]

An option for how many digits required minimum would be a great way to avoid that.

We have some labels and IDs too being marked as phone numbers and it even messed up one of our softwares that has links and they got overwritten.

 

[NickD_3CX]

We made an integration with 3CX CRM, so we like the click2call function. We would like our customer can use your softphone to make calls from our SaaS software. What's wrong here is something that is not a phone number is considered like that.

I don't think we can exclude only "some" pages because this can happens in many many pages of our software (we are speaking of hundreds of pages).

Do you have some suggestions? Why did the extension worked differently before; can we do something to prevent the wrong parsing?

Thanks

We will take your feedback into consideration.

While it's not something that 3CX made, you could use some other Chrome Plugin like "Tel Linker" (search for the latest published one...) and there you can actually give it a regex on what number formats to detect.
Before releasing our own, I had done some experimenting with it here:
https://www.3cx.com/community/threads/3cx-v18-client-gui-problems.83399/#post-388734

Note that this will convert the number to "tel" protocol, so the only option you will have is to load it into the Desktop App, not the WebClient.

 

[drenda]

@NickD93 thanks for your reply. Actually I think it would be enough if in your plugin you add a settings that avoid the plugin to parse something different from "tel:"

Right now when you find a tag <a href="tel:+390123456"> you convert it as

<a _ngcontent-kik-c286="" style="padding: 0 8px;" href="" title="Call +3912345678 via 3CX" tcxhref="+3912345678" target="_blank">+3912345678</a>

and that's great. What I don't expect is that your plugin does this where there isn't the tel: protocol. If you can add a setting to enable or disable this function I think it's enough.

 

[NickD_3CX]

If you are satisfied with only "tel", then you don't need the Click2Call plugin at all!

"tel" can be detected by Windows and automatically launched into the Desktop App.

The Click2Call plugin only fills in for numbers that aren't "tel", and also gives the additional option of loading them into the WebClient (that's why it converts 'tel' numbers too...).

 

[drenda]

@NickD_3CX Thanks for your reply. What if I want to use the WebClient and not the Desktop app?

 

[NickD_3CX]

@NickD_3CX Thanks for your reply. What if I want to use the WebClient and not the Desktop app?

Then the only choice you have right now is the 3CX Click2Call plugin, with whatever behavior that entails at the moment.

 

[drenda]

Then the only choice you have right now is the 3CX Click2Call plugin, with whatever behavior that entails at the moment.

Thanks. Do you think could be an idea to add a settings in the plugin to change the behaviour as I described before?
Something like:

• parse only tel: protocol
• parse everything

in order to leave the user the choice to select what the proper function based on the SaaS software he uses. In our case, the tel: option would be perfect because we always use that standard when we display phone numbers in the application.

Thanks

 

[NickD_3CX]

Thanks. Do you think could be an idea to add a settings in the plugin to change the behaviour as I described before?
Something like:

• parse only tel: protocol
• parse everything

in order to leave the user the choice to select what the proper function based on the SaaS software he uses. In our case, the tel: option would be perfect because we always use that standard when we display phone numbers in the application.

Thanks

Of course!

Speak with your 3CX Partner to open a thread in the Ideas section, or upvote an existing thread if it exists.
Our Product Team monitors all Ideas carefully and decides what will and will not be implemented.

I suggested alternatives because I sensed some urgency in your post, as in you want it now. Even if your suggestions are accepted it will need some time to be implemented and will almost certainly will be after the holidays.

Anyhow, we have discussed a few alternative approaches you could follow, so hopefully you can chose the less impactful way forward depending on your project.

 

[drenda]

Thanks for the clarification. Of course the feature is important for our customer. Right now we should suggest them one of the alternative you suggested, but we know if not the "best" option.
I hope my suggestion will be useful to improve your extension because (as a developer) I feel it doesn't require an incredible effort but it provides value on the customer side.

Thanks