We recently upgraded from V14 to V15. Two strange issues, which I have tested for hours but cannot figure out, are related to the provisioning files for our phones. Problem 1: V15 does not appear to be creating new or updated provisioning files. (I have worked with these files in depth in V14 due to our use of some legacy phones.) For example, if a core change is made to an existing extension, this would normally cause the system to produce an updated provisioning file in V14. For example, change the name associated with an extension, save the change, and an updated provisioning file should be created. This no longer occurs. If a completely new extension is created (with a phone configured on the "phone provisioning" tab), a matching provisioning file is not created when the extension is saved. This always occurred in V14 and seems mandatory in order for phones to provision. I have tested by selecting multiple types of phone models when creating these new test extensions. I have verified the settings and the location where the system claims that the provisioning files should be found. None of this has changed from our V14 install. URL: "http://oursubdomain.3cx.us:5000/provisioning/xxxxxxxxx" File Path: C:\ProgramData\3CX\Instance1\Data\Http\Interface\provisioning\xxxxxxxxx All of the files from our V14 are in place, but nothing new is being added. Does anyone have any possible ideas as to why this would be happening? Second Issue: Provisioning files cannot be accessed remotely using http. Before the upgrade I could test the ability of a phone to access provisioning files by viewing one of these files through a web browser. For example: "http://oursubdomain.3cx.us:5000/provisioning/xxxxxxxxx/54781A13F837.xml" should be able to be viewed through a browser. This worked fine in V14. No changes to our server or firewall settings have occurred. When trying to access any file in the provisioning directory through a browser, the browser URL is auto-forwarded to the "https" version. The settings within the extensions, on the phone provisioning tab, clearly list the Provisioning Link as "http://oursubdomain.3cx.us:5000/provisioning/xxxxxxxxx/54781A13F837.xml". I am able to view provisioning files through a browser over https, but our phones do not support this. ("https://oursubdomain.3cx.us:5001/provisioning/xxxxxxxxx/54781A13F837.xml" for example) The system should be allowing http connections to the provisioning files, but I am unable to determine why the upgraded 3CX server is not allowing this. If anyone has ideas I would appreciate it.