Gigaset N870 IP Pro

[Mickel den Ouden]

A customer would like to switch to 3cx
A few months ago they bought 6 Gigaset N870 IP Pro for their current exchange.
The phones they use are the Gigaset SL750H Pro

The N870 is supported in 3cx but I still have a question about that.

Can I access the phone book of the 3cx exchange via the N870 and SL750H?

Can I easily make a Blind / Attended Transfers to a colleague with the use of an internal phonebook ?

Greetings,

Mickel

 

[Mark Kingston]

I have Gigaset N670 with a single S650H PRO phone. I can't comment on the Blind / Attended Transfer, but I can tell you that the central phone book is broken. I have checked the XML phone book created in the provisioning folder and have noticed the following:

• 3CX Contacts with only a company name generate a Gigaset contact with no name at all, the surname and name fields are left blank.
• Only Gigaset office1 field phone numbers are exported; all other number are ignored.

This has the interesting effect of producing Gigaset XML entries that are either completely empty, have a name with no numbers or a name with only one number.

This has already been mentioned in this forum post: phonebook-entries-to-custom-xml

I'm currently developing a Python script that reads the 3CX phonebook database table and generates Yealink-V43 DirectoryEntry XML, Yealink-V50 MenuItem XML, Gigaset XML (based on FAQ Nx70 - Central phone-book) and an OpenLDAP / LDIF server for OpenStage phones.

 

[leejor]

Obviously, when you are dealing with a Phonebook (database) that has many fields, and you attempt to convert that to one that has only one name and one number field (or, at least, fewer than the original), some items are bound to be"lost". So, it's not that the phonebook is "broken" as such, it's that you are trying to fit a square peg into a round hole.

Having a program that can scan every field, then, if empty, move to another, then put the contents into a new format, appears to be what you are attempting to do.

 

[Mark Kingston]

Obviously, when you are dealing with a Phonebook (database) that has many fields, and you attempt to convert that to one that has only one name and one number field (or, at least, fewer than the original), some items are bound to be"lost". So, it;s not that the phonebook is "broken" as such, it's that you are trying to fit a square peg into a round hole.

Having a program that can scan every field, then, if empty, move to another, then put the contents into a new format, appears to be what you are attempting to do.

Obviously, you miss-understand. I'm not putting any pegs in any holes. What I did way buy a supported SIP phone, provision it and give it to a user. They complained that the company phone book was corrupted and they couldn't use it. I checked the phone, the 3CX contacts and finally the 3CX generated XML phone book in the provisioning folder.

3CX supports the Gigaset N670 device and 3CX generates an XML phone book in the provisioning folder based on the 3CX contacts and provided by default via the provisioning. This XML phone book that is generated by 3CX is broken. The following is an extract of the XML generated by 3CX:

<entry surname="" name="" office1="" office2="" home1="" home2="" mobile1="" mobile2="" />
<entry surname="" name="" office1="" office2="" home1="" home2="" mobile1="" mobile2="" />
<entry surname="" name="" office1="" office2="" home1="" home2="" mobile1="" mobile2="" />
<entry surname="" name="" office1="" office2="" home1="" home2="" mobile1="" mobile2="" />
<entry surname="" name="" office1="" office2="" home1="" home2="" mobile1="" mobile2="" />
<entry surname="" name="" office1="" office2="" home1="" home2="" mobile1="" mobile2="" />
<entry surname="" name="" office1="" office2="" home1="" home2="" mobile1="" mobile2="" />
<entry surname="" name="" office1="" office2="" home1="" home2="" mobile1="" mobile2="" />
<entry surname="" name="" office1="" office2="" home1="" home2="" mobile1="" mobile2="" />
<entry surname="" name="" office1="" office2="" home1="" home2="" mobile1="" mobile2="" />
<entry surname="" name="" office1="" office2="" home1="" home2="" mobile1="" mobile2="" />
<entry surname="" name="" office1="" office2="" home1="" home2="" mobile1="" mobile2="" />

Each of the above entries has a Company Name and at least one phone number.

 

[autohaus]

Irony on: "That's not a bug, it's a feature". Irony off

Their phonebook exports only "mobile number 1" to connected devices, even if they support more like work, home, ....

There are several scripts in this forum to export all numbers to devices like Snom, .. For example:

https://www.3cx.com/community/threads/custom-phonebook-for-snom-devices-including-all-numbers.66804/