Solved 3XU Pro Firmware

[sbmuseart]

Hi,

Is version 2.4.7.5 going to be available in the cloud hosted version soon? I have having the same issue as found here https://www.3cx.com/community/threads/x3u-pro-provisioning.114806/#post-532021

Thanks,
Joe

 

[cobaltit]

There is no firmware difference between hosted 3CX and on-premise 3CX. But it will be out when it's out. Vendor releases firmware and provides to 3CX for testing, 3CX tests and if everything works, approves it.

 

[sbmuseart]

Well the issue is 3CX has only approved 2.4.7.5 for provisioning for the 3XU Pro phones. The phones come shipped with 2.4.7.4. When you assign to an extension in 3CX, 3CX does not update the firmware and then you end up having the phone duplicated as 3CX has said only 2.4.7.5 is approved with them. Why not push that firmware to the phone? Kinda silly to have to upgrade every phone first to 2.4.7.5 before provisioning.

 

[sbmuseart]

and wow sorry for the misspelling on the thread title lol....I was so tired when I posted this.

 

[cobaltit]

That's not 3CX's fault. As stated in the post you linked 2.4.7.4 sends the wrong UA which is a Fanvil mistake. 3CX doesn't think the phone is provisioned properly so it can't push the firmware to the phone. You will need to update it manually.

 

[sbmuseart]

That's not 3CX's fault. As stated in the post you linked 2.4.7.4 sends the wrong UA which is a Fanvil mistake. 3CX doesn't think the phone is provisioned properly so it can't push the firmware to the phone. You will need to update it manually.

Ok, but when adding to the 3CX system, why not check and then update the firmware to latest version? Other phone systems I have used would update to latest firmware available on their system for the model upon initial provisioning. 3CX obviously knows the model of the phone and firmware it has as it shows it as ready to be provisioned. So, yes this is 3CX's fault. They should not allow for a phone to be provisioned if it is not on the correct level or firmware needed or update the phone's firmware automatically before final provisioning.

 

[cobaltit]

What you described is normally how it works. But in this case, when 3CX tries to provision as phone model A, the phone replies back and says it's model B. 3CX won't push a firmware down that maybe wrong as it might brick the phone. So yes, it is Fanvil fault because that particular version of firmware is not replying to SIP packets with the correct UA. All of this was already explained in the post that you linked.

 

[sbmuseart]

What you described is normally how it works. But in this case, when 3CX tries to provision as phone model A, the phone replies back and says it's model B. 3CX won't push a firmware down that maybe wrong as it might brick the phone. So yes, it is Fanvil fault because that particular version of firmware is not replying to SIP packets with the correct UA. All of this was already explained in the post that you linked.

No, not quite. Phone replies back that it is the same model in both cases. Both instances 3CX knows the phone is a 3XU Pro. That is not what the link described at all. The link described where the firmware was not understood by 3CX so did not provision completely and ended up with duplication. So back to my original question....3CX knows the model of the phone and the firmware that is on there, why not update the firmware to the version that is compatible. Same model from 3CX point of view on both firmware versions. 3CX knows it is a 3XU Pro, push the correct firmware down. Makes zero sense.

 

[cobaltit]

So I'm not sure if we're reading different posts, and I don't have a phone to test myself but this seems to imply it's not returning the expected value in the UA:



So assuming the above is true, then my statement still stands. 3CX will upgrade firmware as long as here is a simple path forward and nothing stopping them on the phone side. There are a number of other scenarios (usually SSL related or step-upgrade related) but typically as long as you get a supported phone and keep it current to avoid big firmware jumps you are ok. Your scenario is one of those exceptions where you did everything right but got bit by a roll of the dice.

 

[sbmuseart]

So I'm not sure if we're reading different posts, and I don't have a phone to test myself but this seems to imply it's not returning the expected value in the UA:

View attachment 30635

So assuming the above is true, then my statement still stands. 3CX will upgrade firmware as long as here is a simple path forward and nothing stopping them on the phone side. There are a number of other scenarios (usually SSL related or step-upgrade related) but typically as long as you get a supported phone and keep it current to avoid big firmware jumps you are ok. Your scenario is one of those exceptions where you did everything right but got bit by a roll of the dice.

Alright....still does not seem right...3CX knows the old firmware version...it is illogical to not upgrade it to latest version automatically. Besides if was true about the previous version being unsupported, why even attempt to provision it? Going to drop this now as gotta move on in my life.

 

[JohnS_3CX]

Hmm I think the whole discussion probably stems from a misconception of how 3CX works, so lets make some clarifications:

1.) 3CX checks the phone user agent against a list of known supported phones.

2.) If a match is made, 3CX checks the reported firmware version, against the known latest supported one

3.) If the reported firmware is different than the latest supported one, any phones that are running an older version will be marked in Red so you can upgrade them.

Alright....still does not seem right...3CX knows the old firmware version...it is illogical to not upgrade it to latest version

It would indeed appear illogical if you were not aware of how 3CX works, or hadn't yet read our Fanvil guide.
In your case, the phones failed at step one (no match was ever made), hence the procedure never took off the ground to begin with.

Our guide is very clear on this: You must first upgrade your firmware before you even attempt to provision the phone.

https://www.3cx.com/sip-phones/fanvil-x3-x5/


The TL;DR is that your phones were effectively unsupported in the state they arrived and this is not something you can blame on 3CX or the manufacturer. It's simply an inconvenient occurrence, especially with the early batches of phones that come with older firmware.