Long Re-Provisioning Times with Snom D715 Phones on 3CX V18

[denko2k]

Hello!
Dear 3CX Fans!

We are using 3CX Version V18 Update 9 (Build 20).

While more and more users are adopting the 3CX Chrome Softphone (which deserves high praise), many of our staff members still prefer using a traditional telephone. For this, we are employing the Snom D715 with firmware version 10.1.175.0, which is approved for use with 3CX.

Our Problem:
The phones provision themselves once every 24 hours, which is generally fine. However, since one of the last 3CX-Snom updates, the re-provisioning process has taken a very long time. During this, employees are unable to use their phones for about 5 to 7 minutes. So far, I have not found a way to schedule the provisioning during night hours.

Does anyone have any ideas or tips for me?

Thank you very much!

 

[JohnS_3CX]

Hi,

Since they provision every 24 hours, if you reboot them all at midnight, then they will reprovision every day at midnight (ie. 24 hours since the time the phone last booted).

As for delay, it could potentially happen if you have thousands of contacts in the phonebook. I think the devices max out at around 2000 entries total. Beyond that, Snom Support may be able to help you troubleshoot that if you provide them with some logs.

 

[denko2k]

Hello!

Thank you for your response!
I can organize the "reboot them all at midnight" as a nice workaround.

We synchronize about 8,000 contacts with MS365. Is there a way to prevent these from being transferred to the phones?

 

[JohnS_3CX]

That might indeed be it then. Normally you don't notice it under other circumstances. I'm not aware of any way to prevent this, by default we send the entire system phonebook to the devices.

You could potentially make a custom template that removes the phonebook, however I would not recommend custom templates because we cannot provide support in case you have issues in the future, and also they do not get auto updated when we release new templates in the future which include fixes/improvements. Just something to keep in mind in case you choose to go ahead.

 

[denko2k]

Thanks. This will help!

 

[denko2k]

Thank you for your help. We have decided on the custom template. We have adjusted section

<!--########################################################-->
<!--###               Phonebook Settings                 ###-->
<!--########################################################-->


    <!--# The "url" paramater of the "file" field specifies the filename which contains the Company Directory (3CXPS System-Wide Phonebook). The provisioning template sets this value to "%%PROVLINK%%/snom_phonebook.xml", which is path for the phonebook generated by 3CXPS in Snom compatible format.-->


    <file url="https://XY-URL_phonebook.xml"/>

and referred to an empty XML file.

We are aware of the issue with unsupported templates and the updates as well.

This also has another reason: The Snom D715 models, which are quite good in hardware execution but become quite sluggish with 3219 phonebook entries. Without the phonebook, the operation of the Snoms runs much smoother.

This has solved our problem. Many thanks to 3CX. We hope that the Snom D715 will be supported for a long time