Opened on 03/19/2015 at 10:39:19 AM

Closed on 07/31/2015 at 10:47:18 AM

Last modified on 10/08/2019 at 05:28:45 PM

#2170 closed change (fixed)

Setup central online company phonebook

Reported by: fred Assignee: fred
Priority: P3 Milestone:
Module: Office-IT Keywords:
Cc: Blocked By:
Blocking: Platform: Unknown
Ready: yes Confidential: no
Tester: Unknown Verified working: yes
Review URL(s):



With more people equipped with a work phone it woule be nice to be able to look up colleague's phone number right on your phone instead of having to open the People directory document on Google Docs.

Our DECT phone system supports several options for a centrally managed online / on-device phonebook.
These options are:

  • LDAP connection
  • XML file (static or dynamic via CGI script) on a web server

Since we currently do not have an LDAP directory, we can only use the XML option for now, which means the data on the web server must be manually updated whenever there is a staff change.

Details on the Gigaset XML phone book search protocol can be found here:

What to change

  • Setup a web server on the office network (or use one of the existing servers)
  • Create the XML file with the phonebook information
  • Change the configuration of the Gigaset DECT controller to make use of the XML phonebook
  • Inform users about the new feature

Attachments (0)

Change History (4)

comment:1 Changed on 03/19/2015 at 04:18:30 PM by fred

  • Blocked By 1961 added

I set up an nginx webserver on server01 (cologne1) which is so far being used for the WLAN controller software.
The phonebook can be reached at the URL http://phonebook.eyeo.intern/phonebook.xml

Unfortunately we this URL is not accessible from the phones right now, because they are still sitting "outside" of the office network / outside of the firewall.

So I regard the network redesign as a blocker for this issue now.

comment:2 Changed on 07/31/2015 at 10:46:44 AM by fred

  • Tester set to Unknown
  • Verified working unset

Since we now do have an LDAP server (UCS) and the LDAP approach is the better way of implementing the phonebook, I have removed the nginx setup from server1 (cologne1) again.

Instead, I have created a system user called "phonebookuser" that is used by the DECT phone controller device to conenct to the UCS openLDAP server and retrieve the information for the central phonebook.

comment:3 Changed on 07/31/2015 at 10:47:18 AM by fred

  • Blocked By 1961 removed
  • Resolution set to fixed
  • Status changed from new to closed
  • Verified working set

comment:4 Changed on 08/01/2019 at 05:19:21 AM by Salman86


Last edited on 10/08/2019 at 05:28:45 PM by kzar

Add Comment

Modify Ticket

Change Properties
as closed .
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from fred.
Note: See TracTickets for help on using tickets.