3CX Windows App BLFs change after changes of Provisioning

[Kiwi_at]

Hey there,

we have installed v16.3.0.220 of the 3CX Client for Windows. This is no post-update issue, it's seems like maybe a general thing.
If we configure BLFs on Windows-Clients, they seem to be different from the serverside BLFs of the extension. If I add a new BLF it also gets added to the serverside view of the extensions BLFs, no extensions seem to be missing, they are just sorted differently.
Our problem is if we make serverside changes, for example Codecs in Provisioning, the BLFs of the Windows-Client gets overwritten with the serverside BLF-Config.

Why are they different? Is this something I can prevent? Is this a bug or isn't it recommended to configure BLFs directly via the Windows-Client?

 

[NickD_3CX]

The new version of the Windows App, in combination with 3CX PBX V18 will most likely solve this issue.

 

[Kiwi_at]

Thanks for the answer, I just looked into that, there isn't a stable release of v18 right?

 

[NickD_3CX]

No, not yet, but there is the Alpha 3 release if you want to check it out and provide feedback:
https://www.3cx.com/blog/releases/v18-alpha-3/

Final release though shouldn't be very far away.