Solved Upgrading Snom D315

[kaeslin]

Hi,
I'm struggling while updating a snomD315 from version 10.1.46.16 to the current version 10.1.54.16.
Updating with 3CX management console doesn't work.
I know that it could be problematic if you miss a firmware, but I can't find older firmware updates for snomD315 for 3CX. (Only the onces from https://service.snom.com/display/wiki/Firmware+Update+Center - there i can find versions like:
- 10.1.46.16,
- 10.1.46.19,
- 10.1.51.12 and
- 10.1.54.13
but no 10.1.54.16 or something in between.)
Am I missing all this listed firmwares??? Do I have to update them manually through the webinterface of each phone?

 

[JohnS_3CX]

Hi @kaeslin

I'm a bit wary about the fact that those parameters had an older FQDN. It's making me wonder how another FQDN ended up on what should otherwise be a healthy system. The system will populate the value in various places (which you should not need to manually edit, and break continuity).

Were there any manual modification attempts made at some point that may have resulted in this?

In the interest of maintaining a healthy system, I would consider taking a full backup, and then redeploying the latest 3CX iso from scratch, using my backup just to ensure that all relevant values get populated correctly and that there are no remnants from the past that might cause unforeseen issues. This is especially important if you use a an internal local FQDN in addition to the public 3CX FQDN, which can only be changed via reinstalling and will not work correctly if modified manually.

 

[kaeslin]

OK.
The more questions I ask the more possibilities arise.

I figured out that I may missunderstood something. What I interpreted as "old fqdn" is the fully qualified name of my debian host - so its not old, it's active. So adding the DNS entry sounds not this bad anyway.
- We have the desk phones intern;
- We use the 3cx app for Windows as CTI (in-house);
- The app for iOS, Android or Windows is not used on a mobile device

So currently we are ok with it. Doing a full reset will be the last option.


Well, originally I wanted to upgrade 1 (one) snomD315 to examine the procedure stress-free. I did it in the management console.
When several phones were in the same failure state, I remembered this:
"When upgrading the firmware of a Snom IP phone, ALL phones of that model are upgraded to this firmware within 24 hours. Due to this limitation, to test out a firmware before you roll out an upgrade to all Snom phones, be sure to upload the firmware manually and test on a phone, before upgrading your production phones via the 3CX Management Console."
It is written after the 5-point-instruction where it discribes that you can choose one to many phones for the upgrade...
https://www.3cx.com/docs/manual/pbx-management/#h.pvff5z5lkb2b

I really would have been thankful for a hint about this in the managment console...

 

[JohnS_3CX]

Ok then it sounds like everything was good, apart from the fact that you were (needlessly it seems) using the FQDN as an interface, rather than the IP. So when the phones tried to reach the PBX via FQDN the firewall was not allowing hair-pin traffic hence the firmware file was unreachable. In most firewalls this is blocked automatically, hence the need for a DNS entry in your local DNS server to redirect anything contacting your FQDN to go to the internal IP rather than the public IP.

As for the Snom phones in general, the management console will not include that info, that's all in the guides as each phone manufacturer will handle it differently

 

[kaeslin]

As for the Snom phones in general, the management console will not include that info, that's all in the guides as each phone manufacturer will handle it differently

yeah, I realised

 

[JohnS_3CX]

Anyway, glad to hear that all is working well now, I will mark this one as solved then