These menus are provided by the Collaboration service running on Linux-based IP Office servers. For IP500 V2/V2A server, the Collaboration service is provided by an IP Office Application Server or UCM Module. The Collaboration service supported LDAP v3/ LDAPS.
The IP Office system can use LDAP user synchronization to:
Create new user (and extension) records, update existing user records and delete user records.
Obtain directory information.
Perform a combination of the above actions.
This is done by mapping LDAP fields onto IP Office user configuration fields. In addition to this field mapping, for new user creation, a ‘user provisioning rule’ (UPR) is used to define the extension type and extension template.
The information that can be managed through LDAP synchronization is:
IP Office User Field |
New |
Update |
Delete |
User Identification |
Yes |
No |
Yes |
Name |
Yes |
Yes |
Yes |
Full Name |
Yes |
Yes |
Yes |
Email |
Yes |
Yes |
Yes |
Extensions |
Yes |
Yes |
Yes |
Login Code |
Yes |
No |
No |
Voicemail Code |
Yes |
No |
No |
Mobile Twinning Number |
Yes |
Yes |
Yes |
Group Membership |
Yes |
Yes |
Yes |
User Provisioning Rule |
Yes |
No |
No |
Mapping the User Identification and Name fields is mandatory for all operations. All the other fields are optional.
Even if mapped, for each particular synchronization operation above, only those field labeled as ‘YES’ are used.
When creating a new user, if both the Extensions and User Provisioning Rule have been mapped, the extension number setting in the UPR takes priority.
An LDAP field can be mapped to several IP Office fields. For example, the same LDAP field can be mapped to the user Name and Full Name fields.
The LDAP data is not validated during synchronization. When the IP Office configuration is opened in a manual configuration tool, those fields may be flagged as errors until manually corrected. To stop this, the LDAP data should be corrected and resynchronized.
