Solved BLF Function quit with V18 on Yealink

[Mark Colman]

You might wanna see whether your firewall is blocking any traffic to our activation servers.

I have the firewall team looking. but doesn't the firewall checker take care of that?

 

[JohnS_3CX]

No, the firewall checker tests to see if your SIP ports, Audio ports work.

It will not check whether your PBX can reach the activation server.

Besides, that's an outgoing TLS connection so no port forwards are needed. The only thing you need to do is allow the PBX to have internet access, and not block outgoing TLS traffic.

 

[Mark Colman]

So, they added Google's servers to the Debian DNS lookup, and then were able to get the license page to work. Several update license selections and I re-provisioned one phone, and it is all working now. Wild times!!!

Thanks everyone for your help!
Mark

 

[SweetAction]

Question for the 3CX Team

Mark stated BLFs work in webclient but not on IP Phone. Is the webclient treated differently then an IP phone with regards to BLF and licenses?

 

[NickD_3CX]

Question for the 3CX Team

Mark stated BLFs work in webclient but not on IP Phone. Is the webclient treated differently then an IP phone with regards to BLF and licenses?

When the 3CX server cannot reach the activation server at all and has never fully activated, it goes into a 'weird' state, think of it like having a special license type with less features than "Standard".

In this case, then yes, it is very likely, however I need to stress out that this is purely due to this 'weird' state I am referring to.
Under normal circumstances, BLF functionality is available in all license types.