+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: Accessories (/forumdisplay.php?fid=28)
+--- Thread: EXP50 Teams - Not displaying Names (/showthread.php?tid=45740)
EXP50 Teams - Not displaying Names - cjohnston - 04-12-2022 01:30 AM
We have a Yealink MP56 with an attached EXP50. Recently we have seen where the names no longer display, only the pictures.
MP56
Firmware Version: 122.15.0.77
Hardware Version: 122.2.0.0.1.0.32
Company Portal Version: 5.0.5304.0
Teams Version 1449/1.0.94.2022030501
Admin Agent Version: 1.0.0.202112100118.product
EXP50
Firmware Version: 1.0.1.8
Hardware Version: 75.1.0.0.0.0.9.0
RE: EXP50 Teams - Not displaying Names - robertm - 04-13-2022 08:29 PM
(04-12-2022 01:30 AM)cjohnston Wrote: We have a Yealink MP56 with an attached EXP50. Recently we have seen where the names no longer display, only the pictures.
MP56
Firmware Version: 122.15.0.77
Hardware Version: 122.2.0.0.1.0.32
Company Portal Version: 5.0.5304.0
Teams Version 1449/1.0.94.2022030501
Admin Agent Version: 1.0.0.202112100118.product
EXP50
Firmware Version: 1.0.1.8
Hardware Version: 75.1.0.0.0.0.9.0
Also seeing the same issue with the same device and patch combination.
Looks like a factory wipe of the device fixes the issue but with no idea of root cause it's hard to know whether or not we can just do that and regard the issue as closed.
RE: EXP50 Teams - Not displaying Names - MMR1988 - 04-14-2022 03:17 PM
(04-13-2022 08:29 PM)robertm Wrote:(04-12-2022 01:30 AM)cjohnston Wrote: We have a Yealink MP56 with an attached EXP50. Recently we have seen where the names no longer display, only the pictures.
MP56
Firmware Version: 122.15.0.77
Hardware Version: 122.2.0.0.1.0.32
Company Portal Version: 5.0.5304.0
Teams Version 1449/1.0.94.2022030501
Admin Agent Version: 1.0.0.202112100118.product
EXP50
Firmware Version: 1.0.1.8
Hardware Version: 75.1.0.0.0.0.9.0
Also seeing the same issue with the same device and patch combination.
Looks like a factory wipe of the device fixes the issue but with no idea of root cause it's hard to know whether or not we can just do that and regard the issue as closed.
The problem seems to be solved with the yesterdays update of the teams app.