/mcpHTTPS Requests Cisco Finesse does not support plain HTTP but supports only secure HTTP (HTTPS). In response to clients accessing Finesse using plain HTTP, the 301 HTTP redirect is issued to the secured port 8445. Cisco Finesse supports HTTP/2 protocol by default. Note Clients must make all HTTPS requests to port 8445. Finesse desktop APIs conform to the following format: https://<FQDN>:<port>/finesse/api/<object> Use the fully qualified domain name (FQDN) of the Finesse server instead of the IP address to avoid address mismatch errors (SSL certificate uses the Finesse hostname.) Note The following ports are disabled by default: • BOSH/WebSocket (HTTP)—7071 • XMPP—5222 Use the CLI command utils finesse set_property webservices enableInsecureOpenfirePort true to enable these ports. For more information on CLI commands, see Cisco Finesse Administration Guide at https://www.cisco.com/c/en/us/support/customer-collaboration/finesse/products-maintenance-guides-list.html. For gadget development, Finesse server and client connections only support TLS 1.2 by default. Note Real-Time Events Real-time events (such as call events, state events, and so on) are sent by the Cisco Finesse Notification Service, using the XEP-0060 Publish-Subscribe extension of the XMPP (Extensible Messaging and Presence Protocol) protocol. All real-time events are sent over HTTPS. The agents must remain connected to the Cisco Notification Service to retain the user presence information. If not, it can result in unexpected behavior or cause the desktop not to respond as expected. The developer content below only applies to the third-party application building its own XMPP client to communicate with the Finesse server. Gadgets running on the desktop need not do anything to receive events, as the desktop handles this automatically and makes the events available through the respective Javascript API interfaces. Note Applications that need to communicate with the Notification Service must use XMPP over the BOSH (Bidirectional-streams Over Synchronous HTTP)/WebSocket transport. BOSH/WebSocket is an open technology for real-time communication and is useful for emulating a long-lived, bidirectional TCP connection between two entities (such as client and server). See documentation at the XMPP Standards Foundation (http://www.xmpp.org) for details about both XMPP and BOSH/WebSocket (XEP-0124). Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 8 Introduction HTTPS Requests