Solved HTEK Normal and M version Firmware. 3CX downloads wrong one?

[PimvanD]

Banging my head against this issue with HTEK Firmware and 3CX

• 3CX Version, Professional Annual 16.0..493
• Server OS, Debian 9
• Is the 3CX Server Hosted and where? Local Network
• IP Phone Make/Model/Firmware HTEK 903 and 924 (DSP Patch with M)
• Provisioning Method: Local
• Trunk Provider or Gateway Make/Model: Keensystems
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO

Having an issue with updating firmware through 3CX console. The issue here is that I think the wrong firmware is downloaded by 3CX which are not usable by the phone we are using.

I have had contact with Tiptel NL about the firmware and it seems that when the phones have DSP Patch x.x.x.xM (M version) the normal firmwares which are downloaded are not loaded/usable

After some research and looking at the provision link in the Phones the wrong firmware is indeed downloaded and stored @ /var/lib/3cxpbx/Instance1/Data/Http/Interface/provisioning/xxxxxxxxxxxxx/firmware/htek



So in my case I have HTEK 903 and an HTEK924 which both have DSP 9.0.3 (Patch 1.0.16M) The M Version
For that I need the M firmware files.

If i download the firmware from HTEK I get both the "normal" fw and the "M" fw.



As for testing: I have put the right firmware (M version) file manually in the provisioning/xxxxxxxxxxxfirmware/htek folder and when clicking Firmware upgrade in the 3CX console it worked.

I don't want to put each new FW in the folder on the server the let these phones get their FW upgrades, nor do we want to manually upgrade them.

 

[JohnS_3CX]

Hi,

Are you perhaps using localized firmware for the Benelux region when you originally bought the phones
(Similar to Lydis Yealink firmware) ?

 

[PimvanD]

Nope, these phones came out of the box with this DSP Patch M variant.

 

[JohnS_3CX]

I also noticed the following:

The 924 is without the M
The 924E is with the M

I'm wondering, is your model perhaps a 924E but provisioned in the management console as a plain 924?

 

[PimvanD]

I will look into this tomorrow. It is getting more strange by the minute.

Tiptel sells "924, 924E and 903" on the website
3CX has "924, 924E and 903" as extension phones
Phone boxes saying "924, 924M, 903M" (we are buying normal phones but seems we getting M variants)

Normal 924 en 903 phones having DSP Patch M. It seems there is something going on with the FW

I will send a mail to Tiptel about the products they sell to figure out what is going on.
Whenever I get an answer I will repost here to see if we need to go into this any further.

 

[PimvanD]

Found the problem.

We have 2 HTEK 924 models in general, the 924 and the 924E

The 924E is using firmware FW920M.ROM
The 924 **WAS** using FW924.ROM

After some research and calling with Tiptel about this. They gave the 924 another chipset + firmware and also gave the 924 another name which is 924M.
The firmware which the 924(M) is using now is identical to the 924E -> FW920M.ROM.

Tiptel already made this clear to 3CX that the 924/924M (which are the same phones but other chipsets/fw) need FW924M.ROM instead of FW924.ROM.
Unfortunately 3CX is not responding to this.

Because of this all the 924M phones are still downloading the FW924.ROM which are not applicable to these phones.

 

[StefanW]

Hello @PimvanD we hold not cooperation with Tiptel

 

[JohnS_3CX]

Then this discussion is no longer about a supported phone from what you describe.

We support only the following:

Htek UC924 - fw924.rom
Htek UC924E - fw920m.rom

I'm not familiar with Htek UC924(M). If it reports the wrong User Agent and pretends to be another model then we can not do anything about this. This is something for Htek to address.

We talk with Htek directly for our supported models, not Tiptel.

 

[PimvanD]

That is what I figured.
We changed our own standards for buying phones for our clients now to 924E

Problem solved.