Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Scroll export button
scopecurrent
template-id0fa09813-8b86-460a-aa1d-ef450a80e9ce
quick-starttrue
add-onScroll PDF Exporter

Info

This guide explains how to import contacts and users from external databases / servers into a Wildix PBX.

WMS Version: 5.0X / 6.0X

Updated: January March 2023

Permalink: https://wildix.atlassian.net/wiki/x/0xnOAQ

...

Note that in case of WMS network, each PBX has its own Phonebooks, which must be imported separately

Image RemovedImage Added


1 - Backend settings: settings for the synchronization of PBX phonebooks with an external database / server.

...

  • LDAP
  • Active Directory (+users sign-on)
  • Lotus Domino (+users sign-on)
  • MySQL
  • MSSQL
  • Hana DBDB (import of contacts)
  • Office 365
  • Google 
  • Exchange Server 2010-2013 (supports only import of contacts)
  • Infusionsoft (import of contacts)
  • Zoho (import of users)
  • CSV file
  • Outlook (read the chapter Outlook contacts lookup and call generation)

2 - Map: in this section you can set up parameters for the correct association of the Collaboration Phonebook fields to the ones of the external database. Leave the checkboxes of only those fields which can be imported from the external database.

ID” and “Name” are required fields, since they are used as unique identifier of the contact / user.

Image RemovedImage Added

3 - Remove existing contacts which are not received from the backend: if enabled, during the next sync, existing contacts which are no longer present in the database are deleted.

...

  • Backend: select AD
  • Hostname: IP address or domain name of remote server
  • Port: specify the port (389 by default)
  • Secure connection: enable encryption during the connection
  • User: user with the rights to access to the server
  • Password: password of user to access to the server
  • Base DN: Distinguished Name of the base depends on customer’s database structure (e.g. dc=wildix,dc=local)
  • Windomain (import of users): the domain name that user name is connected to and which is required for Active Directory authentication

    Note

    Note: The Windomain field is available starting from WMS Beta WMS 5.04.2022041820220425.2.1

    In case the Windomain field is empty, the data is taken from Base DN. 


  • Full domain (import of users): the field allows to add a custom domain

    Note

    Note: The Full domain field is available starting from WMS 5.04.20220819.1.


  • Sign-on (import of users): enable the option to allow sign-on with AD credentials for imported users 

    Note

    Note: Automatic AD Single Sign-on is available. Consult Active Directory Single Sign-On for details.


  • Allow only single Sign-on (import of users): enable the option to allow only single sign-on. If the option is enabled, login of users to Collaboration with WEB password is not possible

...

In this example only those users whose category is “person” or “user” and whose status is “not disabled” from the “Map” section will be imported:


Image RemovedImage Added

Lotus Domino

Backend settings:

...

In this example only those fields from the “Map” section will be imported, which are present in “export_csv_user_10000” table and only for contacts whose type is “user”.


Image RemovedImage Added


Note

Note: It is also possible to enable connection to MSSQL instance.

Requirement: SQL Server browser must be running on MSSQL host. Please check the Microsoft documentation for detailed information on SQL browser.

Backend settings:

  • Hostname: specify MSSQL instance in the form of ip_adress_of_SQL_server\instance_name. For example, 10.100.1.231\wildixdb
  • Port: there is no need to specify the port when connecting to MSSQL instance. By default MSSQL itself listens on TCP port number 1433, but for instances the TCP port is dynamically configured
  • User and Password: enter the credentials to access to MSSQL Server
  • Database name: the name of database to be imported
  • Timeout: specify connection timeout

Image RemovedImage Added

Map

  • Check off the field that can be imported from MSSQL instance

Filter

  • Use the field to create a special select query if needed

Hana DB

Note

Note:

  • Import of contacts only.
  • The support starts from WMS5.04.20220506.5.

Backend settings:

  • Backend: select Hana DB
  • Hostname: IP address or domain name of remote server
  • Port: specify the port (30015 – default for Hana DB)
  • User: user with the rights to access to the server
  • Password: password of user to access to the server
  • Database name: name of the remote database
  • Timeout: connection timeout

...

  • Сheck off only those fields that can be imported from the remote database

Click Save and Import.

Image RemovedImage Added


Office 365

Backend settings:

...

In this way all values present in the "E-mail" field of the remote server/ database will be imported into the "E-mail" field of Collaboration Phonebook.


Image RemovedImage Added

Google

Backend settings:

...

In this way all values present in the "Address" field of the remote server/ database will be imported into the "Address" field of Collaboration Phonebook.


Image RemovedImage Added

Infusionsoft

Note

Import of contacts only. 

...

The values in the file should be separated by coma (,) and enclosed into the quotation marks (“). You can download a sample CSV file by clicking Download sample CSV when importing contacts in WMS -> Devices -> Phonebooks.

Image RemovedImage Added

Zoho

Note

Import of users only.

...