Solved tel: HTML Link Bug With DTMF Comma

[chance-wmt]

Clicking on "tel:12223334444,123" results in the Windows client (latest V18 client) putting in "12223334444123" without a comma. The Windows app supports comma but it has to be manually entered.

The comma is typically used for 2 second pauses in DTMF.

 

[ChrisC_3CX]

This is actually expected behavior as the number will get normalized when using clicktocall, dashes, commas, dots etc will be removed.

The Windows app supports comma but it has to be manually entered.

The 3CX Windows App will allow it but it will again actually normalize the number by removing it before placing the call, so it makes no difference.

 

[chance-wmt]

This is actually expected behavior as the number will get normalized when using clicktocall, dashes, commas, dots etc will be removed.


The 3CX Windows App will allow it but it will again actually normalize the number by removing it before placing the call, so it makes no difference.

This is incorrect, if you manually put a comma in the Windows App dial it will pause for 2 seconds and does not remove it. Only clicktocall does.

 

[ChrisC_3CX]

if you manually put a comma in the Windows App dial it will pause for 2 seconds and does not remove it.

I actually just tested this on the latest 3CX Windows App version (16.3.0.261) and it does in fact remove the comma. This is the current implementation and will not be changed.