I have a couple of PBXact v15 installations running Yealink T5x Handsets (FW: 96.85.x.x).
These handsets have always provisioned out of the box/from factory reset via Authenticated HTTPS (using Yealink redirection service) no problem.
These handsets have always called a custom Remote Phonebook script to show & enable dialling Contact manager entries via Authenticated HTTPS no problem.
Since sometime last week (I think), the both these ‘Authenticated HTTPS’ based communications seem to have stopped working. Nothing has changed with the general setup of these installations. I do check & apply any new PBXact System/Module updates quite regularly & I did do this sometime last week (which possibly stopped these functions working as they did previously).
If I specify both the HTTPS-based Provisioning URL & RemotePB script URL in a Web Browser, the PBXacts respond no problem, it just doesn’t do the same from the Yealink handsets themselves.
I have switched a single Yealink handset on BOTH installations to use ‘Authenticated HTTP’ & hey-presto, all is working again.
Does anyone know if something changed in a module update recently that could have broken the ‘Authenticated HTTPS’ communications between PBXact & Yealink handsets ?
PS. I have found some forum articles that suggest Authenticated HTTPS with Yealink handsets didn’t work previously, however, it’s always worked for me on these v15 installations (until now).
Some recent updates which ‘might’ be relevant;
Also for reference;