EasyUC
English
Aurora

Choose appearance

4.8.7

EasyUC for Cisco

Presence Sync from start to finish

End-to-end checklist from the Entra app through profile, mapping and dry run to the check in Presence Live.

EasyUC · Version 4.8.7

In EasyUC: Manager → Module → Presence Sync; Presence Sync → Presence profiles

What it is for

This checklist takes you through the entire setup of the Jabber variant in a fixed order: preparation at Microsoft and Cisco, activating the module, creating the profile, checking the mapping, dry run, going live and the check in the log. Each block ends with a check. Continue only when it has been passed.

The details on fields and messages are in the linked chapters. For the Webex App a separate procedure applies, described in the chapter on presence with Cisco Webex.

Prerequisites

  • Access to the EasyUC Manager to switch on the Presence Sync module.
  • An EasyUC account with the permissions ROLE_APP_PRESENCE_WORKSPACE, ROLE_APP_PRESENCE_TENANTS_EDIT and ROLE_APP_PRESENCE_SYNC_EDIT, or an administrator account.
  • In Microsoft Entra, the right to create app registrations and to grant admin consent for application permissions.
  • In the CUCM, the right to create an application user and an end user and to assign roles.
  • A CUCM connection in EasyUC whose call monitoring covers all devices.
  • Two test users who exist in Microsoft and in the CUCM and carry a common identifier, for example the same e-mail address.
  • The appliance reaches graph.microsoft.com and login.microsoftonline.com over HTTPS as well as the presence web service of IM and Presence.

Step by step: prepare Microsoft Entra

  1. Open the Microsoft Entra admin center and create a new registration under the app registrations, for example with the name "EasyUC Presence".
  2. Note the directory ID (tenant ID) and the application ID (client ID).
  3. Create a client secret and note its value and its expiry date.
  4. Under the API permissions for Microsoft Graph, add the application permissions User.Read.All, Presence.Read.All and Presence.ReadWrite.All.
  5. Grant admin consent for the tenant.
  6. Check: all three permissions show the status "Granted".

Step by step: prepare the Cisco side

  1. In EasyUC, check at the CUCM connection that call monitoring is switched on and observes all devices. This is described in the chapter on call monitoring of the CUCM connection.
  2. In the CUCM, create an application user for the presence web service and give it the role Admin-3rd Party API.
  3. Create a dedicated end user as observer who may see the presence status of the Jabber users concerned. Do not use a personal account for this.
  4. Note the address of the presence web service on IM and Presence (HTTPS with the path /presence-service) and the presence domain of the Jabber addresses.
  5. If IM and Presence uses a certificate from an internal certificate authority, have its CA certificate ready for the EasyUC server.
  6. Check: the presence web service is reachable from the appliance over HTTPS.

Step by step: activate the module and create the profile

  1. Open the EasyUC Manager and switch on the Presence Sync module under Module (modules). The Manager starts the presence service.
  2. Wait until the Manager shows the service as ready.
  3. Log in to EasyUC and select the Presence Sync workspace at the top.
  4. Click Add presence profile and in step 1 enter profile name, tenant ID, client ID and client secret.
  5. In step 2, select CUCM / Jabber and enter the Cisco access: CUCM user directory and the details for Cisco IM and Presence.
  6. In step 3, select Kennzeichen vergleichen (compare identifiers) and the two fields that carry the same value in Microsoft and in the CUCM.
  7. Click Einrichtung speichern (save setup).
  8. Check: Microsoft Graph testen (test Microsoft Graph) shows Graph geprüft (Graph checked), and Cisco-Verbindung testen (test Cisco connection) reports no errors.

Step by step: check the mapping

  1. In step 3 of the profile, click Zuordnung prüfen (check mapping).
  2. Compare Microsoft-Benutzer (Microsoft users) and Cisco-Benutzer (Cisco users) with the expected figures.
  3. Filter by Nicht gefunden (not found). If the identifier is missing for these users in one of the directories, maintain it there.
  4. Filter by Mehrdeutig (ambiguous). Clean up duplicate values in the directory or map individual users through Kandidaten manuell zuordnen … (map candidates manually).
  5. Find your two test users. Both must show Eindeutig (unique) or Manuell (manual).
  6. Click Einrichtung speichern.
  7. Check: the figure under Eindeutig matches the number of users who are to take part in the synchronisation.

Step by step: dry run and going live

  1. Open the Configuration page of the profile.
  2. First switch on only CUCM-Anrufstatus → Teams (CUCM call status) and select the CUCM connection.
  3. Leave Interval (seconds) at 10 and the main switch Enable presence sync off. Click Save.
  4. Make a call on the Cisco phone with a test user and click Dry run while it is connected.
  5. Read the Dry-run preview: Active calls shows at least 1, Planned changes names the test user, Conflicts is 0.
  6. Switch on Enable presence sync and click Save.
  7. Check: the runtime status changes to Synchronisation aktiv (synchronisation active), and Last check is a few seconds old.

Step by step: check in Presence Live

  1. Open Presence Live.
  2. Make another call on the Cisco phone with the test user.
  3. Watch the Statusverlauf (status history). Within the interval, an entry appears in the direction Cisco CUCM → Teams with the source status Im Gespräch (on a call) and the result Erfolgreich (successful).
  4. Check in the Teams client of a colleague that the test user shows "In a call".
  5. End the call. An entry with the action Freigeben (release) appears in the status history, and Teams shows the user's own status again.
  6. If required, switch on further directions, one at a time, and repeat dry run and check.
  7. Check: the counter Fehler (errors) above the status history stays at 0.

Fields and options: what you should have noted at the end

Field / actionMeaning and use
Tenant ID and client IDIdentifiers of the Entra app. EasyUC no longer displays the client secret after saving.
Expiry date of the client secretWhen it expires, Graph access fails. Enter a new secret in the profile in good time.
Application user and observerNames of the two Cisco accounts and who manages them.
Selected identifiersField in Microsoft and field in the CUCM that are used for the mapping.
Directions switched on and intervalState of the configuration page after acceptance.
Manual mappingsList of the exceptions with a justification, so that they can be reviewed when the directory changes.

Check the result and narrow down errors

  • Acceptance passed: for both test users, start and end of the call appear in Presence Live, Teams shows the status within the interval, and after the end of the call the user's own status is shown again.
  • Also check: restart of the Teams client during a call, two calls in succession, a user with "Do not disturb" in Teams. The last case must appear as skipped in the log.
  • The dry run shows Active calls 0 despite a call: the call monitoring of the CUCM connection does not cover the device. Check the Live Calls of the connection.
  • The test user is missing under Planned changes: they are not mapped uniquely, or their line is a shared line.
  • The runtime status stays at Erster Abgleich ausstehend (first synchronisation pending): the presence service is not running. Check it in the Manager.
  • Further messages and their remedies are in the chapter on error patterns.

Related chapters