# Adding and Editing Peer Servers

The Peer Server Details page allows you to add and edit MiCollab Client Service and external peer servers.

If you are adding an external server to enable federation, the customer must install the IM server and deploy the XMPP gateway provided with the server to federate with MiCollab Client Service. Refer to the IM server documentation for instructions about configuring federation.

#### To add or edit a peer server:

1. Configure the server Settings.

   - Select the Peer Type. Options include MiCollab Client Service and External.

   - Type a Description for the peer server. The Description is limited to 64 characters in length and must contain alpha-numeric characters, dashes, and/or spaces.

   - (MiCollab Client Services only) Type the hostname for the MiCollab Client Service. The value entered in the hostname field must match the value used for generating the web server certificate on the MiCollab Client Service to which the MiCollab Client Service is being peered.

   - (MiCollab Client Services only) The Peer enterprise ID field defines which enterprise from the peered MiCollab Client Service will be synchronized with the selected Enterprise on the local MiCollab Client Service. The Enterprise ID is configured on the Enterprise tab. Do one of the following to add the Enterprise ID:

   - Click the Select Enterprise link, and then select the correct Enterprise from the list.

   - Type the Enterprise ID in the box. The Enterprise ID:

   - is limited to 4-32 characters in length.

   - must contain alpha-numeric characters (dashes included).

   - cannot contain spaces, vertical bars, commas, semicolons, or colons ( | , ; : ).

   NOTE: The Enterprise domain should be unique for each MiCollab Client Service peer. Mitel suggests using the site location or Enterprise ID (configured on the Enterprise Details page) as part of the Enterprise domain (for example, Phoenix.xyzcompany.com, where Phoenix is the Enterprise ID).

   - (MiCollab Client Services only) If required, type the Peer Dialing Prefix for the server. The Peer Dialing Prefix is only required for PBX-to-PBX calls where the networked PBXs are not configured for transparent extension dialing. The value you enter here corresponds with the dialing prefix (not including the outgoing call digit) that PBX users must press to dial an extension on the networked PBX. The Peer Dialing Prefix is limited to 20 characters in length.
     Note: No validation is performed on the characters entered for the Peer Dialing prefix. The administrator should enter what is set up in the PBXs for calling from one PBX to another. The Peer Dialing prefix can start with a hyphen (-) character. Doing so informs the MiCollab Client Service to not append the outgoing prefix digit defined under the PBX node settings when making calls to extensions on the PBXs associated with the peered MiCollab Client Service.

2. If you are adding a new peer server, click Create.
3. (External Servers only) Configure the Synchronization Settings for the server.

   1. (Optional) Schedule automatic synchronizations between MiCollab Client and the AD/LDAP databases by specifying the following:

   - 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 Add to add an AD/LDAP synchronizer and configure the settings.

   3. Click Sync Now to synchronize the AD/LDAP directory with the Unified Communications server. After you click Sync Now, the peer server contacts are imported to the MiCollab Client Service database (visible from the Corporate Directory Tab) and federation with these contacts is automatically enabled.

4. Click Save.

After you create peer servers, you can edit the associated fields at any time.

Peering between different enterprises on the same MiCollab Client Service is supported.

Related Topics:

Peering Tab

Federation Tab

Provisioning MiCollab Client