EasyUC for Cisco
Presence Sync: error patterns and remedies
Messages and omission reasons of presence synchronisation with meaning and remedy.
In EasyUC: Presence Sync → Presence profiles → profile → Presence Live
What it is for
Presence Sync reports in three places when something does not run as expected: when the configuration is saved, in the status line of the profile and per event in Presence Live. This chapter sorts the messages by their origin and gives the meaning and the remedy for each.
The messages appear in German in the interface, even if you have selected another language. They are reproduced here verbatim so that you can find them with the search. Placeholders such as names or numbers are replaced by "…".
Prerequisites
- A presence profile and the permission
ROLE_APP_PRESENCE_SYNCto see the configuration and Presence Live. - For changes
ROLE_APP_PRESENCE_SYNC_EDIT, for the profile accessROLE_APP_PRESENCE_TENANTS_EDIT. - Access to the EasyUC Manager to check the presence service and its logs.
Step by step: narrow down a fault
-
Open Presence Live of the profile and read the runtime status between the two tiles: Synchronisation aktiv (synchronisation active), Voraussetzung fehlt (prerequisite missing), Teilweise verfügbar (partially available), Fehler (error), Erster Abgleich ausstehend (first synchronisation pending), Worker-Daten veraltet (worker data outdated) or Ausgeschaltet (switched off).
Fields and options: results and actions in Presence Live
| Field / action | Meaning and use |
|---|---|
| Erfolgreich (successful) | EasyUC has carried out the action at the vendor. Which action it was is shown in small print after the status: Setzen (set), Erneuern (refresh) or Freigeben (release). |
| Action Setzen (set) | A new target status was published. The entry shows Ziel angefordert: (target requested) with the state. |
| Action Erneuern (refresh) | An existing state was refreshed before it expired. |
| Action Freigeben (release) | EasyUC has removed its state at the vendor because the source has ended. |
| Beobachtet (observed) | EasyUC has read a change at the source. The entry does not confirm a transfer to the target. |
| Übersprungen (skipped) | The state is deliberately not transferred. The message gives the reason. This is not an error. |
| Fehler (error) | The vendor rejected the action or was not reachable. The message names the cause. |
| Ergebnis filter (result) | Erfolgreich, Fehler, Übersprungen / ignoriert and Beobachtet / Vorschau (observed / preview). The filters apply to the loaded entries, at most 5,000. |
| Direction System | Entries of the service without a user, for example saved settings or a cleanup after switching off. |
Omission reasons: deliberately not transferred
| Field / action | Meaning and use |
|---|---|
| Microsoft Graph unterstützt diesen Status nicht als sichere App-Session. | Microsoft Graph does not support this status as a safe app session. A Jabber status such as busy or do not disturb cannot be set in Teams as the session of an app without overwriting the personal status. No remedy required. |
| Die eigene EasyUC-PWS-Quelle wird nicht zurück nach Teams gespiegelt. | EasyUC's own PWS source is not mirrored back to Teams. The Jabber status that was read originates from EasyUC itself. This prevents a feedback loop. |
| Der von EasyUC in Teams gesetzte Status wird nicht zurück nach Cisco gespiegelt. | The status set in Teams by EasyUC is not mirrored back to Cisco. The Teams status that was read originates from EasyUC itself, for example from a CUCM call. |
| Ein persönlicher Cisco-DND-Override wird nicht überschrieben. | A personal Cisco DND override is not overwritten. Teams reports "Do not disturb" or "Presenting". Cisco requires a global override for this, which EasyUC does not set. |
| Status an der Quelle beobachtet; dies bestätigt keine Übertragung zum Ziel. | Status observed at the source; this does not confirm a transfer to the target. A pure observation entry at every change at a source. |
| … gemeinsam genutzte CUCM-Leitungen werden nicht als eindeutige Benutzeranrufe veröffentlicht. | … shared CUCM lines are not published as unique user calls. Calls on a shared line cannot be attributed reliably to one user. Give the users lines of their own if their call status is to appear. |
Messages when saving the configuration
| Field / action | Meaning and use |
|---|---|
| Für den Presence-Abgleich muss mindestens eine Richtung aktiviert sein. | At least one direction must be activated for presence synchronisation. The main switch is on, but no direction is selected. Switch on a direction. |
| Das Abfrageintervall muss zwischen 5 und 60 Sekunden liegen. | The polling interval must be between 5 and 60 seconds. Correct the value in the Interval (seconds) field. |
| Bitte eine aktive CUCM-Verbindung auswählen. | Please select an active CUCM connection. Under CUCM connection, select a connection that is active in EasyUC. |
| Für CUCM → Teams muss „Show Active Calls“ dieser Verbindung aktiviert sein und alle Geräte beobachten. | For CUCM → Teams, "Show Active Calls" of this connection must be activated and observe all devices. Switch on the call monitoring of the CUCM connection and set it to all devices. |
| Für den Presence-Abgleich fehlen die Microsoft-Graph-Zugangsdaten. | The Microsoft Graph credentials for presence synchronisation are missing. Enter tenant ID, client ID and client secret in the profile and check with Microsoft Graph testen (test Microsoft Graph). |
| Teams → Jabber ist vorbereitet, kann aber erst mit einem Cisco-IM&P-Presence-Web-Service für genau diese CUCM-Verbindung aktiviert werden. | Teams → Jabber is prepared but can only be activated with a Cisco IM&P presence web service for exactly this CUCM connection. The Cisco access of the profile contains no presence web service for the selected connection. Add it to the access in the profile. |
| Diese Entra-App wird bereits von einem anderen Presence-Tenant verwendet oder hält dort noch eine unbereinigte Session. Pro Entra-Tenant und Client-ID ist nur ein Presence-Eigentümer erlaubt. | This Entra app is already used by another presence tenant or still holds a session there that has not been cleaned up. Only one presence owner is allowed per Entra tenant and client ID. Use a separate app registration for each profile, or switch off the other profile and wait for the cleanup. |
| Der IM&P-Connector dieser CUCM-Verbindung wird bereits von einem anderen Teams→Jabber-Tenant verwendet oder hält dort noch unbereinigte Sessions. Pro Connector ist nur ein schreibender Tenant erlaubt. | The IM&P connector of this CUCM connection is already used by another Teams→Jabber tenant or still holds sessions there that have not been cleaned up. Only one writing tenant is allowed per connector. Only one profile may write to Jabber through the same Cisco access. Switch off the direction in the other profile or use a separate application user. |
| Bitte den Presence-Sync zuerst deaktivieren. Erst nach erfolgreicher Bereinigung können Entra-Tenant, Client-ID oder Client-Secret geändert werden. | Please deactivate presence sync first. Entra tenant, client ID or client secret can only be changed after a successful cleanup. Switch off the main switch, save, wait for one run and then change the credentials. |
| Cisco-Client oder Verbindung wurden nicht geändert, weil bestehende Presence-Sitzungen der bisherigen Konfiguration nicht vollständig bereinigt werden konnten. | Cisco client or connection were not changed because existing presence sessions of the previous configuration could not be cleaned up completely. The previous vendor was not reachable during the change. Restore reachability and save again. |
| Eine ausgeschaltete Sync-Richtung konnte nicht vollständig bereinigt werden; bestehende Presence läuft spätestens mit ihrer Ablaufzeit aus. | A sync direction that was switched off could not be cleaned up completely; existing presence expires at the latest when its expiry time is reached. A note, not an abort. The states that were set disappear on their own after the expiry time of the vendor. |
| Die Presence-Einstellungen werden gerade geändert; bitte erneut versuchen. | The presence settings are currently being changed; please try again. Another operation holds the lock of the profile. Wait briefly and save again. |
| Ein Presence-Abgleich läuft bereits. | A presence synchronisation run is already in progress. Sync Now was clicked during a running synchronisation. Wait for the run to finish. |
Messages of the running synchronisation
| Field / action | Meaning and use |
|---|---|
| Presence-Abgleich erfolgreich. | Presence synchronisation successful. The last run had neither errors nor notes. |
| Einstellungen gespeichert; der erste Abgleich steht noch aus. | Settings saved; the first synchronisation is still pending. The service has not yet processed the profile. If the message stays longer than the interval, check the presence service in the Manager. |
| Seit dem Aktivieren ist noch kein Presence-Worker-Lauf bestätigt. / Der letzte Presence-Worker-Lauf ist veraltet; Worker und Netzwerk prüfen. | No presence worker run has been confirmed since activation. / The last presence worker run is outdated; check worker and network. The presence service is not running or is stuck. Check the state and logs of the service in the Manager and restart it if necessary. |
| „Show Active Calls“ ist nicht mehr für alle Geräte aktiv; bestehende Teams-Status werden deshalb nicht gelöscht. | "Show Active Calls" is no longer active for all devices; existing Teams states are therefore not deleted. The call monitoring of the CUCM connection was restricted or switched off. Switch it on again for all devices. |
| Die CUCM-Leitungszuordnung ist momentan nicht erreichbar; bestehende Teams-Status bleiben unverändert. | The CUCM line mapping is currently not reachable; existing Teams states remain unchanged. The AXL access to the user directory does not respond. Check the CUCM connection and the AXL service. |
| Jabber → Teams konnte nicht gelesen werden: … | Jabber → Teams could not be read: … The presence web service did not answer the query. The text after the colon names the cause, for example network, TLS or login. |
| Teams → Jabber konnte nicht abgeglichen werden: … | Teams → Jabber could not be synchronised: … Publishing to Jabber failed. Check the Cisco access in the profile with Cisco-Verbindung testen (test Cisco connection). |
| Teams-Presence konnte nicht gelesen werden: … | Teams presence could not be read: … Microsoft Graph did not deliver the status. Check the permission Presence.Read.All, admin consent and the expiry of the client secret. |
| Microsoft hat nicht für alle zugeordneten Benutzer einen Presence-Status geliefert; bestehende Cisco-Quellen werden nicht gelöscht. | Microsoft did not deliver a presence status for all mapped users; existing Cisco sources are not deleted. The status is missing for individual users, for example those without a Teams licence. A note, not an abort. |
| IM&P liefert für … eindeutig zugeordnete Benutzer keinen bekannten Presence-Status; vorhandene Quellen werden bis zu ihrer Ablaufzeit beibehalten. | IM&P delivers no known presence status for … uniquely mapped users; existing sources are kept until they expire. The observer may not see the status of these users, or they have no valid Jabber address. Check the visibility for the observer and the presence domain. |
| … konnte nicht gesetzt werden: … / … konnte nicht entfernt werden: … | … could not be set: … / … could not be removed: … The vendor rejected an individual publication. For Teams, check the permission Presence.ReadWrite.All; for Jabber, the role of the application user. |
| IM&P hat die Application-Session wiederholt ersetzt; alle betroffenen Status sind für den nächsten Lauf sofort fällig markiert. | IM&P has repeatedly replaced the application session; all affected states are marked as due immediately for the next run. A second system logs in with the same application user. Use a separate application user for EasyUC. |
| Die gewählte Cisco-Verbindung ist nicht mehr aktiv; bestehende Presence-Status bleiben unverändert. | The selected Cisco connection is no longer active; existing presence states remain unchanged. The CUCM connection was deactivated or deleted in EasyUC. Select an active connection in the profile. |
| Die Microsoft-Graph-Zugangsdaten fehlen; bestehende Presence-Status bleiben bis zu ihrer Ablaufzeit erhalten. | The Microsoft Graph credentials are missing; existing presence states are kept until they expire. The credentials in the profile were removed. Enter them again. |
Messages on mapping and accesses
| Field / action | Meaning and use |
|---|---|
| Es sind keine eindeutigen Microsoft-/Cisco-Benutzer zugeordnet. | No unique Microsoft/Cisco users are mapped. The selected identifiers match for no user. Change the fields in the profile and repeat Zuordnung prüfen (check mapping). |
| … mehrdeutige Benutzerzuordnungen werden ausgeschlossen. / … Microsoft-Benutzer haben keinen eindeutigen Cisco-Treffer. | … ambiguous user mappings are excluded. / … Microsoft users have no unique Cisco match. A note referring to the counters Mehrdeutig (ambiguous) and Nicht gefunden (not found). Clean up the directory data or map manually. |
| Dieser Cisco-Benutzer passt zu mehreren Microsoft-Benutzern; alle betroffenen Zuordnungen werden ausgeschlossen. | This Cisco user matches several Microsoft users; all affected mappings are excluded. Two Microsoft accounts carry the same identifier. Correct one of them. |
| Das gewählte Microsoft-Feld ist leer oder ungültig. | The selected Microsoft field is empty or invalid. The identifier is not maintained for the user. The user counts as ignored. |
| Das Cisco-Benutzerverzeichnis ist nicht vollständig erreichbar. | The Cisco user directory is not completely reachable. The AXL access does not deliver a complete user list. Check permission, AXL version and certificate. |
| Die Benutzerverzeichnis-Abfrage ist fehlgeschlagen; der nächste sichere Zuordnungsversuch steht noch aus. | The user directory query failed; the next safe mapping attempt is still pending. EasyUC continues to use the last valid mapping and tries again after a short wait. |
| CUCM-AXL-Lesezugriff nicht bestätigt; URL/TLS/Zugangsdaten prüfen. | CUCM AXL read access not confirmed; check URL/TLS/credentials. Result of Cisco-Verbindung testen. The address must end in /axl/, and the certificate must be trusted. |
| IM&P-Anmeldung nicht bestätigt. TLS/Zugangsdaten prüfen; eine aktive Worker-Session wird nicht übernommen. | IM&P login not confirmed. Check TLS/credentials; an active worker session is not taken over. Check application user, password and the role Admin-3rd Party API. With an internal certificate authority, store the CA certificate. |
| Cisco IM&P ist nicht sicher erreichbar (Netzwerk/TLS/Timeout). | Cisco IM&P is not securely reachable (network/TLS/timeout). Check the network path and the certificate of the presence web service. |
| Für den CUCM-Benutzer ist keine gültige IM&P-JID vorhanden. | No valid IM&P JID exists for the CUCM user. The user has no Jabber address. Check the directory URI or the presence domain. |
| Ein anderes aktives Presence-Profil verwendet bereits diese IM&P-Application-Session. | Another active presence profile already uses this IM&P application session. Only one active profile per application user. Create a separate application user or switch off the other profile. |
| Das Connectorprofil ist noch einem Presence-Profil zugeordnet. Synchronisation deaktivieren und Verbindung trennen, bevor Zugangsdaten geändert oder das Profil gelöscht werden. | The connector profile is still assigned to a presence profile. Deactivate synchronisation and disconnect the connection before credentials are changed or the profile is deleted. First switch off synchronisation in all profiles that use this Cisco access. |
| Verbindung steht; das Verzeichnis liefert keine Benutzer. | Connection established; the directory delivers no users. Result of Microsoft Graph testen. The login succeeds, but User.Read.All is missing or has not been consented to. |
Check the result and narrow down errors
- The fault is fixed when the runtime status shows Synchronisation aktiv, the notes below the tiles are empty and a test call creates an entry with the result Erfolgreich (successful).
- If Verbindung gestört (connection disrupted) appears above the view, your browser does not reach the EasyUC API. Existing entries remain visible, and the next request tries again.
- If Teams shows a status longer than expected although EasyUC was switched off: the vendor keeps it until the expiry time, in Teams up to ten minutes, in Jabber up to one hour.
- If a status change is missing in the log although it took place, it was shorter than the interval. Reduce the interval.
- If you do not find a message here, the full text is in the log of the presence service in the Manager. This log contains no credentials.