HTTPS Provisioning failure on P Series

This is similar to a previous post but focuses to a single issue. I also tryed to open a support ticket (it’s included for the Sangoma phones, right?) but I have issue logging in at help.sangoma.com.

I used HTTPS provisioning for the initial deployment of a few Sangoma P-Series phones. Now, it no longer works.

More details follow:

  • The FreePBX server now has a couple of ZeroSSL free certificates for multiple DNS names. Each certificate includes both names as Subject Alternative Names (SANs). The certificates contain the full chain and are trusted by browsers. I also tried switching between the two certificates.
  • I switched to the TCP channel for provisioning the P330, performed a factory reset, and the phone was able to register and get its extension configuration. However, it still does not fully provision—for example, BLF settings are missing.
  • The BLF XML file is correctly generated, and I can successfully download it via HTTPS in a browser or with cURL without certificate warnings.
  • The phone are in the same VLAN of the FreePBX, no external firewall involved.
  • Provisioning protocol is setup as https on non-standard port selected via System Admin commercial module, with credentials.

The FreePBX 17 server is fully updated now (Jul 2025) and also the phone firmware is updated (4_26_1).

HTTPS provisioning was working at the beginning of the year, but had not been used again until recently.

Did you get this resolved?

Hi @unlikely
There are no known issues with this. We are able to provision PX phones via HTTPS, and even the BLF keys are successfully loaded to the phone.

Can you clarify the exact issue you’re facing with BLF?

  • Are the BLF keys not being loaded to the phone?
  • Are the BLF keys loaded but not displaying?
  • Are the BLF key files (exten-1-blf.xml and exten-1.xml) not being downloaded?

You can check the logs on a v17 system — they are stored at:
/var/log/apache2/other_vhosts_access.log