CallerID with umlauts / special letters

[Starlifter]

Dear Yealink-Support,

I have in use several phones of your company and like them very much. But there is one thing, that my users complain about: the german umlauts aren't recongised by the phones.

But step by step:

As you might know, there are some special language-typical letters out there in the world. In Germany, where I come from, there are f.e. umlauts like "ä" and "ö". There also is a special letter "s" in the german alphabet: "ß".

If one of these letters is part of an incoming caller ID, the Yealink phones (I've tested it with a T38G) doesn't display it. Instead, there will be a questionmark. So, for example, the german name "Müller" (would be Miller in english) is displayed as "M?ller". That's not good. My Aastra phones on the same Asterisk 11 (FreePBX 2.11) machine display the CID correctly.

So I think it is an issue with your phones. They seam not to supoort UTF-8 which they should. Could you please have a look at this?

Thank you!

Greetings from Germany!

[Yealink Support]

Hi Starlifter,

Thanks to your opinion. Can you telll me the version of your T38G?
I test with 38.70.0.143 and this caller ID name can display correctly.

[Starlifter]

Hi,

of course I can. I thought I was using the newest available firmware - 38.70.0.125. But as I see in your post, there is a newer one... Where do I get it? On your homepage, there only is 38.70.0.125 available for download.

I then would report, if I encounter the same issue with the new firmware.

Bye!

[Yealink Support]

Hi Starlifter,

We released the T38G and T32G firmware 3x.70.0.143 which supported Multicast paging feature, please download the firmware as below:
ftp://yealinkftp:yealinkftp@ftp.yealink....wares/T3X/
Thanks.

[lorn10]

I want to note here that this umlaut issue is still present at T32G and T38G also with newest firmware 32.70.1.33 & 38.70.1.33.

I have posted this information at the following thread: http://forum.yealink.com/forum/showthrea...5#pid12765

[Yealink_Daniel]

Dear Lorn10，

I have try to replicate this issue in yealink site, the issue doesn’t exist. My test scenario as below:
PBX: 3CX
Account name: “äöü” ( extension is 1001 ) T46G ( 28.73.0.45 )
Account name: “äöüäöü” ( extension is 1002 ) T38G ( 38.70.1.33 & 38.70.0.185 )
Account name: “äöüäöüäöü” ( extension is 1003 ) T32G ( 32.70.1.33 & 32.70.0.185 )
Make them call each other, the caller ID displayed at the phones are correct.

So could you please help to confirm with your service provider to check whether the caller ID module is correct ? Thank you advanced.
If the caller ID module is correct, please help to get a Correct Syslog, Config.bin and Trace.

How to get a Correct Syslog, Config.bin and Trace, please refer the FAQ below:
http://forum.yealink.com/forum/showthread.php?tid=1319

Best Regards

[lorn10]

(01-27-2015 05:01 PM)Yealink_Daniel Wrote:  Dear Lorn10，

I have try to replicate this issue in yealink site, the issue doesn’t exist. My test scenario as below:
PBX: 3CX
...

Best Regards

Dear Daniel

Many thanks for that fast and detailed answer!

That's really strange, I can reproduce this umlaut error with firmware 38.70.1.33 and 38.70.0.185. For example, Letter ü is displayed as eA, letter ä is displayed eO. Interestingly, internal calls with ä ö ü are displayed correctly. Also entries in the local phone directory are displayed correctly.

I use FreePBX 5.211.65-21 with CID Superfecta 2.11.16. The source of the CID's is Swiss phone book provider local.ch.

Well, it seems that the problem could be rooted in the CID Superfecta module. Will check this first. Thanks for your efforts.

[lorn10]

Ok, problem is now solved! It was not a Yealink related issue, - a PHP unicode module (UTF-8 and UCS-2) was missing at my PBX.

Note, I can confirm that this solution works for FreePBX. Most likely it will also work for all other Red Hat Linux-based distributions; this includes RHEL, Fedora, CentOS, Mandriva, etc.

To solve this umlaut / special letter issue, please follow these steps:

Check if PHP mbstring extension is installed:

Code:

#>php -m

If not installed, install it with the following command:

Code:

#>yum install php-mbstring

Then you must restart the HTTP service:

Code:

service httpd restart

Finished! I suggest you to completely restart the PBX. After these steps are applied all CID Superfecta Lookups are displayed correctly. Many thanks to user lgaetz from Superfecta devolper team at GitHub!

[Yealink_Daniel]

Dear Lorn10,

Thank you for your sharing.
If there is any questions, please feel free to contact us.

Best regards
Daniel