| Scroll export button | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| 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: April May 2024 Permalink: https://wildix.atlassian.net/wiki/x/0xnOAQ |
...
- 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 5.04.20220425.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
...
- businessPhones
- displayName
- givenName
- jobTitle
- mobilePhone
- officeLocation
- preferredLanguage
- surname
- userPrincipalName
- department
- extensionAttribute1-15
| Note |
|---|
Note: The support of the field 'extensionAttribute1-15' starts from WMS 6.01.20230123.2. It allows to sync Custom attributes. The necessary attribute needs to be entered in the Extension field. |
...
| Note |
|---|
If you need to synchronize only certain users from O365, filter them by the field "Extension". If extension is present, user is imported from O365. |
Starting from WMS v. 6.06.20240425.1, it is possible to enable user match via both extension and email. To do this, tick off the option Merge users by matching Email and Extension at the bottom:
When enabled, user import is performed based on the match of extension and email rather than ID only.
Backend settings:
- Backend: select Google
...