Click2Dial detecting/dialing every number on a page — any server-side (Admin Console) controls for number detection?

[itsernst]

We're rolling out the 3CX Click2Dial browser extension (Chrome/Edge) to our users and running into a problem with over-detection.


Setup

• 3CX V20 (self-hosted), Web Client / PWA
• Click2Dial extension configured with Web URL = https://<our-fqdn>
• Users dial from the web client (no desktop app / TAPI)

Problem


On certain websites, the extension is turning every number on the page into a clickable dial link — order numbers, IDs, dates, etc. — not just actual phone numbers. When a user clicks any of those numbers, it tries to place a call.


Constraint


I can't just exclude the whole site, because legitimate phone numbers live on the same URL(s) as the false positives. So a domain-level exclusion / "disable on this site" would kill the numbers we actually want to dial.


What I'm looking for


The per-extension options seem limited, and it feels like some detection controls are missing. My questions:

1. Are there any Admin Console / server-side settings in 3CX that control Click2Dial number-detection behavior (e.g., what qualifies as a phone number, minimum digit length, detection on/off) — pushed down to clients rather than set per-browser?
2. Is there a way to make detection stricter (e.g., only match tel: links or properly formatted numbers) instead of scanning all page text?
3. If this can only be managed at the extension level, what's the recommended approach for a site that mixes real phone numbers with lots of other numeric data on the same page? Is select-to-dial (manual highlight, auto-detection off) the intended fallback?

 

[TheodorosG_3CX]

Click-to-Dial is on the browser level and is not managed from the PBX. This will use the tel: protocol. Web sites with standard tel: protocol tags are automatically recognized and made clickable urls that will redirect to 3CX in order to make the call.