EPM Custom Firmware stupidity

endpoint
Tags: #<Tag:0x00007f4f4242c348>

(Jared Busch) #1

So the new custom firmware thing was implemented in Feb 2020.

Is no one actually using it? Because it does not work unless you make your custom firmware file name match what EPM uses for non-custom firmware.

The EPM Custom Firmware Management wiki does not list this as requirement.

I will go open a commercial support case (edit: I did #997357), and I expect it to get closed to No issue after someone updates the wiki. That is what happened last time I had an issue were something did not work like the wiki said. It is apparently much cheaper to piss people off than fix a bug.

Anyway. Uploaded 2 firmwares. The T40G firmware labeled as T40P because the G is not supported. And then the CP920 because while the model is supported, Sangoma has never, for years and years, put the firmware in an EPM firmware bundle.

But when I rebuild the template, it writes out the default rom names that it uses internally. Not the filename of the uploaded file.

Edit: When you make a custom firmware, the slot (2 in my case) is a symlink to the folder with the uploaded files.
image


#2

I’ve been meaning to try out this feature soon (though for Polycom phones) - any other gotcha’s that you’ve encountered?


(Kapil Gupta) #3

Hi @sorvani does below note in the wiki not making “uploaded file name should be same as phone requested or config generated file name” requirement clear?

Firmware file name is defined in DB which we used for normal EPM FW bundle as well so for custom firmware if we dont use the same file name then generated configuration will have different firmware name then actual file present in the server.


(Jared Busch) #4

No, because that is 100% not even a valid statement.

Every phone pulls the firmware file that the config file tells it to pull. No phone pulls a fixed file name for firmware.