Solved Spaces in tel: phone number included as 20 in number that is passed to dialer

[JerDTSL]

last year i originally was told this was fixed, it hasn't been:
https://www.3cx.com/community/threads/spaces-in-phone-number-included-as-20-in-windows-client.69714/

Lots of people put spaces in phone numbers (like 06 123 2117). Those spaces (%20 in html) get converted to "20" when you do a click to call with the browser plug in.

example, this is the html from an email signature: <a href="tel:06%20123%202117" target="_blank">

When i click to call it wants to dial 0620123202117.

 

[NickD_3CX]

Hi @JerDTSL ,

Please read the section 5.1.1 of the relevant RFC for "tel":
https://tools.ietf.org/html/rfc3966#section-5.1.1

Then also check out section 8 on how it should be used in HTML:
https://tools.ietf.org/html/rfc3966#section-8

So, what you have there is wrong. According to the RFC it should be:
<a href="tel:061232117">06 123 2117</a>

 

[JerDTSL]

You're missing the point, I'm not creating non-confirming tel links, I'm recieving them from all my customers and friends. I'm not asking 3cx to be non-compliant, I'm asking 3CX to deal innovatively with others non-compliance.

I sympathize with you... no one reads or conforms to RFC3966 and it frustrates us rigid left brain folks.

But 9/10 of the email signatures I receive (from annoying non-technical customers) have spaces in the telephone numbers.

What if usability were a primary concern? What if clicking on those non-confirming tel links actually 'just worked'. 3CX would be like a creative genius Apple type instead of a RFC quoting IBM type.

What do you want to be?

 

[NickD_3CX]

The implementation is correct, so there is no bug here, that much we agree on.

Given that this would require some work on the client side, I think you it should be posted in "Ideas".
While you may thinking "why is removing a few spaces such a big deal?", you never know what problems a simple change like this may cause.

 

[N_G]

Nick has a point about it being for the ideas forum, but

"3CX would be like a creative genius Apple type instead of a RFC quoting IBM type. What do you want to be?"

Thats definitely a bit of much needed humor here in the forum

We will look into it....

 

[Constantinos Constantinou]

Hello @JerDTSL ,

Can you please share with me the version of the Chrome Extension that you have ?

We have exactly the same case on our test scenarios where we have "%20" in the tel: number, that when it is passed on Chrome Extension, those spaces are ignored.

 

[NickD_3CX]

Just an update on this, in the next update of the Windows App, this will be addressed. It will behave like the Browser Extension, meaning that spaces in TEL protocol links ('%20' characters) will be correctly parsed and loaded into the client.

 

[JerDTSL]

This is very cool. I'm speechless! Thankyou.