Under Review Snom: How can I choose the IP for getting firmware updates?

[mifritscher]

Using current v16.

I've a 2 interface setup: one for internet uplink & administration (192.168.1.0/24), one for the phones (192.168.20.0/24). The problem: for firmware updates for the phones (Snom D345), 3cx uses the ip from the first network, which is not reachable from the phones's subnet. How can I change that?

 

[ConceptsWeb]

Using current v16.

I've a 2 interface setup: one for internet uplink & administration (192.168.1.0/24), one for the phones (192.168.20.0/24). The problem: for firmware updates for the phones (Snom D345), 3cx uses the ip from the first network, which is not reachable from the phones's subnet. How can I change that?

That's your network config my friend. The 3CX sends the SIP NOTIFY to the phone and it should use the network card that is configured with a gateway.

https://www.3cx.com/blog/docs/network-configurations-supported-3cx-phone-system/

 

[mifritscher]

The phones are working completely - provisioning, incoming/outgoing calls etc. Only the firmware update URL points to the wrong address. And yes, I do need to have the phones in their own LAN - with no internet uplink.

Btw: I've a network like Segregated VoIP network in https://www.3cx.com/blog/docs/network-configurations-supported-3cx-phone-system/ . Only difference: I've no phones in Network A.

 

[JohnS_3CX]

3cx uses the ip from the first network, which is not reachable from the phones's subnet

Hi @mifritscher

So we can better understand:

1. Where did you see that 3CX tells the phone to pick up firmware from the other IP? (be specific please)

2. How did you provision the phones (detailed steps please)

 

[mifritscher]

1. : I saw this in "backup.zip"/provisioning/<random>firmware/snom/snomD345.xml:
<firmware perm="">http://192.168.1.142:5000/provisioning/hip0zsvdpi/firmware/snom/snomD345-10.1.73.16-SIP-r.bin</firmware>
-> which is the wrong interface, should be 192.168.20.251. I also have seen the wrong url biefly on the phone itself

2. factory reset, set VLAN setting manually (need to be in VLAN 20), reboot, got the provision file per dhcp option 66 -> phone configured by this file

 

[JohnS_3CX]

Understood, in this case it should simply be a matter of editing each extension, going to the provisioning tab, and changing the interface to point at 192.168.20.251 then pressing OK to save.

Next time the phone provisions, it will learn this as the correct server address, so the phones will be able to receive firmware, and also reprovision successfully without needing a reboot each time.

 

[mifritscher]

I did this In fact, without this, provisioning would not work (the phones can not be reached via the 192.168.1.0/24 net - and the phones can not reach the 3cx via the 192.168.1.0/24 net. As I said, the provisioning, phoning etc. are all working and using the right IP. Only the firmware url is wrong.

 

[JohnS_3CX]

Go to Phones page, select one of the D345 that you have already changed the interface (like we discussed above) and then click on the +Config button



Now click inside the template box that will appear, press Ctrl+F and search for firmware_status



Does this show the correct interface here?

 

[mifritscher]

in this file, the right interface is used:

    <firmware_status perm="">!http://192.168.20.251:5000/provisioning/<random>/firmware/snom/$(phone_type).xml</firmware_status>

But when I download this xml file
http://192.168.20.251:5000/provisioning/<random>/firmware/snom/snomD345.xml

I get

<firmware perm="">http://192.168.1.142:5000/provisioning/<random>/firmware/snom/snomD345-10.1.73.16-SIP-r.bin</firmware>

which is the wrong interface In fact, this file is the one I saw in the backup.

So, the main provisioning xml file has the right interface, but the firmware xml file is hardcoded to the main interface it seems. Probably one solution whould be one firmware xml file per interface.

 

[JohnS_3CX]

Hi @mifritscher

I understand perfectly what you mean now, thanks for making it clear.
We will look further into this to see if we can improve it in a future release of 3CX.

Meanwhile, we can offer a temporary solution:

1. Pick a quiet time (preferably after business hours) where you can afford some downtime
2. Go to your management console Settings >> Network
3. Under "Select Network Card Interface" make note of which interface it has now (ie.194.168.1.142)
4. Change the interface to the one the phones are in (ie. 192.168.20.251) and press OK to save
5. Go to the Phones page and select all the phones that need a firmware upgrade
6. Press +Firmware and then send the upgrade command
7. Wait for the phones to upgrade and come back online, they should be able to do it now
8. Once they are done, go back to Settings >> Network and change the interface back to what it was before and press OK to save - very important please do not forget this last step.

This is a temporary solution to allow you to complete your firmware upgrade, please try it and let us know how it went.

 

[mifritscher]

Yes, this temporary solution could work. But my temporary solution was to simply update the phones directly in their gui For most phones I did this before provisioning, because they had a way too old FW anyway.

Thank you!