Solved BLF issue with Yealink Phones

Status
Not open for further replies.

ict-project

Silver Partner
Advanced Certified
Joined
Jul 28, 2020
Messages
8
Reaction score
1
Hello,

since the latest Update from 3CX to version 18.0.1880, the BLF settings do not seem to sync with the phones anymore.

That means, when users set the BLF settings on the client or webinterface, they are not synchronized to the phone.

The Phones (Yealink T42S and T48S) have the newest Firmware version 66.86.0.5.

Restart of the Phones and "Auto Provision now" was unsuccessful...

The Phones are STUN provisioned.

Has someone any idea?

Thanks
 
Hi @ict-project

Have a user set BLFs from the webclient, and then log in the management console as admin to check their extension BLFs.

Do the BLFs they just set appear there too?
 
Thank you, for the quick reply!

Yes, the management console syncs the settings correctly!
 
Ok, if they appear on the management console then the issue is probably not related to V18, I think that just may be a coincidence.

Since the phones are provisioned over STUN though, they rely on two things:

1) They should be able to reach your PBX via FQDN and on the HTTPS port (usually 5001). If this is blocked for them, they will no longer reprovision no matter what you do.

2) The PBX must have valid certificates. If these expire, then the phones can no longer connect to the server. Also, if you are using your own custom certificates, they have to be supported by the specific phone manufacturer. And finally, the time must be correct on both the phones and the PBX so the TLS connection will not fail.
 
Solved: The custom certificate on the Phone was expired....
 
Glad to hear you found the issue!
 
Status
Not open for further replies.

Members Online Now

No members online now.

Forum statistics

Threads
111,831
Messages
589,277
Members
164,660
Latest member
RJenkinsROCK