Snom 720/760 w/3CX PBX v14 Phonebook : Helpdesk platform

T

Thomas Gessert

started a topic over 4 years ago

The 3CX PBX is converting the central phonebook into a XML file named , which is then imported to the attached Snom phones via provisioning. The 3CX phonebook ist supporting several numbers per entry as the Snom phones with firmware 8.7.x do if I understand this wiki correctly: http://wiki.snom.com/Features/Mass_Deployment/Setting_Files/XML/Directory .

The problem is, that the 3CX has a hard coded conversion script, that only takes the first filled nummber of a entry, often the mobile number. I would like to create a phonebook file manually, but I have to admit that I don't understand the wiki article to how to define the master and slave entries.

Is it possible to add an extended example file with the new possibilities by chance?

Best Answer

S

Sync Account said over 4 years ago

Hi,

you are right an example is better then 1000 words:

I hope the following commented XML example will help:

<?xml version="1.0" encoding="utf-8"?>
<tbook e='2' complete="true">
  <item context="active" type='master' fav="false" mod="true">
    <!-- 
        the following tags can reside only in the master entry:
        * first_name
        * last_name
        * birthday
        * fav
    -->
    <!--
        the following tags can reside both in the master or in a member entry:
        * group
        * title
        * organisation
        * email
        * note
    -->
    <!--

        the following tags can reside only in a member entry:
        * name (this is just an alias for the number, not the person)
        * number
        * type
        * context (attribute of the 'item' tag meaning the outgoing identity)
    -->
    <name>Johnny</name>
    <!-- the number in the Master entry is used as an identifier linking referred by the Member entries -->
    <number>123</number>
    <first_name>John</first_name>
    <last_name>Doe</last_name>
    <title>Mr.</title>
  </item>
  <item context="active" context="line2" type='' fav="false" mod="true">
    <!-- Member entry of the Master entry with number 123 -->  
    <last_name>123</last_name>
    <number>003912345678</number>
    <!-- in Member Entry should be "Member_Alias" -->
    <first_name>Member_Alias</first_name>
    <number_type>sip</number_type>
    <title>Boss</title>
  </item>
  <item context="active" type='' fav="false" mod="true">
    <!-- Member entry of the Master entry with number 123 -->  
    <last_name>123</last_name>
    <number>003933812345</number>
    <!-- in Member Entry should be "Member_Alias" -->
    <first_name>Member_Alias</first_name>
    <number_type>business</number_type>
  </item>
  <item context="active" type='' fav="false" mod="true">
    <!-- Member entry of the Master entry with number 123 -->  
    <last_name>123</last_name>
    <number>003987654321</number>
    <!-- in Member Entry should be "Member_Alias" -->
    <first_name>Member_Alias</first_name>
    <number_type>cell</number_type>
  </item>
</tbook>

S

Sync Account

said over 4 years ago

Answer

Hi,

you are right an example is better then 1000 words:

I hope the following commented XML example will help:

<?xml version="1.0" encoding="utf-8"?>
<tbook e='2' complete="true">
  <item context="active" type='master' fav="false" mod="true">
    <!-- 
        the following tags can reside only in the master entry:
        * first_name
        * last_name
        * birthday
        * fav
    -->
    <!--
        the following tags can reside both in the master or in a member entry:
        * group
        * title
        * organisation
        * email
        * note
    -->
    <!--

        the following tags can reside only in a member entry:
        * name (this is just an alias for the number, not the person)
        * number
        * type
        * context (attribute of the 'item' tag meaning the outgoing identity)
    -->
    <name>Johnny</name>
    <!-- the number in the Master entry is used as an identifier linking referred by the Member entries -->
    <number>123</number>
    <first_name>John</first_name>
    <last_name>Doe</last_name>
    <title>Mr.</title>
  </item>
  <item context="active" context="line2" type='' fav="false" mod="true">
    <!-- Member entry of the Master entry with number 123 -->  
    <last_name>123</last_name>
    <number>003912345678</number>
    <!-- in Member Entry should be "Member_Alias" -->
    <first_name>Member_Alias</first_name>
    <number_type>sip</number_type>
    <title>Boss</title>
  </item>
  <item context="active" type='' fav="false" mod="true">
    <!-- Member entry of the Master entry with number 123 -->  
    <last_name>123</last_name>
    <number>003933812345</number>
    <!-- in Member Entry should be "Member_Alias" -->
    <first_name>Member_Alias</first_name>
    <number_type>business</number_type>
  </item>
  <item context="active" type='' fav="false" mod="true">
    <!-- Member entry of the Master entry with number 123 -->  
    <last_name>123</last_name>
    <number>003987654321</number>
    <!-- in Member Entry should be "Member_Alias" -->
    <first_name>Member_Alias</first_name>
    <number_type>cell</number_type>
  </item>
</tbook>

T

Thomas Gessert

said over 4 years ago

Thank you very much, that's what I was looking for!

S

Sync Account

said over 4 years ago

I just updated the wiki page, thanks for the suggestion.

T

Thomas Gessert

said over 4 years ago

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?

S

Sync Account

said over 4 years ago

Hello Thomas,

the number_type can be one of the following:

sip
mobile
business
fixed
home

I updated the wiki and the example. Thanks a lot!

P

Paolo Postai

said over 1 year ago

Hi,

it's an old thread, but i'm trying to use this information to build a centralized phonebook on a M700 DECT Multicell system.

If i generate a phonebook with this template, dect cordless, cannot show the phonebook correctly.

I have one entry each slave item (all labelled Member_Alias) plus one entry for master item, eith number as progressive index.

I tried with FW 410 B11 (Cell) FW 410 B7 (M65) and also with the latest firmware FW450B7/FW450B5)

Can you tell me if this tbook format is already supported?

C

Catalina Moritz

said over 1 year ago

Hi Paolo,

Yes, the tbook format is still supported. See a working example as well here: https://helpdesk.snom.com/support/solutions/articles/6000186162-how-to-use-the-local-central-directory-on-snom-m700-and-m300-dect-bases

Thanks

Catalina

P

Paolo Postai

said over 1 year ago

Hi Catalina

Ok. Tbook, i know.

But i need the extended version of tbook (item Master -> item Member_Alias).

If i use the second format, all phone devices (M25, M65, M85) are unable to show entries correctly.

C

Catalina Moritz

said over 1 year ago

Hi Paolo,

Ok I understand now. Unfortunately as far as I know the extended format with Master und Member is supported only on the deskphones. I opened a request to check with development if this would be possible, with ID DECT-624 . We will inform you as soon as we get a reply from development.

Thanks

Catalina