Snom D120 with 3CX V18

[Elvin.H]

Hi all,

We are planning to upgrade from V16 to V18 soon, and we've noticed that Snom D120 is not supported by 3CX anymore. I've tried to check it on our 3CX test server, and when tried to assign a new phone to extension, this model was not even listed. I've manually added this model to snom.ph.xml, and so could add the phone to extension, and it worked, but the phone didn't take any config from template. I've also noticed that there is snom_eol.ph.xml in the template folder where Snom D120 is listed, but couldn't assign a phone to extension using this template.

Is there any way to make working this model with V18 using templates? We have 500+ phones of this model, and they are using templates to get config without which they won't be able to work properly.

Parameters of servers on which I've tested:
Windows Server 2016 Standard
License - Professional Annual 8SC
3CX version - 18.0 (Build 418)

 

[JohnS_3CX]

Hi Elvin,

If you use PnP provisioning (available for LAN or SBC deployment) then you don't need to modify the templates.
Simply factory reset the phone, and you will be able to see it and assign it to your preferred extension.


For STUN, I'm afraid I will not be able to help - you have to provision them manually without a template.

While this was declared EOL, Snom decided to review their decision and will extend its life for at least another 18 months.
Once the new firmware is produced and tested, the D120 shall return to the 3CX supported devices and is very likely to stay for as long as the manufacturer supports it. When their support ends, it will again at some point be removed in the distant future so keep that in mind going forward.

 

[Elvin.H]

Hi John,

What will happen to phones that are already working after upgrading to V18? Will they retain config that they already have, or we will have to reconfigure all of them again? Or we have to manually configure without template only new phones?

 

[JohnS_3CX]

Hi Elvin,

Yes, they will retain their config. When upgrading to V18, existing already-provisioned phones will continue to function exactly like before on Local LAN deployments. You can still add a new one using the method I stated above for LAN or SBC provisioning.

The only thing that changes, is that you can no longer manually add a phone from the drop down list (ie. for STUN provisioning).

If Snom follows through, it will return to the supported phones and will behave just like it did before these changes came along, but I'm afraid I'm not in any position to answer that one. If you invested into many of these devices, it would be a good idea to contact Snom and learn more about their future plans so you can also be prepared for the future.

Worst case scenario, you will have to use a custom template in the future (using an older existing template as your source) but we will not be able to provide any support on that.

 

[Elvin.H]

Thanks for the explanation! I'll share the results after the upgrade.

Worst case scenario, you will have to use a custom template in the future (using an older existing template as your source) but we will not be able to provide any support on that.

Is there any manual on how to use EOL models with custom templates? I couldn't make SnomD120 to get configurations from any of templates. Tried copying templates from V16 server, using the content of snom_eol.ph.xml, adding SnomD120 manually to default template - none of this worked.

 

[JohnS_3CX]

Hi Elvin,

Except for this guide on how to correctly start creating a custom template there is NO further support available whatsoever on this matter from 3CX.

 

[RJansen]

I do not advise to use D120 with 3CX V18 due to lack of memory in the D120 they experience random reboot multiple times per day.
We find out first hand because we placed 85 D120 at a school running 3 weeks on V16 no issues at al. But when we updated to V18 al of the D120 started the random reboots. The D735 on same locatie didn have this issues. When i placed a single D120 at my own location with a V18 same reboot issues occur. After troubleshooting by snom support we got the confimation from snom that is due to memory issues and new cyphir suites in V18. Due to good relations with Snom the agreed to replace the D120 for the D712 because they where brand new. After replacement for the D712 no more reboots occured.

 

[Elvin.H]

We have finally upgrade our systems to V18 and I would like to tell about our experience with D120 models:
On V16 we used two templates of Snom - default, and custom with few differences. On V18 Snom template we added line <model ua="snomD120">Snom D120</model> which allowed us to add D120 models with default and custom templates copied from it. After upgrade, phones with custom template automatically pulled configs from the new custom template file and worked normally. Phones with default template couldn't take configuration from template for some reason (however they worked, but without some necessary configs), and he had to manually reprovision all these phone one by one, after which they worked normally too. Out Snom715 with default template also had problem which was fixed by reprovisioning.
Currently, all our SnomD120 phones are working quite stable with firmware 10.1.37.11. With firmware version 10.1.56.x (which is recommended) there we had problems with dot1x config from template - they were continuously rebooting.

 

[oidenburga]

Hi Elvin,

If you use PnP provisioning (available for LAN or SBC deployment) then you don't need to modify the templates.
Simply factory reset the phone, and you will be able to see it and assign it to your preferred extension.
View attachment 32164

For STUN, I'm afraid I will not be able to help - you have to provision them manually without a template.

While this was declared EOL, Snom decided to review their decision and will extend its life for at least another 18 months.
Once the new firmware is produced and tested, the D120 shall return to the 3CX supported devices and is very likely to stay for as long as the manufacturer supports it. When their support ends, it will again at some point be removed in the distant future so keep that in mind going forward.

Hello;
I have also problems with the D120.
i have about 30 D120 running with V18, without problems.
But i am not able to provision new ones.
They dont appear in the "Phones" Tab.

EDIT: The Problem ist that my "new" D120 have the Firmware 10.1.54.24, but 3CX only supports 10.1.54.16.
When i tried to downgrade to 10.1.54.16 the Phone says "HW rev. is not supported"
The "new" D120 have the HW Revision 2.
So, 3CX has to Update the Firmware, i guess.
https://service.snom.com/display/wiki/10.1.54.24+Release+-+D120+exclusive

 

[JohnS_3CX]

Hello,

The firmware will most likely be upgraded later, but this is mostly dependent on Snom.

They have to fully test it and provide it to us - this is the normal procedure we always follow.

For now, you are forced to use your version because it is not possible to downgrade certain hardware revisions (snom blocks it to ensure the device is not bricked)

 

[oidenburga]

Ok, i understand.
They seem to work now.

 

[ms_aqua]

Hello,

We also have Snom D120 devices here (firmware version snomD120-SIP 10.1.54.24 / hardware version 2).
With the current 3CX 18.0.5.418, we no longer have a template for ordering a new phone.


Is there any new information about the supported firmware?

Greetings

 

[JohnS_3CX]

The D120 will be returning in V18 Update 6 - but there is no word regarding new firmware. Best to contact Snom directly on this.

 

[mat_81]

I'm trying to provision a brand new D120 v2 but provisioning is not working.

Phone's firmware is latest: snomD120-SIP 10.1.54.24 and we are running latest 3CX v18 update 6. Server and phone are on the same network.

Can you help me to provision this phone? I tried setup phone manually and it works. The problem seems related to unsupported firmware version. (3CX support 10.1.54.16 but not latest 10.1.54.24).

Thanks

 

[JohnS_3CX]

I'm trying to provision a brand new D120 v2 but provisioning is not working.

Phone's firmware is latest: snomD120-SIP 10.1.54.24 and we are running latest 3CX v18 update 6. Server and phone are on the same network.

Can you help me to provision this phone? I tried setup phone manually and it works. The problem seems related to unsupported firmware version. (3CX support 10.1.54.16 but not latest 10.1.54.24).

Thanks

As above, you should contact snom about it. We were not given then newer version I'm afraid..

That aside, I don't see any reason why that would prevent you from provisioning.
Start a new thread in the snom section if you need help but read this first: https://www.3cx.com/community/threads/post-in-relevant-category.115838/