/mcpPossible Values Description Data Type Name PUT: A property of the User, Dialog, Team, Queue, or Media object that was modified. DELETE: A User, Dialog, Team, Queue, or Media object has been deleted. For a User/Queues modification, the queues removed from the user's list of queues. POST: A User, Dialog, Team, Queue, or Media object has been added. For a User/Queues modification, specifies the queues that were added to the user's list of queues. The type of modification that occurred to the User, Team, Dialog, Queue, User/Queues, or Media object. String Event /finesse/api/User/{id} /finesse/api/Dialog/{id} /finesse/api/Team/{id} /finesse/api/User/{id}/Dialogs /finesse/api/User/{id}/Dialogs/Media /finesse/api/Queue/{id} /finesse/api/User/{id}/Queues /finesse/api/User/{id}/Media The resource location for the User, Dialog, Team, Queue, User/Queues, or Media object that was modified. String Source An opaque, unique string, used to correlate the originating request with the resulting event The requestId that was returned when the triggering REST API request was made. If the event was unsolicited, this tag is empty. This tag is empty for a User/Queues notification. String RequestId Managing Notifications in Third-Party Applications For applications that aren’t gadgets in the Cisco Finesse Desktop or in a third-party OpenSocial container, use one of the following methods to establish a connection with the Cisco Finesse Notification Service to subscribe to XMPP events: • Cisco Finesse Desktop EventTunnel (for browser applications only) • XMPP over TCP based on Smack over port 5222 or 5223 (TLS) Finesse uses the following base XMPP features: 1. session establishment 2. presence Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 371 Cisco Finesse Notifications Managing Notifications in Third-Party Applications