Solved Upgraded to v18 - BLFs no longer work

[cparker_RCT]

I guess I'm just gonna be posted like crazy today!

My internal system is filled with this in the activity log.
08/13/2021 4:43:09 AM - [CM101008]: The '' feature is disabled in currently activated licenseBLF

Both Yealink and Fanvil phones cannot subscribe to presence information, latest firmware behind v18 SBC with freshly upgraded PBX to v18. Haven't tested other phones like Polycom yet. No custom templates are in use.

I've rebooted both the PBX and SBC. This is a new one for me.

 

[cparker_RCT]

Just for giggles I tried poking my shared parking BLF slot on the windows client to see if 3CX would respond appropriately. It was set to CTSA with my Yealink. It got stuck on trying and connected (still showed trying while in a call) to parking orbit in SP1. Then magically, all of my phones started receiving BLF subscriptions.

Rebooted the PBX, SBC and phones a few more times and I can't reproduce it.

Ghosts perhaps?

 

[Saqqara]

Try refreshing your license - Settings -> License , click on 'Refresh License Key Information'

 

[cparker_RCT]

Try refreshing your license - Settings -> License , click on 'Refresh License Key Information'

In my haste/confusion that may have been what fixed it. I wonder if it jiggled the handle in the database to fix entitlement.

Nothing had changed in the UI, everything looked correct and it's not a new license either, but it is current.

 

[ChrisC_3CX]

It may be just that for some reason the PBX wasn't able to contact our activation service to activate the license. Just to confirm, did manually clicking the "Refresh License Key Information" button completely resolve the issue, is everything now in order?

 

[cparker_RCT]

I believe it did. This is a legacy install in Digital Ocean - not the ISO. When it upgraded to Debian 10 it didn't have networking, so I had to reboot it again to get the networking stack up. Surprised it didn't refresh the license info on boot once I fixed Internet connectivity. If this is all I run into on a fresh upgrade I'm still happy.
If anything this is a documented fix for anyone else that might stumble upon it.

 

[ChrisC_3CX]

Glad to hear this got resolved!