Page Comparison

<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>

...

 <div class="lang-box-pdf">
	<div>
		<div class="google-lang">
			<div id="google_translate_element">
			</div>
			<script type="text/javascript">
					function googleTranslateElementInit() {
						new google.translate.TranslateElement({pageLanguage: 'en', includedLanguages: 'de,es,fr,it,nl', autoDisplay: false}, 'google_translate_element');
						}
			</script>
			<script type="text/javascript" src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script>
		</div>
		
		<div class="pdf-button">
			<a href="https://confluence.wildix.com/spaces/flyingpdf/pdfpageexport.action?pageId=20710821" alt="Convert to .pdf" title="Convert to .pdf"><img src="https://confluence.wildix.com/download/attachments/14549012/pdf-button-download-wildix-documentation.png"></a>
		</div>
	</div>
</div>

General info

Import For import of users:

• Go to WMS

...

• -> Users
• Click Import (the option is available only for admin user)

Import For import of contacts:

• Go to WMS -> Users -> Phonebooks

...

• Select  an existing phonebook or click + to add a new Phonebook 
• Click Import

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

Import of contacts and users 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)
• Google 
• Exchange Server 2010-2013 (+users sign-onsupports only import of contacts)
• CSV file
  

Backend settings: settings for the synchronization of Collaboration phonebooks with an external database / server

Map: set up the 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.

3 - 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.

4 - 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 5 - Filter (available for LDAP, AD, Lotus Domino, MySQL/ MSSQL): this section allows you to create a special select query.

6 - Scheduled job: settings of the synchronization (if disabled, the sync must be done manually each time)
Feedback email: . Set the period for performing the sync (1/ 2/ 6/ 12/ 24 hours) and enter the email of a user who will receive notifications each time the scheduled job is doneButtons below:

7 - Import

...

test button : make a test to check if the entered parameters are correct

8 - Save and Import button: save the parameters and perform the import right away

9 - Save button: save the parameters

10 - Cancel button: 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=wildixwildixad,dc=local)

Map: check

• 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 In this example only those users whose category is “person” or “user” “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  enable the option to allow sign-on with AD credentials 
• Allow only single Sign-on: Add additional checkbox "Allow only Sign-on" and disable login for internal users(except admin) in case of this option is enabled

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

single sign-on via AD. Now you can import users as:
1. userPrincipalName as LOGIN and log in on PBX via: username@domain
2. sAMAccountName as LOGIN and log in on PBX via: domain\username

Filter:

• Example:

...

• (&(objectCategory=person)(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2)))

in 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“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: enable the option to allow sign-on with Lotus Domino credentials 
• Allow only single Sign-on:

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

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:

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

Filter:

• Example: SELECT ${MAP} FROM `export_csv_user_10000` WHERE `type`="user" 

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”.

Office 365

Backend settings:

• Backend: select Office 365

Click on “Login” Check off Access to organizational contacts to provide access for import of organizational contacts.

Click Login and perform login with your Windows account, after which you can select the categories of contacts that must be imported (folders). For example:Example:

• Organizational contacts
• Contacts

...

Click Available fields to see a drop-down list with all available fields which can be imported.

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

For example:

• Name: name |

...

• company

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” “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))

...

Google

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” 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

Click Available fields to see a drop-down list with all available fields which can be imported.

Map: check

• 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

For example:

• Name: name | organization

In this way value present in the “name” “Name” field of the remote server / server  database , will be imported into the "Name" field of Collaboration, in case absent, value present in the “organization” “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

• 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

For example:

• Name: name |

...

• companyName

In this way value present in the “name” “name” field of the remote server / database, will be imported into the "Name" field of Collaboration, in case absent, value present in the “organization” “Company” field will be imported.

CSV

Backend settings:

• Backend: select CSV

Map:

• Check off the fields that can be imported from a CSV

...

• file

Click Choose File to upload the a CSV file from your PC or from Windows Share.It is possible to set up the sheduled job for import from from Windows Share.

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

Outlook Import

Import of Outlook contacts cannot be done via WMS.

However, thanks to Outlook Integration (documentation: https://manuals.wildix.com/outlook-integration/) it check Outlook integration for Microsoft Windows documentation) 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 You can download it from Google Drive (for your Windows system type, : 32 or 64 bit): LINK

<div class="fb-like" data-href="https://confluence.wildix.com/x/pQU8AQ" data-layout="button_count" data-action="recommend" data-size="large" data-show-faces="true" data-share="true"></div>

...