3CX update 2025.10.19 caused deskphones BLF and extensions to disappear from deskphones.

[Hendry:5060]

Good day all,

I had a few of my PBXs auto-update the big ones every sunday when required. This happened, and my BLF buttons and my extensions on my reception phones went missing.
Can I please ask what is the issue is it provisioning link is it my setups or is it the firmware that 3cx has on archive I used that BTW.

Looking forward to any feedback and some tricks/steps methods to try.

Thanks,
Hendry

 

[KyriacosS_3CX]

Hello,

Is that phone supported? Are the BLFs visible in the Extension config or where they configured directly on the phone?

 

[Hendry:5060]

Hello,

Is that phone supported? Are the BLFs visible in the Extension config or where they configured directly on the phone?

Hi there,

They were configured on the phones directly. Not on ext in 3cx is that my problem?
Its Yealink T33G,T40G and the reception units is T46S with extention pads attached.

 

[Colorado VoIP]

Hi there,

They were configured on the phones directly. Not on ext in 3cx is that my problem?
Its Yealink T33G,T40G and the reception units is T46S with extention pads attached.

if you configured anything on the phone directly, those changes are overwritten every time the phone reprovisions itself (every 24 hours). you'll have to setup the BLFs on the extensions in 3cx and then they are pushed from the system.

 

[Hendry:5060]

if you configured anything on the phone directly, those changes are overwritten every time the phone reprovisions itself (every 24 hours). you'll have to setup the BLFs on the extensions in 3cx and then they are pushed from the system.

OK let me try that out weird thing is why did they not lose configs before this update?

I have done what you asked Ill get back tomorrow.

Warm regards,
Hendry

 

[Colorado VoIP]

that's a good question cause the yealink phones provision every 24 hours. if you plug a phone in at 9 am, you can watch the light flash the next day at 9 am and it re-sync's with the system.

 

[ITMgr2527]

OK let me try that out weird thing is why did they not lose configs before this update?

I have done what you asked Ill get back tomorrow.

Warm regards,
Hendry

Our users have reported mixed results on the lifespan of setting BLF keys, etc., directly on the phone. I surmise 3CX doesn't have anything set for the button manually configured by the user, they may occasionally stick around a little while longer than designed but I never tell them to set them direct; usually it's just staff trying to be independent. However, I always tell staff to not count on them sticking around if they add through the phone and to either (A) set them from the 3CX extension portal or (B) tell me so I can add them within 3CX. This is best practice and the only guaranteed way to ensure buttons remain.

 

[VoIPTools]

It also depends on how the phones were provisioned. Manual phones will not get updates from 3CX. Custom templates can be a factor as well. If you want your phones to work properly with 3CX, then make sure you are on the latest 3CX supported firmware, avoid custom templates, and auto-provision the phones properly via 3CX. Never show a customer how to forward their calls via the phone interface, rather, use 3CX presence statuses to forward calls. BLFs, and forwarding rules should ALWAYS be defined in the 3CX extension configuration settings and never directly on the phone. If you are touching the web interface of the phone for any reason, you are almost certainly doing something wrong.

 

[ITMgr2527]

It also depends on how the phones were provisioned. Manual phones will not get updates from 3CX. Custom templates can be a factor as well. If you want your phones to work properly with 3CX, then make sure you are on the latest 3CX supported firmware, avoid custom templates, and auto-provision the phones properly via 3CX. Never show a customer how to forward their calls via the phone interface, rather, use 3CX presence statuses to forward calls. BLFs, and forwarding rules should ALWAYS be defined in the 3CX extension configuration settings and never directly on the phone. If you are touching the web interface of the phone for any reason, you are almost certainly doing something wrong.

I'm not disagreeing with anything. Simple tangent but... the first day we deployed phones, we had a half-dozen users sending text messages directly from within the Yealink phones to one another (not 3CX chat but Yealink's native version). It was obnoxious! Some users dig in and think they can configure/use whatever features they can find on the phone itself, including chat, BLF keys, forwarding, etc.

 

[SteveITS]

A) yes, maintain the BLFs only in 3CX.

B) a few years ago we helped set up a Fanvil door phone for a client and the speed dial button was set in the phone. That stayed for several v18 updates but after upgrading to v20 we found that and each v20 update afterwards removed the button setting, though any daily provisioning did not. The answer, of course, was "A" above.

 

[fxbastler]

The answer, of course, was "A" above.

We know this problem and have it too. It happened again last week (i10S).

The tried-and-tested solution is to provision the doorphone completely manually or, after 3CX has automatically provisioned it, to remove the 3CX provisioning link from the doorphone.

The 3CX provisioning template doesn't support the many possible settings for such a device. Manually adjusting the template in 3CX is generally not worth the effort for us.

But yes: if telephone and BLF then management in the 3CX and only there.

 

[VoIPTools]

We have all experienced the joy of users tinkering. You can tell them not to set up forwarding from their phones, and why, and expound on the virtues and benefits of using the 3CX presence settings to do this, and they will ignore you. So, we can lead them in the path they should follow, but it is, unfortunately, their free agency to choose. I all feel your pain.

 

[JohnS_3CX]

We know this problem and have it too. It happened again last week (i10S).

Hi,

What exactly did you face with the i10S?

This is a supported model with firmware 2.12.48.25

It supports only "Speed Dial" type, in BLF position 1 to ring the doorbell.

 

[fxbastler]

What exactly did you face with the i10S?

It may be that the i10S's single front button can be configured and used with just a single, simple Speed Dial action in the 3CX template.

That's not enough for us or the customer.

The device is used as an intercom system in a vandal-proof emergency call bell, e.g. for pharmacies, called Notdienstklingel.
https://team3-gmbh.com/index.php?id=Produkte
If you expand the first product category you see a picture, the red thing, in the middle of it.

The i10S not only has a front button, but also an input and an output as a relay switch on the back. Various actions, including slightly more complex ones, can be defined for all of these inputs and outputs in the i10S. This is what's needed. The 3CX standard template overrides these individual settings. So we removed auto-provisioning.

This is a supported model with firmware 2.12.48.25

now ...

For a long time, there were also major problems with the required firmware for the device. The firmware provided by 3CX until recently was significantly too old, lacked features, and had problems. The current firmware provided by 3CX, while still not the most recent version for this device, no longer has these problems. Furthermore, there are now other ways to help with unsupported firmware in 3CX.

 

[JohnS_3CX]

Understood, so you were talking more about customization, not the default 3CX supported features.

 

[fxbastler]

Understood, so you were talking more about customization

Yes, that's what the device is for.

The only downside is that the other settings outside of the 3CX supported usage are overwritten by the provisioning. This could be solved differently in the template.