EasyUC for Cisco
Presence with Cisco Webex
Switch the native Cisco integration with Teams and observe its status changes.
In EasyUC: Presence Sync → Presence profiles → profile → Cisco Webex
What it is for
If the customer uses the Webex App instead of Jabber, the presence status lives in the Webex cloud, even when telephony runs through the CUCM. Synchronisation with Microsoft Teams is then handled by Cisco itself through the "Cisco Call for Microsoft Teams" integration.
In this mode EasyUC does not publish any states of its own. It can read and set the organisation-wide switch of the Cisco presence integration and observes the status changes in Webex and Teams. In Presence Live, Beobachtet (observed) means that EasyUC has read a source status. It does not confirm that Cisco has already transferred the target status. The Webex-specific labels are German in version 4.8.7 and are quoted as shown.
Prerequisites
- The Presence Sync module is active. Roles as for the presence profile:
ROLE_APP_PRESENCE_TENANTS_EDITandROLE_APP_PRESENCE_SYNC_EDITfor setup. - In Microsoft Entra: app registration with
User.Read.AllandPresence.Read.Allwith admin consent.Presence.ReadWrite.Allis not required for Webex mode. - In Webex: an integration with client ID and client secret and a refresh token. Permissions required according to the interface:
spark-admin:people_readandspark:people_readwith admin consent. To read the organisation switchspark-admin:telephony_config_read, to change it additionallyspark-admin:telephony_config_writeand a suitable administrator role. - The Webex organisation ID.
- On the Cisco side: Cisco Call is approved and installed in the Teams admin center, the Microsoft consent required by Cisco has been granted, and the Microsoft Teams integration is set up in Control Hub. With telephony through Unified CM, the Presence status sync service in Connected UC is required as well. The current Cisco guide is authoritative.
- The e-mail addresses of the users match in Microsoft and Webex.
Step by step
Fields and options
| Field / action | Meaning and use |
|---|---|
| Webex-Organisations-ID | Identifier of the Webex organisation. Responses of the Webex API are checked against it. |
| Webex-Integrations-Client-ID / Webex-Client-Secret | Credentials of the Webex integration. |
| Webex-Refresh-Token | Allows the access to be renewed automatically. |
| Vorhandenes Zugriffstoken verwenden / Webex-Access-Token | Alternative without a refresh token. An access token alone is limited in time. Its expiry appears as a connector error. |
| Kennzeichen in Webex | Webex-E-Mail, Webex-Telefonnummer or Webex-Person-ID. |
| Organisationsweite Cisco Presence-Integration aktivieren / deaktivieren | Sets the switch for the entire Webex organisation and its Teams integration. |
| EasyUC-Monitoring aktivieren | Controls only the observation and the log in EasyUC. Synchronisation by Cisco runs independently of it. |
| Cisco Webex → Teams / Teams → Cisco Webex | Observation directions. Cisco synchronises natively, EasyUC logs the changes. |
| Interval (seconds) | 5 to 60 seconds. Choose a larger value with many users because Webex limits frequent status queries. |
Check the result and narrow down errors
- Success: runtime status Monitoring aktiv, the connector shows Ready, and Presence Live shows entries with the result Beobachtet / Vorschau.
- Speichere zuerst den Cisco Client bei ausgeschaltetem Hauptschalter. Aktiviere anschließend die organisationsweite Cisco Presence-Integration, bevor du das EasyUC-Monitoring einschaltest. Keep to this order: save the client, activate the Cisco integration, then switch on monitoring.
- Die Cisco Presence-Integration konnte nicht aktualisiert werden. The token lacks the write permission or the administrator role in Webex.
- If the connector reports an expired token, save the access in the profile with a new refresh token.
- If Webex throttles the queries, EasyUC reports the observation as incomplete. Increase the interval.
- Switching off monitoring or the module does not deactivate native synchronisation by Cisco. Only the organisation switch does that.
- An organisation switch that is on does not replace the prerequisites on the Cisco and Microsoft side. If the states remain unchanged despite the switch, check the setup in Control Hub and in the Teams admin center.