When I have a phone number that contains spaces, for example +1 123 456 7890, click-to-call displays the following:
Clicking yes results in an attempted call 12012320456207890. (Blue = the real phone number to dial; Red = junk)
Although the percent symbol is rightly stripped, there's no validation for encoded spaces (%20) which leaves behind the hex code for space (20) which is then interpreted as part of the number.
On the phone
In Jabber
I'm using Jabber 11.8.2.50390 on Windows 10 v1607, but other affected versions appear to be 11.6.0.35037, 11.7.1.46916 & 11.8.0.49608; there may be others as well.
Can anyone else reproduce?
Am trying to narrow the scope of the issue:
- is this a client bug?
- is this a configurable client setting?
- is this a configurable server-side setting?
- is this an issue with the application that's passing the number on to Jabber?
- is this something else entirely?
