SNOM Devices Provisioning Issues

Dear all,

we ‘re trying to set VitalPBX in production, but we have got issue with provisioning SNOM devices. SNOM device are provisioned but we are getting the message HTTP Password not set and reboot required.

Any ideas?

We have provisioned successfully Yealink devices but still SNOM devices appears the above messages.

What version of VitalPBX are you running? What Phone model are you using?

The latest 4.5.

Note that HTTP Password not set have been resolved with creating a new template from scratch.

Reboot required message is our main issue. Model of SNOM device is D725.

Requested url from phone to vitalpbx provisioning

Jan 28 13:37:07.393 [WARN ] PHN: Config setup: code: 404, uri: https://vitalpbx_url:443/phoneprov/0e54c33838bc8ed8/snom725-xxxxxxxxxxxx.htm

URL accepted by PBX

https://vitalpbx_url:443/phoneprov/0e54c33838bc8ed8/snomD725-xxxxxxxxxxxx.htm

VitalPBX needs an extra D at the X position snomX750

Please look for the provisioning file on this location /var/lib/vitalpbx/provisioning, try renaming the filename as you mention

Thank you Roger for providing the location path of provisioning.

Now SNOM device is provisioned but still the message Reboot required message is here.

Can you assist further for that ?

-rw-rw-r–+ 1 www-data www-data 207880 Jan 30 11:46 snom725-xxxxxxxxxxxx.htm → Renamed file.
-rw-rw-r–+ 1 www-data www-data 207823 Jan 30 12:17 snomD725-xxxxxxxxxxxx.htm ->Auto generated.
/var/lib/vitalpbx/provisioning/provisioning_templates/0e54c33838bc8ed8$ sudo mv snomD725-xxxxxxxxxxxx.htm snom725-xxxxxxxxxxxx.htm

Every time we make a configuration change, the incorrect autogenerated file is created again. As a result, we have to manually rename the file each time.

While renaming a single file is manageable, doing so for multiple phones will not be practical. We need to find a permanent solution to prevent the incorrect file from being generated for the specific phone model (Snom D725).

Also, BLFs color code (Green for available status & RED for unavailable status/talking) is not working.

All BLFs have got grey color.

Note that BLFs color code is not fully working at Yealink devices also.

Please check & assist on my last 3 posts.

Hello Sir,

Would you be able to share the template you are using for provisioning? We would like to conduct the necessary tests.

Thank you!

Hello,we 're currently using the default provisioning templates in VitalPBX for the SNOM D725 and D735 models. However, we have noticed that the BLF key LEDs remain off at all times, despite having DSS keys assigned to BLF. The desired behaviour is a solid green LED when the extensions is free.
A blinking red LED when it is ringing
A solid red LED when it is busy.
D735_Template_03fe3e77-bb31-44f6-810b-da429031e705.txt (198.8 KB)
D725_Template_58392593-6623-481a-b8e4-8f2c7fbc40ec.txt (199.7 KB)

Please send me an email to this address roger@vitalpbx.com, I’ll provide you some instructions to patch the issue related to the provision filename