Synchronization with LDAP/AD
This module is designed for bidirectional synchronization of employee account data with MikoPBX. The data source is either an Active Directory or LDAP server.
When a new employee is created in the domain, they will automatically be uploaded into MikoPBX, with an available internal number assigned to them. The information about the number will then be sent back to the domain and recorded in the employee's profile. The same will happen with their mobile phone number and photograph. As always, the setup is extremely straightforward.
Synchronization Parameters
For each AD/LDAP server, you can specify synchronization settings, departmental filters, or create a custom filter for complex filtering logic.
Account Attributes
Next, you need to correctly configure the attributes for synchronizing account data.
Initial Synchronization
During the initial synchronization, the system will match the existing MikoPBX account data with the data obtained from the domain. The following fields are used for matching:
Email address
Employee name
Mobile phone
Internal phone
Testing and Launch
Before enabling automatic synchronization, it is recommended to test the correctness of the specified attributes by clicking the Run request button.
If all parameters are correctly specified, you will see a list of employees with attributes from the domain. This is a safe request and will not result in changes to the system.
Next Steps
After testing, you can initiate manual or automatic data synchronization.
In the columns "status" and "updated", you can track the current synchronization process.
As of now, the removal of an employee from the domain will not lead to their automatic removal from MikoPBX. The account will be retained until manually deleted by a MikoPBX administrator. This is because there may be various complex call routing scenarios where it's not feasible to simply remove an employee from the call route without replacing them with someone else.
Last updated
