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>

...

General info

...

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

...

• LDAP
• Active Directory (+users sign-on)
• Lotus Domino (+users sign-on)
• MySQL
• MSSQL
• Office 365
• Google 
• Exchange Server 2010-2013 (supports only import of contacts)
• CSV file

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.

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). 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 done:

...

• 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 (import of users): enable the option to allow sign-on with AD credentials for imported users. If the option is enabled,  "Set Password" feature for Collaboration for all users is not possible
• 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
  

...

• Login: userPrincipalName/ sAMAccountName (“Login” field in WMS -> Users)

  Note
  Note: When enabling "Allow only single sign-on" option, you can import users as: userPrincipalName as LOGIN and log in on PBX via: username@domain sAMAccountName as LOGIN and log in on PBX via: domain\username LOGIN must be the same as stored in local LDAP.

  
  

• Extension: telephoneNumber
• Office: ipPhone
• Department: department
• Disable “Language”, “WEB password” and “SIP password” as they are not used

...

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

...

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

...

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

...