After some testing I noticed that the values inside the <number_type> tags in the example are not working as expected.Every unknown value translates to "sip".
Working values are "mobile" and "home". With "business" or "work" I had no success.
Can you please add some documentation for the <number_type> tag to your wiki?
2. Phonebook sort order
After importing the modified "snom_phonebook.xml" I noticed that the sort order of the list is by "first_name", what is very unusual for Germany.
In the old format everybody could use the preferred form because there was only the tag <name>. With two separate tags there is an option missing to set the sort order.
Because the slave entries only use the tag <first_name> like for the member alias, we have now a mix of both variants.
Best Answer
S
Sync Account
said
over 4 years ago
Hi Thomas,
about the first question I replied on the old topic.
About the sorting order: we have this parameter: http://wiki.snom.com/Settings/tbook_sort allowing you to configure the sorting order of the internal addressbook.
about the first question I replied on the old topic.
About the sorting order: we have this parameter: http://wiki.snom.com/Settings/tbook_sort allowing you to configure the sorting order of the internal addressbook.
T
Thomas Gessert
said
over 4 years ago
Hi Pietro,
I'm still trying to get this thing done. I added <tbook_sort> tag to the <phone-settings> section of the provisioning script:
Thomas Gessert
1. Tag "<number_type>"
After some testing I noticed that the values inside the <number_type> tags in the example are not working as expected.Every unknown value translates to "sip".
Working values are "mobile" and "home". With "business" or "work" I had no success.
Can you please add some documentation for the <number_type> tag to your wiki?
2. Phonebook sort order
After importing the modified "snom_phonebook.xml" I noticed that the sort order of the list is by "first_name", what is very unusual for Germany.
In the old format everybody could use the preferred form because there was only the tag <name>. With two separate tags there is an option missing to set the sort order.
Because the slave entries only use the tag <first_name> like for the member alias, we have now a mix of both variants.
Hi Thomas,
about the first question I replied on the old topic.
About the sorting order: we have this parameter: http://wiki.snom.com/Settings/tbook_sort allowing you to configure the sorting order of the internal addressbook.
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstSync Account
Hi Thomas,
about the first question I replied on the old topic.
About the sorting order: we have this parameter: http://wiki.snom.com/Settings/tbook_sort allowing you to configure the sorting order of the internal addressbook.
Thomas Gessert
Hi Pietro,
I'm still trying to get this thing done. I added <tbook_sort> tag to the <phone-settings> section of the provisioning script:
<tbook_sort perm="R">9</tbook_sort>
and checked to phone settings after reprovisioning. The entry shows like this:
"tbook_sort&: 9"
So I guess it worked. "9" should sort by <last_name> so I expected at least any effect compared to no entry / default. But no.
Is it because the 720 / 760 phones behave different?
-
LDAP and country code
-
Settings are changed when user logs on
-
USB Bluetooth compatibility for D725
-
Low volume with Plantronics Headset
-
Change Log for FW 8.8.3.32
-
Subscriptions failing after time since upgrade to 8.7.5.28
-
SNOM 870 - INBAND DTMF
-
SNOM 320 + Headset Plantronics CS540A with Snom EHS
-
Configure Settings - Set all to Read Only
-
Can't enter "+" sign in directory via WUI
See all 714 topics