Synchronization Tab

 NOTE: Some configuration fields are disabled if MiCollab Client is running in MiCollab-integrated mode.

Using synchronization, you can quickly populate the MiCollab Client accounts list based on your existing PBX node, Active Directory (AD), or Lightweight Directory Access Protocol (LDAP) corporate directory. In addition, you can schedule periodic synchronizations to keep your MiCollab Client accounts and corporate directory synchronized.

From the Synchronization tab, select the Enterprise from the list box, and then select a synchronization type.

After you select a synchronizer, you can complete the following tasks:

• Perform a manual synchronization.

  To perform a manual synchronization:

  Click Sync Now. The MiCollab Client accounts database is synchronized with the AD/LDAP directory or the PBX Node database.

• Schedule a day and time to perform automatic synchronizations.

  Schedule automatic synchronizations for the MiCollab Client accounts database and the AD/LDAP directory or the PBX node database.

  To schedule automatic synchronizations:

  1. Specify the following to schedule the synchronization:

  • The frequency (in days) the synchronization should occur.
  • The hour the synchronization should start.
  • The minute the synchronization should start.
  • Whether the synchronization should occur in the AM or PM.

  2. Click Apply to save the information, or click Reset to clear your changes.

• For Enterprises configured for AD/LDAP synchronizers only, you can also do the following:
• Click Add to add an AD/LDAP synchronizer and configure the settings.
• Click an AD/LDAP Synchronizer link to edit it.
• Delete an AD/LDAP synchronizer. When you delete an AD/LDAP synchronizer, all the accounts associated with the synchronizer are also deleted.

  To delete an AD/LDAP synchronizer:

  1. Select the AD/LDAP synchronizer you want to delete from the list.

  2. Click the Delete link. A dialog box appears prompting you to confirm the deletion.

  3. Click OK to delete the synchronizer, or click Cancel to cancel the deletion.

• Check the status of the last AD/LDAP synchronization.

 NOTE: For synchronization failures, refer to the Synchronization Error Messages topic.

• For Enterprises configured for PBX Node synchronizers only, you can also do the following:
• Check the status of the last PBX Node synchronization on the PBX Nodes tab.
• View PBX Node synchronization details on the PBX Node Details page.
• Specify a feature profile to use for all accounts created during the PBX node synchronization.

   NOTE: Before specifying a Feature Profile, refer to the Licensed Features and Synchronization topic.

  To specify the feature profile to use for PBX node accounts:

  1. Create the feature profile for the PBX node on the Features tab.

  2. On the Synchronization tab, select the appropriate feature profile from the list box.

  3. Click Apply to save the information, or click Reset to clear your changes.

• Enable or disable the Synchronize Dynamic Extensions only option.

  This option specifies if new accounts are created or not during the synchronization process. By default, this option is disabled. Options include:

  • Disabled: When this option is disabled (not selected) the synchronization process pulls data (including Dynamic Extension information) from the PBX nodes and creates MiCollab Client accounts.
  • Enabled: When this option is enabled (selected) the synchronization process does not create new accounts. It does however, pull Dynamic Extension data from the PBX node to update existing MiCollab Client accounts. When you enable this option, you must manually create the accounts first.

 NOTE: The following are valid character ranges for LDAP synch. Anything outside of these is invalid character for LDAP synch:
0x9, 0xA, 0xD, 0x20 to 0xD7FF, 0xE000 to 0xFFFD, 0x10000 to 0x10FFFF

Synchronization Rules for MiVoice Business:

Below are the synchronization rules for MiVoice Business.
(On MiVoice Business, PRG stands for - Personal Ring Group. MDUG - stands for Multi Device User group):

1. Starting from MiCollab Client 5.1, user can have either a Minet Softphone or a SIP softphone, but not both.
2. The MiCollab Client will recognize numbers on MiVoice Business with device type as 'App Server Port' or '5020 IP' with MAC address starting with A1:21:00 as Minet Softphone. Numbers on MiVoice Business with device type as 'MiCollab Client Endpoint' will be recognized as 'UC Endpoint', if user does not have a Minet Softphone. If user has both number types, then MiCollab Client will assign the Minet Softphone as User softphone.
3. If user has deskphone and softphone , and no PRG or MDUG on MiVoice Business, then the first name, last name and department fields in MiVoice Business has to match exactly (including case) for the deskphone and softphone for MiCollab Client PBX sync to associate the two phones for same user. This restriction does not apply if user has PRG or MDUG on MiVoice Business and the deskphone and softphone are part of the PRG.
4. When user has PRG or MDUG on MiVoice Business, the first name,last name and department of PRG pilot is used to identify the account in MiCollab Client. The PRG pilot will be assigned as user deskphone or as user softphone.
5. If user has multiple deskphones or SIP phones or Minet softphones, then PRG or MDUG has to be defined in MiVoice Business and all the user devices have to be part of the group for MiCollab Client to pull in all the phone numbers for that user.
6. When a phone number is deleted in MiVoice Business then it will still show up in MiCollab Client for that account when one or more of the following is true:
   1. The number was manually added in MiCollab Client by the administrator.
   2. Some of the user's dynamic statuses are still pointing to that number for call routing purposes.

To remove the number from MiCollab Client database, the user has to login to the desktop client and update the dynamic statuses pointing to the deleted number. User has to update the Make Call from setting within each status to point to a different number. Once all the references are removed, the user can delete the number from MiCollab Client database.

 NOTE: Rule 6 also applies to MiVoice Office 250.                   

Related Topics:

Adding and Editing AD/LDAP Synchronizers

Common AD Field Mappings

Features Tab

Provisioning MiCollab Client