Snom D715 FW update - V20

[AWS2P]

Hi,
on V20 console I get a FW to be updated for a Snom D715, but after clicking on the Update link " (Mise à jour) " and validate " OK " on the following windows, nothing happens on phone side.

The same FW update for other Snom models on V18 PBX went like a breeze.



PBX is self Hosted AWS lightsail , phones are behind SBCs, what could i check or do ?

 

[JohnS_3CX]

Hi,

If nothing is happening, the phone is probably not able to reprovision (a required action before firmware upgrade takes place).

Can you please confirm this first?

 

[AWS2P]

Hi John,
You want I test a reprovision on extension to see what happens?

tried reprovision with no more success, only reboot button works

 

[AWS2P]

Is there anything to care about if SBC is behind a 4G router (this worked fine until now in V18).

 

[JohnS_3CX]

Is there anything to care about if SBC is behind a 4G router (this worked fine until now in V18).

Can't say for sure regarding 4G, nothing specific in mind.

Rename the extension and reprovision, see if the phone actually takes the name change to confirm provisioning is ok.
Then also reboot the phone (in case something is stuck, preventing upgrade).

 

[AWS2P]

Rename of extension didn't change a thing trying to provision , so I did a factory reset, now phone appears only in PNP phones section, and when I want to assign it to an extension Pbx displays it's already assigned to previous 109 extension.
phone stay unprovisionned

 

[AWS2P]

Deleted assigned phone to Extension 109 and tried to reassign but it does nothing on the phone.
As it seems obvious now provisioning is not reaching the phone, what else can be tried?

On PBX side every change or tries are logged fine

 

[AWS2P]

Are provisioning file going through the SBC tunnel?

I have another SBC connected to that PBX , I can try with that one to see if something change

 

[AWS2P]

Well just i wanted to switch SBC I found the phone Up to date and provisionned (so clearly it's surely it was very slow to do things?)

So if i resume , it's probably after the factory reset, phone did the FW update, and then reprovision. now i changed once more the extension name and it changed instantly on the phone.

Problem not understood but fixed. Could it be failure was due to phone not being seen part of default departement ?

Thanks John for your help.

 

[JohnS_3CX]

Are provisioning file going through the SBC tunnel?

I have another SBC connected to that PBX , I can try with that one to see if something change

No never, just a sip notify with the provisioning URL will go via SBC.

If the phone cannot reach the URL it will simply not provision.

Maybe the 4G connection was causing problems after all, or the DNS resolution was not working right - just a guess.

Were you able to upgrade the phone successfully in the end?

 

[AWS2P]

Well , I finally found it already updated latest FW and PBx registred while I was coming to change its link to 2nd SBC.

Maybe the 4G connection was causing problems after all

Agree ,That's a way if bandwith was not so good in time of trying to DL files to upgrade
For DNS it shouldn't be the case as it is set to 8.8.8.8