# Conditions

## General

- You can apply the default set of attribute mappings to a connection by leaving the Use default attribute mappings box checked, or you can clear the box and assign custom mapping attributes to a connection.

- At minimum, directory server attributes must be set for the User ID, Distinguished Name, First Name, and Last Name fields. All other fields can have blank directory server attributes, which allows the fields to remain blank or to be populated from a template.

- Customized attribute fields are validated when the connection runs. If you enter an attribute incorrectly, the operations will likely fail. The failed operations are listed as errors in the summary and are sent to in the detained updates queue.

- If you change an attribute mapping on MiCollab after the initial full synchronization, another full synchronization is required because regular scheduled synchronizations only detect and apply deltas from the directory service. The directory service is unaware of the change on MiCollab until you perform a full synchronization. A warning message is displayed if you change an attribute on MiCollab after the initial sync. The warning indicates that another full synchronization is required apply the change to the directory server.

- MiCollab supports UTF-8 format for the directory service attributes with the following exceptions: Email address, Department, and Location. These field attributes do not support UTF-8 format. This limitation applies to the MiVoice Business system also. If one of these fields receives UTF-8 data, the operation fails and is sent to the deferred updates queue.

- If First Name, Last Name, or Department attributes are updated for a user, the updated values will get reflected after 15 minutes in the client call window. It is recommended for users to wait for 15 minutes or restart the system to display the updated values.

## Specific Conditions Relating to Users

Directory service attributes that are mapped to user service data must

- be unique

- belong to the user object class - different objects cannot be described by the same set of attributes; otherwise, updates will fail.

- programmable from a user interface such as the Active Directory Users and Computers console.

- be single-valued (not a list of comma-separated values)

- be available (when you select an LDAP attribute to map to user service data, ensure that the attribute in use for some other purpose).

## Specific Conditions Relating to Contacts

The attribute mappings of the IDS connection must be set to match the MiVoice 5000 directory schema. The MiVoice 5000 can have different attributes for internal (people) and external (contact) records. Therefore, to support the synchronization of both types of records, the internal and external record attribute tables on the MiVoice 5000 LDAP directory service must match each other for the MiCollab IDS connection to retrieve both types of records.

The MiVoice 5000 and MiVoice 5000 Manager (AM7450) allow you to configure custom attributes in the directory schema in order to provide additional custom information for external records. On the MiVoice 5000 you perform the configuration from the Telephony Service -> Subscribers -> Directory-> Parameters ->Customization menu. On the AM7450 you perform the configuration from the Telephony-> Directory Management-> Customization menu. The custom attributes are named attr1, attr2, attr3, and so forth. MiCollab IDS support mappings to these custom attributes.

## Specific Conditions Relating to Mobile Phones

If the Mobile Phone Directory Number field is mapped in the Attribute Mappings table, when a new user is created with a mobile number in Active Directory, the mobile number is populated into the External Hot Desk User (EHDU) number in MiVoice Business. It is also sent to MiCollab Client server (UCA) and added to the user's phones list. The user will see this number when they manage their dynamic status and other users will see that number in the corporate directory. The EHDU number is added to the following interfaces:

- User and Services application in MiCollab.

- Phone service in MiVoice Business.

- User's phone service list as presented in the UCA management pages

- End user's account information.

- MiCollab Client corporate directory as presented to other users.

When the mobile number for an existing user is updated in Active Directory, then on the next scheduled IDS synchronization cycle, the mobile number change is detected and the new mobile number is shown in bold in the detained queue. If the IDS connection is configured to apply updates immediately (defer all updates is not checked) then the EHDU number will be updated immediately in the interfaces listed above; if not, the EHDU is updated after you save the update in the 'Manage Detained Queue' tool.

Note the following:

- DID numbers and Directory numbers are not updated. Only mobile numbers are updated.

- Whenever you update an Active Directory user (any attribute) if there is a mobile number programmed in Active Directory the number will be synchronized into MiCollab, possibly over-writing end user's provided EHDU number. To avoid overwriting a user's EHDU number, review the change in 'Manage detained queue' and if necessary choose not to apply the change.

- If you do not want mobile numbers that are provisioned in Active Directory to be applied to the MiCollab solution, remove the mobile number mapping from the IDS connection.

- If the EHDU was published, it remains published. If it was not published, it remains unpublished.

- If other fields are also updated in Active Directory at the same time (such as the user's first or last name) these updates are also applied.

- It is not necessary to perform a PBX sync in order for an update to be sent to the MiVoice Business or MiCollab Client.

- The same number format supported in the initial create is supported in the subsequent update.

- To synchronize existing users mobile numbers with Active Directory, check the 'Re-initialize on next cycle' option in the IDS connection and re-run the sync.

- The correct MiVoice Business system username and password must be provisioned in the Network Elements tab in the User and Services application.