Solved Yealink T46G Shared Park BLF provisioning bug

[SyncWave]

This may apply to other T4XG models, however, we've found that under the most current 3CX supported firmware (28.83.0.130) you can manually provision the phone to have a working Shared Park DSSKey. However, if you try and configure this in the webclient BLF tab and reboot the phone the button never provisions but other buttons we setup for that phone like BLF keys do.

 

[SyncWave]

We are starting the process of getting older clients on FreePBX to switch to 3CX and many of them have T46G and T42G phones so allowing them to manage their BLFs error free would be great.

 

[JohnS_3CX]

Hi @SyncWave

Manual provisioning (ie. adding the SP on via the phone menus) is not supported - you must ensure the phone is provisioned as per our instructions otherwise the webclient BLFs will have no effect on the phone the way you wanted. https://www.3cx.com/sip-phones/yealink-t4-series/

After you have provisioned the phone as per our guide, you can check to see if adding BLFs will also work:


1. Firstly edit the extension from the management console and ensure has the right to "Park".

2. Then on the BLF tab, assign a shared parking and press OK to save.

3. Now restart the phone, has the BLF for SP (shared parking) appeared?

PS: I have tested this on a properly provisioned T46G v28.83.0.130 and sure in enough after rebooting it appeared

 

[SyncWave]

Thanks for the followup. From prior testing on older 3CX supported firmware it didn't work. At one point the syntex itself SP0 was invalid (alpha not supported). The manual phone entry was just a test to see if the syntex was now supported like on newer model phones. When I saw that work I assigned the key via the webclient and rebooted to a different T46G phone and it didn't show up within 3min of a reboot I made this post. Strangely enough it did show up on the phone like 2 hours after the reboot.

Most of my testing was older and it certainly didn't work but I didn't do the full battery of tests on this version prior to posting. Thanks!

 

[JohnS_3CX]

Hi @SyncWave

Very glad to hear! It might have been a fluke, but once the phone reached out for provisioning it managed fine then