Activating and observing presence synchronisation

What it is for

On the Configuration page of a presence profile you define in which direction synchronisation takes place and switch it on. For Jabber there are three independent switches: the Jabber status to Teams, the call status from the CUCM to Teams and the Teams status to Jabber.

EasyUC detects the call status through the call monitoring of the CUCM connection: a connected call on the Cisco phone sets the matching Teams user to "In a call". Ringing alone changes nothing. For Teams, EasyUC publishes a session of its own through Microsoft Graph, for Jabber through the presence web service of IM and Presence. States set manually by users take precedence and are not overwritten.

The work is done by a background service of its own at a base rate of five seconds. Presence Live shows every publication, every omission and every error with time, user, direction and reason. Presence Live and some texts on the configuration page are labelled in German in version 4.8.7 and are quoted as shown.

Prerequisites

A saved presence profile with checked Graph access, Cisco access and user mapping.
Viewing: ROLE_APP_PRESENCE_WORKSPACE and ROLE_APP_PRESENCE_SYNC. Changing and triggering manually: additionally ROLE_APP_PRESENCE_SYNC_EDIT.
The presence service of the appliance is running.
For CUCM-Anrufstatus → Teams: the selected CUCM connection monitors active calls on all devices. The selection then shows all devices monitored.
For Cisco Jabber → Teams: a presence observer user is stored in the Cisco access.
The Entra app has User.Read.All, Presence.Read.All and Presence.ReadWrite.All with admin consent.

Step by step: switch on synchronisation

Select Presence Sync at the top and click Configuration on the profile.
Under Cisco Client beim Kunden, check the selection Cisco Jabber · IM and Presence.
Check the two status rows Microsoft Graph permissions and Cisco IM and Presence connector. Both should show Ready.
Switch on the desired directions: Cisco Jabber → Teams, CUCM-Anrufstatus → Teams, Teams → Cisco Jabber.
For the call status, select the CUCM connection under CUCM connection.
Under Interval (seconds), enter a value from 5 to 60. The default is 10.
Click Save, still without the main switch.
Click Dry run. In the Dry-run preview, read the values Mapped users, Active calls, Conflicts, Planned changes and Ignored users. The dry run writes nothing.
Switch on Enable presence sync and click Save.
If required, click Sync Now so that you do not have to wait for the next cycle.

Step by step: follow status changes in Presence Live

Click Presence Live on the profile or Live-Ansicht öffnen on the configuration page.
Check the header: Connector bereit, Microsoft Graph eingerichtet and the runtime status, for example Synchronisation aktiv.
For a test, change the status of a mapped user or make a call on the Cisco phone.
Watch the Statusverlauf (status history). The view reloads every 5 seconds. The newest entries are at the top.
Narrow down with Richtung (direction), Ergebnis (result) and the search field. Zurücksetzen clears the filters.
Click Pause to stop the list and Fortsetzen to continue loading.
Click Ältere Einträge laden to go further back.

Fields and options

Fields and options
Field / action	Meaning and use
Enable presence sync	Main switch. The integration remains completely inactive until it is switched on and saved.
Cisco Jabber → Teams	Reads the status from Cisco IM and Presence and publishes available and away in Teams.
CUCM-Anrufstatus → Teams	A connected call on the Cisco phone sets the Teams user to "In a call".
Teams → Cisco Jabber	Transfers available, away, busy as well as calls and meetings to Jabber. States that cannot be transferred safely, such as "Do not disturb" and "Presenting", are omitted and logged with a reason.
CUCM connection	CUCM connection for the call status. Suffix all devices monitored or monitoring incomplete.
Interval (seconds)	Interval of the synchronisation runs for this profile. Allowed: 5 to 60 seconds. Default 10.
Mapped users / Active calls / Conflicts / Last check	Figures of the last run of the background service.
Dry run	Calculates the planned changes without publishing states or writing events.
Sync Now	Triggers a run immediately. Only after the settings have been saved.
Richtung (Presence Live)	Cisco → Teams, Teams → Cisco or System.
Ergebnis (Presence Live)	Erfolgreich (successful), Fehler (error), Übersprungen / ignoriert (skipped / ignored), Beobachtet / Vorschau (observed / preview).

Check the result and narrow down errors

Success: runtime status Synchronisation aktiv, Last check is a few seconds old, and during the test call Presence Live shows an entry in the direction Cisco → Teams with the result Erfolgreich.
Select at least one sync direction. The main switch is on, but no direction is selected.
Presence sync can only be enabled after this CUCM connection monitors active calls on all devices. Switch on call monitoring of the CUCM connection for all devices.
IM&P connector not ready with the note that the direction only publishes once an IM and Presence server is connected. Test the Cisco access in the profile.
Für Jabber → Teams muss ein lesender Cisco-Presence-Benutzer auf dem Server konfiguriert sein. Der Connector meldet derzeit keine Leseberechtigung. Add the observer user in the Cisco access.
Der Worker hat noch keinen Abgleich gemeldet. or Der letzte Worker-Abgleich ist veraltet. Hintergrunddienst und Verbindungen prüfen. The presence service of the appliance is not running or is stuck. Check the state of the service in the Manager.
Save the changed settings before running the sync.
Conflicts greater than 0: an identifier matches several people. Clean up the mapping in the profile with Zuordnung prüfen.
States such as "Do not disturb" appear in Presence Live as Übersprungen / ignoriert with a reason. This is a limit of the vendor interfaces and not an error.
If a source fails, EasyUC does not set anyone to "available". States already published can persist at the vendor until they expire.