Environment :
3CX Pro 16.0.2.910
Snom M300 DECT Bases (fw 4.00 B0002)
Snom M25 Dect Handsets (fw 400.2)
We are trying to edit the central directory that gets populated in the M25 Handsets. By default 3cx publishes all the extensions in the system to this phone book. We have 21 locations, each with a m300 base and two M25 handsets. It would be very helpful if we could show just a few entries in the directory that comes up.
We found a similar post, but it is closed to further comments:
https://www.3cx.com/community/threa...om-snom-m700-dect-in-hotel-environment.65503/
We did find that the DECT templates are not in the same directory as the other phone templates. We found copies of them in both of these directories:
/var/lib/3cxpbx/Instance1/Data/Http/Templates/fxs
/var/lib/3cxpbx/Data/Http/Templates/fxs
We found that these directories both have M300 provisioning templates that refer to:
/var/lib/3cxpbx/Instance1/Data/Http/Interface/provisioning/(instance)/snom_phonebook.xml
We created a new file called snom_custom_phonebook.xml and saved it to the same directory as the original snom_phonebook.xml
We then tried editing both versions of the M300 templates files that we found to read snom_custom_phonebook.xml instead of snom_phonebook.xml
This would not push to the M300. Logging into the GUI of the M300, the central directory field would still show snom_phonebook.xml
We tried re-provisioning the M300, we tried deleting the DECT entry in the PBX and re-creating the DECT in the PBX, and re-provisioning. We could not get the M300 GUI to show anything other than snom_phonebook.xml
We tried editing the filename in the GUI, replacing snom_phonebook.xml with snom_custom_phonebook.xml, but this was overwritten each time the M300 rebooted
The only success we have had is by editing the actual snom_phonebook.xml in
/var/lib/3cxpbx/Instance1/Data/Http/Interface/provisioning/(instance)/snom_phonebook.xml
Editing this file we are able to change the directory that appears on each phone. This lasts until an extension gets added, deleted or name changed. After any of these instances, 3cx rebuilds the snom_phonebook.xml file.
At this point we are considering writing a script to overwrite snom_phonebook.xml every 20 min or something to that effect.
3CX Pro 16.0.2.910
Snom M300 DECT Bases (fw 4.00 B0002)
Snom M25 Dect Handsets (fw 400.2)
We are trying to edit the central directory that gets populated in the M25 Handsets. By default 3cx publishes all the extensions in the system to this phone book. We have 21 locations, each with a m300 base and two M25 handsets. It would be very helpful if we could show just a few entries in the directory that comes up.
We found a similar post, but it is closed to further comments:
https://www.3cx.com/community/threa...om-snom-m700-dect-in-hotel-environment.65503/
We did find that the DECT templates are not in the same directory as the other phone templates. We found copies of them in both of these directories:
/var/lib/3cxpbx/Instance1/Data/Http/Templates/fxs
/var/lib/3cxpbx/Data/Http/Templates/fxs
We found that these directories both have M300 provisioning templates that refer to:
/var/lib/3cxpbx/Instance1/Data/Http/Interface/provisioning/(instance)/snom_phonebook.xml
We created a new file called snom_custom_phonebook.xml and saved it to the same directory as the original snom_phonebook.xml
We then tried editing both versions of the M300 templates files that we found to read snom_custom_phonebook.xml instead of snom_phonebook.xml
This would not push to the M300. Logging into the GUI of the M300, the central directory field would still show snom_phonebook.xml
We tried re-provisioning the M300, we tried deleting the DECT entry in the PBX and re-creating the DECT in the PBX, and re-provisioning. We could not get the M300 GUI to show anything other than snom_phonebook.xml
We tried editing the filename in the GUI, replacing snom_phonebook.xml with snom_custom_phonebook.xml, but this was overwritten each time the M300 rebooted
The only success we have had is by editing the actual snom_phonebook.xml in
/var/lib/3cxpbx/Instance1/Data/Http/Interface/provisioning/(instance)/snom_phonebook.xml
Editing this file we are able to change the directory that appears on each phone. This lasts until an extension gets added, deleted or name changed. After any of these instances, 3cx rebuilds the snom_phonebook.xml file.
At this point we are considering writing a script to overwrite snom_phonebook.xml every 20 min or something to that effect.
