3CX v16 and snom 715 results in reboot loop after upgrading to the suggested firmware 10.1.37.11

[iconline]

Hi there,

today I tried to update one of our snom 715 from firmware 8.9.3.96 to 10.1.37.11.
Unfortunately the update completed successfully, but after reprovisioning the phone ends in a reboot loop.

The following steps are happening:

1. Phone is getting IP of PC Vlan (10.1.4.88)
2. Phone is rebooting with VLAN ID 41 and QOS ID 7
3. Phone is getting IP of Voice Vlan (10.1.3.19)
4. Phone is starting Phone Application
5. Restart happens and phone proceeds with step 1

I already tried to reset the whole phone, but after provisioning with the 3CX URL the problem is happening again.

I also tried to disable LLDP and LLDP-MED on the switch ports like mentioned here:
https://www.3cx.com/community/threads/snom-760-firmware-8-9-3-57-rebooting-loop.48078/

Any ideas? Thank you in advance!

Kind Regards

 

[iconline]

Curious: I copied the default snom 10.1.37.11 template (named snom_debug.ph.xml) and set auto_reboot_on_setting_change to off (default is on). Now the phone starts and provisions like it should. What is the problem here? I can delete the Message "Reboot required" and everything works.

 

[AWS2P]

Hi,
i join you on new firmware problem, i applied this morning, and now phone stays with back light always on, and also change from features to pictos on display is not so good, IMO it was better like it was in 8.9.3.96 FW

 

[JohnS_3CX]

Hi all,

There template changes also so please ensure you are using the latest updated default template (v88271)

 

[AWS2P]

Sorry I don't remember where to check template version in use on 3CX

 

[JohnS_3CX]

It's under Settings > Templates > snom.ph.xml

 

[JohnS_3CX]

If you use a custom template, please delete the phone and add it again using the updated default template, and then please reprovision the phone to ensure everything is up to date.

 

[AWS2P]

No i use default , and version is the same in your screen copy

 

[iconline]

Template verison is 88271

 

[AWS2P]

I've done a factory reset and reassign phone to extension, after updating process, phone stay always with back light on when idle, there's a very small light decrease from normal use.

So i needed to go from phone menu to decrease manually when phone is idle to retrieve same as it was before (completly dark)

 

[JohnS_3CX]

Hi @aws2p

This is not something that changed provisioning-wise, I checked the old template and the new one.

You will have to take it up with Snom in this case. Note that the LCD does not have the option to control dim levels via template (even when comparing 8.9.3.96 to 10.1.37.11 templates)

    <!--########################################################-->
    <!--###           Phone LCD Backlight Settings           ###-->
    <!--########################################################-->
    
    <!--# The "use_backight" field specifies whether the LCD Backlight is always off, or whether the LCD Backlight turns off Automatically after a period of inactivity. Valid values are "on"==On but turns off after 20 seconds of inactivity, "off"==Always Off, "always"==Always On. The provisioning template sets the value to "on"==On but turns off after 20 seconds of inactivity.-->
    <use_backlight perm="">%%blktime%%</use_backlight>
    <dim_timer perm="">%%dimtimer%%</dim_timer>

 

[AWS2P]

ok i open a ticket on snom support

 

[iconline]

ok now we have 20 phones in reboot loop

 

[iconline]

I restored the old snapshot with template 87396, it seems to work with all the phones on 10.1.37.11, I will check completely tomorrow.

 

[dimitrybradt]

since i testdrive every new update/firmware in LAB i experienced the same issue in our testing scenario as ionline when using vlans (e.g. option 132)
there must be something to it.

template version tested and affected:
87396, 88271

phones tested:
d735, d785

downgrading the firmware doesn't give the solution as 3cx repushes the firmware to the latest as you choose to have them at this firmware version.

wkr,

 

[iconline]

So I continued testing and found out that DHCP Option 132 (Vlan Tag) and DHCP Option 133 (QOS) forces our Snom 715 and D765 to reboot.

I disabled both options on DHCP and now the phones are working with the latest firmware and template version, but are in the wrong network of course.

We configured it like mentioned here, but it seems that the new firmware can't deal with this option correctly?:
https://www.3cx.com/sip-phones/vlan-configuration/#h.so503xvxwidq

 

[dimitrybradt]

hi,
D735 on old template also affected. D785 also affected with all templates.
(on a side-note: if you remove the phone from the extention, the phone boots just fine with old config).

seems problem only occurs when it tries to check the config (option66 is configured in LAB)

Wkr,

 

[AWS2P]

also noticed reprovisionning button has no more action in CM , just restart stay active and force phone reboot.

 

[YiannisH_3CX]

Can you please describe the procedure to enable Option 132 and set it up to the phone so we can try to replicate it? Do you only enable the option in your DHCP server or do you also set it up under the phone provisioning settings as well? Also do you do any configuration in the web interface of the phone?

 

[AWS2P]

Can you test if your 3CX CM provisionning button concerning snom extensions is always working after FWU ?
mine seems to have no more effect on the phone, my phones are behind SBC