Version 20.0 Update 2 caller ID not working on parked call

[kmhbjb]

We have Yealink T43u phones and after the update to 20.0 Update 2 last night we can no longer see caller ID when picking up a parked call. I reset the phone and are still having the same issue. The caller ID show up fine in the web app. The history on the phone only shows SP1, SP2, etc.

Thank you.

 

[lief]

We are experiencing the same issue with Fanvil X210 and X7C phones after upgrading from V18 to V20 Update 2 last evening on a locally hosted system. The caller ID does follow a transferred call properly (just having issues with parked calls) .

 

[alij]

Experiencing the same issue with T46S and T54W phones.

 

[lief]

We have noticed that when a parked call "recalls" it does include the caller ID. Unfortunately, it does not follow distinctive ring set on the extension so our receptionists cannot tell the difference between a recalled park or a new call coming in (different issue for a different post).

 

[TheodorosG_3CX]

We are aware of this issue and i currently under investigation.

 

[lief]

Thank you for the update!

 

[TheodorosG_3CX]

You are welcome.

 

[QCS-INF]

We are aware of this issue and i currently under investigation.

Hi TheodorosG

Thanks for recognizing you have identified the issue.
We have approximately 150+ systems we are looking to push the V20 update to and 95% of them all use desk phones primarily.
With the V18 EOL scheduled for the end of the year, we are really trying to avoid a mad rush in getting everyone updated.

The SP display issues as per this thread is pretty critical and if the fix is expected in the next patch we will hold out on upgrades till then, however if there is no foreseeable fix and we are going to be waiting another month - 2 months, we might be pressured to start upgrading clients regardless of the bug in order to avoid the EOL rush. Which will leave a pretty sour taste with pretty much all clients.(I'm sure other partners would agree)

Do you possibly have or able to get us any update or further information on a expected fix?

Cheers.

 

[TheodorosG_3CX]

I'm afraid not, you may keep up in our blog for any future update or fix.

 

[alij]

Any chance was this addressed in the Update 3 alpha? Didn't see anything in the notes.

 

[alij]

bumping

 

[SteveITS]

Should be fixed in update 3:
https://www.3cx.com/community/threa...g-the-number-of-the-caller.128104/post-614832