Document description
Updated:
Permalink:
General info
Import of users:
WMS Users, “Import” (button is available only for admin user)
Import of contacts:
WMS Users > Phonebooks, click “+” to add a new Phonebook. Select an existing phonebook and click “Import”.
Import is possible from:
- LDAP
- Active Directory (+users sign-on)
- Lotus Domino (+users sign-on)
- MySQL
- MSSQL
- Office 365 (+users sign-on)
- Google (+users sign-on)
- Exchange Server 2010-2013 (+users sign-on)
- CSV file
Backend settings: settings for the synchronization of Collaboration phonebooks with an external database / server
Map: set up the 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
Remove existing contacts which are not received from the backend: if enabled, during the sync, existing contacts which are no longer present in the database will be deleted.
Erase existing value if empty value is received: if enabled, during the sync, fields which are empty, will be deleted.
Filter: this section is present only for databases (MSSQL, MySQL) and LDAP server, it allows you to create a special select query.
Scheduled job: settings of the synchronization (if disabled, sync must be done manually each time)
Feedback email: enter the email of user who will receive notifications each time the scheduled job is done
Buttons below:
- Import test: make a test to check if the entered parameters are correct
- Save and Import: save the parameters and perform the import right away
- Save: save the parameters
- Cancel: close the window without saving parameters
LDAP
Backend settings:
- Backend: select LDAP
- Hostname: IP address or domain name of remote server
- Port: specify the port (389 by default)
- 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)
Map: check off only those fields that can be imported from AD
Filter:
Example:
(&(objectCategory=person)(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2)))
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
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
Map: check off only those fields that can be imported from remote database
Filter:
Example:
SELECT ${MAP} FROM `contacts_table` WHERE `type`=”customer”
in this example only those fields from the “Map” section will be imported, which are present in “contacts_table” table and only for contacts whose type is “customer”
Active Directory
Backend settings:
- Backend: select AD
- Hostname: IP address or domain name of remote server
- Port: specify the port (389 by default)
- 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: Enable the option to allow sign-on with AD credentials
Map:
- Login: sAMAccountName (“Login” field in WMS > Users)
- Extension: telephoneNumber
- Office: ipPhone
- Department: department
- Disable “Language”, “WEB password” and “SIP password” as they are not used
Filter:
Example:
(&(objectCategory=person)(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2)))
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
Office 365
Backend settings:
- Backend: select Office 365
Click on “Login” and perform login with your Windows account, after which you can select the categories of contacts that must be imported (folders):
Example:
- Contacts
- my first folder
- my second folder
Map supported fields:
businessPhones
displayName
mail
givenName
jobTitle
mobilePhone
officeLocation
preferredLanguage
surname
userPrincipalName
department
You can insert two values separated by | – in this way you can enable the import of the first value, in case it is not filled out, the second value will be imported.
Example:
Name: name | organization
In this way value present in the “name” field of the remote server / database, will be imported into the Name field of Collaboration, in case absent, value present in the “organization” field will be imported.
Lotus Domino
- 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
Filter: (&(objectClass=dominoperson))
Default MAP:
‘cn’ => ‘cn’,
‘userPrincipalName’ => ‘userPrincipalName’,
‘extenNumber’ => ‘ipPhone’,
‘facsimileTelephoneNumber’ => ‘facsimileTelephoneNumber’,
‘officeNumber’ => ‘telephoneNumber’,
‘mail’ => ‘mail’,
‘mobile’ => ‘mobile’,
‘preferredLanguage’ => ‘preferredLanguage’,
‘ou’ => ‘ou’,
‘userPassword’ => ‘userPassword’,
‘wuserPasswordSip’ => ‘wuserPasswordSip’
NOTE: For import of Users with Lotus Domino it’s possible to enable Users Sign-on option
Backend settings:
- Backend: select Google
You can set up the import of contacts with any Google account, but for import of users you must possess a special corporate (business) Google account.
Click on “Login” and perform login with your Google account, after which you can select the categories of contacts that must be imported:
- My Contacts
- Friends
- Family
- Coworkers
- Starred in Android
Map: check off only those fields that can be imported from Google contacts
You can insert two values separated by | – in this way you can enable the import of the first value, in case it is not filled out, the second value will be imported.
Example:
Name: name | organization
In this way value present in the “name” field of the remote server / database, will be imported into the Name field of Collaboration, in case absent, value present in the “organization” field will be imported.
Exchange Server
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
Map: check off only those fields that can be imported from Exchange Server
You can insert two values separated by | – in this way you can enable the import of the first value, in case it is not filled out, the second value will be imported.
Example:
Name: name | organization
In this way value present in the “name” field of the remote server / database, will be imported into the Name field of Collaboration, in case absent, value present in the “organization” field will be imported.
CSV
Backend settings:
- Backend: select CSV
It is possible to upload the file from PC or from Windows Share.
It is possible to set up the sheduled job for import from from Windows Share.
The values should be separated by coma (,) and enclosed into the quotation marks (“). You can download a sample CSV file from WMS interface by selecting CSV backend.
Outlook Import
Import of Outlook contacts cannot be done via WMS.
However, thanks to Outlook Integration (documentation: https://manuals.wildix.com/outlook-integration/) it is possible to search Outlook contacts in real time from Wildix Collaboration search field and to see the Caller ID from Outlook contacts upon receiving an incoming call.
It is also possible to import Outlook contacts using an external Wildix utility. Download it from Google Drive (for your Windows system type, 32 or 64 bit): LINK