EasyUC for Cisco
Setting up a presence profile
Create Microsoft tenant, Cisco access and user mapping for presence synchronisation.
In EasyUC: Presence Sync → Presence profiles → Add presence profile
Images come from the EasyUC lab. Names and example values provide orientation. A different interface language is indicated beside the relevant image.
What it is for
Anyone using Cisco telephony and Microsoft Teams side by side does not see in Teams that a colleague is on a call on the Cisco phone, and does not see in Jabber that they are in a Teams meeting. The Presence Sync workspace synchronises these states.
The basis is one presence profile per customer. It contains three things: the access to Microsoft Graph for the tenant, the access to the Cisco side (CUCM with IM and Presence for Jabber, or the Webex cloud) and the rule by which EasyUC recognises the same person in both systems. A profile needs no SBC, no SIP port and no certificate. The three setup steps inside a profile are labelled in German in version 4.8.7, also in the English interface, and are quoted as shown.
A new profile starts switched off. You then activate synchronisation on the Configuration page. Tenants that already exist in EasyUC Teams appear as profiles marked Shared with Teams SBC and share the Graph access.
Prerequisites
- The Presence Sync module is activated on the appliance. It runs as a service of its own and requires neither the Teams SBC nor the ACD.
- Viewing profiles:
ROLE_APP_PRESENCE_WORKSPACEandROLE_APP_PRESENCE_TENANTS. Creating or changing profiles: additionallyROLE_APP_PRESENCE_TENANTS_EDIT. Cisco access and user mapping: additionallyROLE_APP_PRESENCE_SYNCand, for changes,ROLE_APP_PRESENCE_SYNC_EDIT. Administrators (ROLE_APP_ADMIN,ROLE_OWNER,ROLE_ADMINorROLE_SUPER_ADMIN) have all permissions. - In Microsoft Entra: an app registration with client ID and client secret. Application permissions
User.Read.All,Presence.Read.AllandPresence.ReadWrite.Allwith admin consent for the tenant. - For Jabber in the CUCM: AXL access to the user directory. You can take over an existing CUCM connection from EasyUC or enter address, version and user directly.
- For Jabber on IM and Presence: the address of the presence web service, the presence domain, an application user with the role
Admin-3rd Party APIand a dedicated end user as observer who may read the presence status of the mapped Jabber users. - A field that carries the same value in Microsoft and Cisco, for example e-mail address or phone number.
- Other prerequisites apply to Webex. See the chapter on presence with Cisco Webex.
Step by step: create a profile
Step by step: check accesses and mapping
Fields and options
| Field / action | Meaning and use |
|---|---|
| Profilname | Display name of the profile, at most 190 characters. The customer name is common. |
| Microsoft-Tenant-ID | Directory ID of the Microsoft tenant. |
| Microsoft-Graph-Client-ID / Client-Secret | Credentials of the Entra app. Stored secrets are not displayed. Empty fields keep the existing value. |
| CUCM / Jabber or Cisco Webex | Client the customer uses. The client of an existing Cisco access cannot be changed afterwards. |
| Name der Cisco-Verbindung | Name of the stored Cisco access, at most 190 characters. One access can be used by several profiles. Changes then apply to all of them. |
| CUCM-AXL-Adresse | HTTPS address of the AXL interface. It must end in /axl/, for example https://cucm-pub01.intern:8443/axl/. |
| AXL-Version | Selection from 10.0 to 15.0. |
| Presence-Webservice-Adresse | HTTPS address of the presence web service on IM and Presence, with the path /presence-service. |
| Presence-Domain | Domain of the Jabber addresses, for example example.com. |
| Presence-Anwendungsbenutzer / -kennwort | CUCM application user with the role Admin-3rd Party API. |
| Presence-Beobachterbenutzer | End user with read permission for the presence status of the mapped Jabber users. Without it EasyUC cannot read the Jabber status. |
| Erweiterte Cisco-Einstellungen | Alternative Webservice-Adresse for a second IM and Presence node, and paths to CA certificates on the EasyUC server for private certificates. |
| Kennzeichen in Microsoft | E-Mail, User Principal Name, Geschäftliche Telefonnummer (business phone), Mobiltelefon, Entra-Objekt-ID, Mitarbeiter-ID (employee ID), Lokaler Benutzername (on-premises user name) or a custom attribute. |
| Kennzeichen in CUCM / Jabber | CUCM Mail-ID, CUCM Benutzer-ID, CUCM Telefonnummer, CUCM Directory URI or CUCM Abteilung (department). |
| Groß- und Kleinschreibung unterscheiden | Case sensitivity. Default: off. When switched on, the values must match exactly. |
| Manuelle Zuordnungen | Fixed pairs of Microsoft user ID and Cisco user ID. Each ID may occur only once. |
| Delete profile | Only for independent profiles. Deletes the profile and stops its synchronisation. |
Check the result and narrow down errors
- Success: the profile list shows Microsoft Graph · Ready, the Cisco test is green and the preview shows the expected number under Eindeutig.
- Speichere das Profil vor dem Verbindungstest. and Speichere den Cisco-Zugang vor dem Verbindungstest. Tests always work with the stored credentials.
- Wähle eine vorhandene Verbindung oder gib einen Verbindungsnamen und gültige HTTPS-Adressen ohne eingebettete Zugangsdaten ein. Addresses must begin with
https://and must not contain a user. - Die Prüfung ist unvollständig. Beachte die Hinweise; nicht geprüfte Benutzer gelten nicht als zugeordnet. One of the directories could not be read completely.
- Mehrdeutig: the same value occurs for several users. Such matches are skipped. Change the field or map manually.
- Für die Cisco-Einrichtung benötigst du die Presence-Sync-Berechtigung.
ROLE_APP_PRESENCE_SYNCis missing. - Dieses Profil teilt seine Microsoft-Zugänge mit dem Teams SBC. Änderungen gelten für beide Bereiche und benötigen zusätzlich die Teams-Tenant-Bearbeitungsberechtigung. Changes apply to both areas and also need the Teams tenant edit permission.
- Ein anderes aktives Presence-Profil verwendet bereits diese IM&P-Application-Session. Per IM and Presence application user only one active profile can publish. Use an application user of its own or deactivate the other profile.
- If saving fails after the first partial step, the profile is kept. Add the missing details and save again. No second profile is created.