Html |
---|
<div id="fb-root"></div> <script>(function(d, s, id) { var js, fjs = d.getElementsByTagName(s)[0]; if (d.getElementById(id)) return; js = d.createElement(s); js.id = id; js.src = 'https://connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.11'; fjs.parentNode.insertBefore(js, fjs); }(document, 'script', 'facebook-jssdk'));</script> |
...
Info |
---|
This guide explains how to import contacts and users from external databases / servers into a Wildix PBX. WMS Version: 3.88/ 4.01 Updated: February 2018 Permalink: https://confluence.wildix.com/x/pQU8AQ |
Table of Contents |
---|
General info
For import of users:
- Go to WMS -> Users
- Click Import (the option is available only for admin user)
...
- LDAP
- Active Directory (+users sign-on)
- Lotus Domino (+users sign-on)
- MySQL
- MSSQL
- Office 365
- Exchange Server 2010-2013 (supports only import of contacts)
- Infusionsoft (import of contacts)
- ZohoCRM (import of users)
- CSV file
- Outlook (read the chapter Import of Contacts and Users - Admin Guide - EnglishGuide#Outlook Import)
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.
...
10 - Cancel button: close the window without saving parameters
Language choice for imported users
The following logic is applied:
- For Active Directory: use preferredLanguage value from AD, if not empty
- If empty, or if another backend is used: use the language based on the Country Code selected in WMS Settings → PBX → Language and region
- If the official language of the country is not supported as user interface language, or if the country has several official languages (e.g. Switzerland), then Language selected in Language and region settings is applied
LDAP
Backend settings:
- Backend: select LDAP
- Hostname: IP address or domain name of remote server
- Port: specify the port (389 by default)
- Secure connection (WMS 4.01): 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=wildixad,dc=local)
...
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.
Active Directory
Backend settings:
- Backend: select AD
- Hostname: IP address or domain name of remote server
- Port: specify the port (389 by default)
- Secure connection (WMS 4.01): 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)
Sign-on (import of users): enable the option to allow sign-on with AD credentials for imported users
Note Note: Starting from WMS 4.01, 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:
Lotus Domino
Backend settings:
- Backend: select Lotus Domino
- Port: port for connection to the server
- Hostname: IP address or domain name of remote server
- User: user with the rights to access to the server
- Password: password of user to access to the server
- Sign-on (import of users): enable the option to allow sign-on with Lotus Domino credentials for imported users
- 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
...
- Full Name: cn
- Login: userPrincipalName
- Extension: ipPhone
- Fax: facsimileTelephoneNumber
- Office: telephoneNumber
- Email: mail
- Mobile: mobile
- Language: preferredLanguage
Department: ou
WEB password: userPassword
SIP password: wuserPasswordSip
MySQL / MSSQL
Backend settings:
- Backend: select the backend (MySQL or MSSQL)
- Hostname: IP address or domain name of remote server
- Port: specify the port (3306 – default for MySQL / 1433 – default for MSSQL)
- 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
...
- Example: SELECT ${MAP} FROM `export_csv_user_10000` WHERE `type`="user"
- Example for query for import of of contacts from SAP Business One: select '' as empty, OCRD.CardCode, CardName, Name, Tel1, OCPR.Fax, Cellolar, E_mailL, Title from OCRD INNER JOIN OCPR ON OCRD.cardcode = OCPR.cardcode where cardtype = 'S' (More information on SAP B1 integration: https://www.wildix.com/sap-business-one/
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”.
...
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:
Map
Filter
|
Office 365
Backend settings:
- Backend: select Office 365
...
Click Available fields to see a drop-down list with all available fields which can be imported.
Map supported fields:
- businessPhones
- displayName
- givenName
- jobTitle
- mobilePhone
- officeLocation
- preferredLanguage
- surname
- userPrincipalName
- department
...
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.
Backend settings:
- Backend: select Google
...
Click Available fields to see a drop-down list with all available fields which can be imported.
Map:
- Check off only those fields that can be imported from Google contacts
...
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.
Infusionsoft
Note |
---|
Import of contacts only. Available starting from WMS version 4. |
...
Integration with Infusionsoft: https://www.wildix.com/infusionsoft/
Chrome Extension "Wildix integration to Infusionsoft": https://goo.gl/Z5YnMZ
Import of Infusionsoft contacts
...
You can now set up the Dialplan to route calls from known callers to their account managers, read the document How to automatically route calls to contact owners.
Exchange Server
Anchor | ||||
---|---|---|---|---|
|
Backend settings:
- Backend: select ExchangeServer
- Hostname: IP address or domain name of remote server
- User: user with the rights to access to the server
- Password: password of user to access to the server
...
Click Available fields to see a drop-down list with all available fields which can be imported.
Map:
- Check off only those fields that can be imported from Exchange Server
...
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.
CSV
Backend settings:
- Backend: select CSV
...
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.
Zoho CRM
Note |
---|
Import of users only. Available starting from WMS version 4. |
Read the document: Zoho CRM Products integration with Wildix PBX.
Outlook contacts lookup and call generation
Import of Outlook contacts cannot be done via WMS.
...
It is also possible to import Outlook contacts using an external Wildix utility. You can download it from Google Drive (for your Windows system type: 32 or 64 bit): LINK
macOS contacts lookup and call generation
Requirements
- WMS version starting from 4.01.43713.08
- WIService version starting from 2.9.9
- MacOS starting from High Sierra (10.13.2)
...