McDewey

Client applications can communicate with the Cisco Finesse Notification Service through BOSH/WebSocket, using the binding URI http://<host>:7071/http-bind. Developers can create their own BOSH/WebSocket library or use any that are available publicly. Client applications can communicate with the Cisco Finesse Notification Service through BOSH/WebSocket over HTTPS, using the binding URI https://<FQDN>:7443/http-bind. Developers can create their own BOSH/WebSocket library or use any that are available publicly. Finesse desktop uses the Strophe.js XMPP library internally to manage its XMPP connections over BOSH/Websocket. Applications receive notification events of feeds to which they are subscribed. Users are currently subscribed to a few feeds by default (subject to change). Other feeds require an explicit subscription (see Subscription Management). XMPP Connection Management 1. After creating the connection, the client application must send a priority stanza with a non-negative presence priority to ensure all events are recieved. It is advisable to set the presence priority as 0 by default. For more details about the presence information, see the Mapping the Extensible Messaging and Presence Protocol (XMPP) to Common Presence and Instant Messaging (CPIM) documenation. 2. Stream management is not supported by the Finesse Notification service and clients cannot use this feature. 3. Finesse depends on the presence availability of the agent to drive automatic logouts. Therefore, ensure that the whitespace pings are enabled and have retries to handle failures. Finesse uses ping interval value of 10 seconds and 2 retries. API Parameter Types The following sections describe the parameter and data types for the Cisco Finesse APIs. API Header Parameters Description Type Name The password used in the request header to make any Finesse API request. Finesse supports a "Basic" authorization scheme only and authorization is required for each Finesse API request. String password The username used in the request header to make any Finesse API request. Finesse supports a "Basic" authorization scheme only and authorization is required for each Finesse API request. String username Body Parameter A body parameter (also known as a complex parameter) appears in the body of the message. In the following example, targetMediaAddress and requestedAction are body parameters. <Dialog> <targetMediaAddress>1001001</targetMediaAddress> <requestedAction>HOLD</requestedAction> </Dialog> Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 9 Introduction API Parameter Types