Solved Snom D385/D785 directory empty after reboot

[Dennis The Menace]

Dear List,

After having updated our Snom D385/D785 phones to the newest 3CX recommended firmware 10.1.54.13, on all phones, the directory shows <empty>.
After Maintenance -> Synchronize Settings, the directory is correctly loaded.
However after the next reboot/poweron, the directory is empty again.
PS: Everything worked correctly before.

Thanks for any help.
Dennis

 

[coreybrett81]

I have the same issue with the D735 and D717.

 

[coreybrett81]

This is causing an issue with the ringtones as well. Anyone else having trouble?

 

[Raumpatrouille]

Same here:
After updating to Snom Firmware V. 10.1.54.13 the phone book is empty.
Another workaround: If hotdesking is used, log out and log in again.

@StefanW Can 3CX verify that?
Snom is informed.

 

[JohnS_3CX]

Thanks for reporting, we will investigate this

 

[nitrox]

+1

 

[nitrox]

i discovered one problem more. If you try to call via click_dial number with "+" sign on top it doesn't start any call from snom. No problem if i try from the same extension on the web app or iOS/android app. So it is something related to the snom.
Some of you have discovered the same problem of mine?

 

[JohnS_3CX]

Hi @nitrox

Are you referring to CSTA dialling? (Webclient, chose phone from drop down menu, and make a call using + in front)

 

[nitrox]

yes. The web client can make call with + in front but if i choose snom phone on the drop down menu and try to call via CSTA the snom doesn't start the call. This is what the snom write in its log:

Jun 25 15:56:00.636 [FATAL ] CSTA: Fail to create sip contact with +393461234567

ps. the number doesn't exist i have changed it because i don't want to write my work number in this forum (of course).

 

[AWS2P]

Same here on Snom D725 and D785 since firmware applyied phonebook is empty.

 

[AWS2P]

 

[JohnS_3CX]

Thanks, I can replicate it here too. We have raised the matter with Snom so it can be addressed

 

[David Liddle]

An interesting thing occurred on our system. On Wednesday, I updated the following models on our system: Snom D375, D315, and 715. Yesterday, one of our receptionists reported that the phonebook was no longer available. I reset and reprovisioned my phone, a D315, to no effect. Today, I confirmed that it affected these models and not others (Snom 320 and 710). After I asked the same receptionist to confirm that the latter models by her still functioned correctly, she reported that they all have the directory. After reprovisioning my phone again, the directory is available. This behavior seems a little bizarre to me.

 

[JohnS_3CX]

@David Liddle indeed this has been replicated and reported to Snom, we expect a fix so we can release it

 

[nitrox]

The click to call and the address book are two important features of the snom/pbx. I am wondering if the firmware are really tested before deployment by someone of 3cx/snom or we are the testers of the firmware. These is really important to know if someone want to update the phone when the release is out for deployment.

 

[AWS2P]

Other thing I noticed today don't know if related to new firmware but , each 24 hours is there a complete reboot of the phone expected or only a provisioning because my D785 did alone a complete reboot in middle of morning?

 

[nitrox]

Other thing I noticed today don't know if related to new firmware but , each 24 hours is there a complete reboot of the phone expected or only a provisioning because my D785 did alone a complete reboot in middle of morning?

it should provisioning and not reboot as always but we never know what this last firmware has changed.

 

[AWS2P]

in all the case I don't remember having phone reboot alone before this firmware upgrade.

 

[coreybrett81]

Is firmware automatically upgraded on phones?

I manually triggered the firmware update on a few phones, to make sure there wasn't any issues with it.

The next morning, about 75% of all my phones had been updated.

 

[AWS2P]

Not sure but in my memory this is something needing to be manually done . Perhaps if automatic update is enabled on PBX then it applies alone ?