UTF-8 Encoding for Telephone Numbers?

[chmars]

If I send a telephone number including the + character to a T4x telephone, the + is shown as %2B, i.e., there is something wrong with the UTF-8 encoding.

Any ideas?

[chmars]

Unfortunately, the issue is still reproducible. Any ideas?

[Christoph_tm]

Hi there,

I have the same problem here! We would urgently need proper UTF-8 encoding, because our CRM doesn't recognize contacts, of course. Also phone amego shows corrupted Caller ID when the name contains letters like „ö“ „ä“ etc. We want to switch to Yealink T48G with all our phones, because our Gigasets are EOL.

I already bought 3 phones and I'm quite upset a product these days still can't handle UTF-8!

Also Wifi Networks with e.g an "ö" in the SSID can't be connected to the T48G.

Are there any plans to solve this? If not I could dump the new phones right away...

Best,

Christoph

[chmars]

@Christoph, I haven't too much hope …

[complex1]

Hi,

I have test it on my T48G but I can’t reproduce the issues.

@chmars
1. Incoming calls started with a “+” sign are correctly shown in the call history log.

@Christoph_tm
2. I have create a contact in the local phonebook, give it Office Number 12 and then call the T48G from ext 12. The name is displayed correctly.

Please see the screenshots.