/mcp{String} The ctiHeartbeatInterval between the Cisco Finesse server and the CTI server. getLastCTIHeartbeatStatus() Retrieves the lastCTIHeartbeatStatus. The lastCTIHeartbeatStatus provides the success or failure of the last heartbeat sent to the CTI server. This can be used to determine whether the Cisco Finesse side is healthy or not. If three consecutive heartbeats fail, the CTI server gets disconnected. • success—The last CTI heartbeat was successful. • failure—The last CTI heartbeat was unsuccessful. Returns {finesse.restservices.SystemInfo.lastCTIHeartbeatStatus} The last Heartbeat status (success or failure) to CTI. getlicense() Retrieves the license and is applicable only to Unified CCX deployment. Returns {String} The Unified CCX deployment license details. Otherwise, an empty string. getPeripheralId() Retrieves the peripheral Id that Cisco Finesse is connected to. The peripheral Id refers to the Id of the PG Routing Client (PIM). Returns {String} The Id of the Unified CCE peripheral to which Cisco Finesse is connected. For Unified CCX, it returns an empty string. getStatus() Retrieves the status of the Cisco Finesse server. The possible values are: • IN_SERVICE • OUT_OF_SERVICE Returns {finesse.restservices.SystemInfo.Statuses} The system status. getStatusReason() Retrieves the reason for Cisco Finesse being OUT_OF_SERVICE. Returns {String} Returns the status reason if the Cisco Finesse is OUT_OF_SERVICE. Otherwise, an empty string when Cisco Finesse status is IN_SERVICE. getSystemAuthMode() Retrieves the system authentication mode for the current deployment. The possible values are SSO or non-SSO. Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 516 Cisco Finesse JavaScript APIs SystemInfo