McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 18

↗ View in doc context
page
18
source
finesse/v12.5/developer-guide/developer-guide.md
chunk_id
finesse::v12.5::developer-guide::developer-guide::2

• Single Sign-On—Get User Authentication Mode—This API allows a client to get the authentication mode of a user in a Unified CCE deployment that is in hybrid mode (SSO and non-SSO). • ECCVariableConfig—Get ECC Variable Configuration—This API allows a user to get ECC variable configuration details for Unified CCE. • Cloud Connect Configuration—This API allows a user to configure Cloud Connect in the Cisco Finesse server. The following are the new Cloud Connect Configuration APIs: • CloudConnectConfig—Get • CloudConnectConfig—Set • CloudConnectConfig—Delete The following changes are made to the payloads in the Cisco Finesse 12.5(1) REST APIs. • MediaPropertiesLayout APIs—The uiEditable field has been added to the payload to indicate if the call variable values can be edited in the agent and supervisor desktop. • SystemInfo APIs—The following fields have been added to the payload: • lastSuccessCTIHeartbeatTime—Indicates the last successful heartbeat time between the Cisco Finesse server and the CTI server. • ctiVersion—Indicates the CTI protocol version with which the Cisco Finesse server is connected to the CTI server. • ctiHeartbeatInterval—Indicates the heartbeat interval between the Cisco Finesse server and the CTI server in seconds. • Phone Book Contact Limit The maximum number of contacts per agent is increased from 1500 to 6000 in the PhoneBook and Contact APIs. • Dialog—Create a New Dialog (Make a Call) For a Unified CCE deployment, the MAKE_CALL API now allows you to make a call from Ready state. When an agent goes off-hook to place a call, the Unified CCE changes the agent status to Not Ready with 50006 reason code. HTTP Secure Support This release supports only HTTP Secure (HTTPS) and support for HTTP is disabled for the administration console, desktop (agent and supervisor), Web Services, Desktop Modules (gadgets), and Finesse IPPA. All the HTTP requests are automatically redirected to HTTPS. The support to the following ports are disabled: • Tomcat (HTTP)—80, 8082: If you access Finesse using HTTP, then the 301 HTTP redirect status response is issued to the secure port 8445. • BOSH/WebSocket (HTTP)—7071 and XMPP—5222: These ports are disabled by default. Set the utils finesse set_property webservices enableInsecureOpenfirePort to true to enable these ports. For more information, see Service Properties section in Cisco Finesse Administration Guide at https://www.cisco.com/c/en/us/support/customer-collaboration/finesse/products-maintenance-guides-list.html. Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 2 Introduction What's New in Cisco Finesse 12.5(1)