# How Entries are Paired

The Reconcile Wizard pairs up entries in the MiCollab database with entries in the MiVoice Business databases that have matching data for the following:

- User Information (Directory Number, Login ID, and Email Address)

- Network Elements

- Locations

- Department Names

- Template Names, and

- Role Names.

It pairs MiCollab with MiVoice Business users

- firstly, by phone directory numbers (and PRG/MGUG group membership if available) and

- secondly, upon the user's login ID and e-mail address.

If a MiCollab user is paired with one or more MiVoice Business users, the reconcile operation merges them into a single entry.

The following data is not paired:

- Single-line devices

- Line Appearance Keys

- Local-only devices

- Phones without users (example, application ports)

The following table summarizes how the wizard automatically pairs data entries:

Status of entries | Reconcile Operation
MiCollab and MiVoice Business users have same directory numbers. | The user entries are collapsed into a single user with one or more phones. The MiCollab user information is applied to the user. If there are multiple MiVoice Business users, they will be either collapsed or deleted. The end result being a single user with the MiCollab user information and the phones from the MiVoice Business entries.
MiVoice Business users that are not paired with a MiCollab user are not automatically assigned MiCollab Client service. | In previous MiCollab releases, when a user was created the user was automatically assigned MiCollab Client service. However, in MiCollab 7.0 and later, when MiVoice Business users are synchronized with the MiCollab database via System Data Synchronization, if those MiVoice Business users are not paired with a MiCollab user, then they are not automatically assigned with MiCollab Client service.
Matching MiCollab and MiVoice Business entries have different services for the user. | If a MiCollab user who is assigned application services (such as MiCollab Client or NuPoint) gets paired with a MiVoice Business user who also has services (such as a PRG or MDUG) then the reconciled user receives both the MiCollab services and the MiVoice Business services. Note: Exception MiCollab doesn't display MiVB embedded voice mail services
Duplicate non-default Template Names | The wizard renames the MiVoice Business template as follows: <Template Name> becomes <Template Name>(x). Where (x) is a number starting with 1. For example, in a scenario where there are more than two servers in the network and they all have a non-default template with the same name, the resulting template names would be: “Example Template Name” (for the template that was on the first node in the sharing network) "Example Template Name (1)” “Example Template Name (2)”
Reconciling Duplicate Departments or Locations | The wizard merges the MiCollab and MiVoice Business departments such that only one department with that name will exist. When departments are merged, the department number and description are retained in the MiCollab database If the MiCollab and MiVoice Business both have a location with the same name, then the wizard merges these two locations into a single location.
Same role name referring to a different template | The wizard renames the MiVoice Business role as follows:: <Role Name> becomes <Role Name> (x)”, where (x) is a number starting with ‘1’.
MiCollab and MiVoice Business user match on a directory number (DN) and the MiVoice Business user has additional DNs. | The wizard pairs the MiCollab and MiVoice Business users based on the matching DN. The merged user uses the MiCollab user information. The additional MiVoice Business user DNs are also included with the merged user.
MiCollab user has multiple DNs, one or more of which match the DNs of a MiVoice Business user. | The wizard merges the MiCollab and MiVoice Business users. The merged user uses the MiCollab user information. If there are multiple MiVoice Business users, they will be either collapsed or deleted. The end result being a single user with the MiCollab user information and the phones from the MiVoice Business entries.
MiCollab user has DNs that match to MiVoice Business DNs that are not assigned to user s | MiVoice Business DNs that are not assigned to users that are matched to a MiCollab user are merged with the MiCollab user.
Teldir entries are updated when MiVoice Business users are merged with MiCollab users | The wizard updates the MiVoice Business telephone directory entries when a MiVoice Business user is merged with a MiCollab user.
Non-sharing network elements that are either programmed on the MiCollab system but not programmed in the MiVoice Business sharing network, or programmed in the network but their data is not being shared with any other elements. | Non-sharing network elements will not support Flow Through Provisioning after the reconcile. You must add the missing elements to the sharing network from the System Administration tool of one of the member MiVoice Business systems, and then start the Reconcile Wizard again.
Network elements that need to be reconciled with this network element. |
External and Other-PBX Phones | The wizard does not attempt to pair up the DNs for these phones with DNs on the MiVoice Business. Instead, these phones are treated as MiCollab services that are not shared across the network.