McDewey

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

Page 531

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

onLoad: handleSystemInfoOnLoad, onChange: handleSystemInfoOnChange }); systeminfo.getCtiMMode(); Methods getAlternateHost() Retrieves the FQDN of the alternate Finesse host and this is used for failover purposes. Returns {String} The FQDN (if properly configured) of the alternate node, defaults to primary if no match is found, and undefined for the single-node deployments. For example, if the desktop is connected to the primary Finesse node, this method will return FQDN of the secondary Finesse node, and vice-versa. getCtiVersion() Retrieves the CTI version for the current deployment. Example systeminfo.getCtiVersion(); Returns {String} The CTI version used in the Cisco Finesse to connect the CTI server. getCurrentTimestamp() Retrieves the current timestamp from the SystemInfo object. This is used to calculate the time drift between the server and the client. Example systeminfo.getCurrentTimestamp(); Returns {String} The time (GMT) in the format: yyyy-MM-dd'T'HH:mm:ss'Z' getDeploymentType() Retrieves the deployment type Unified CCE or Unified CCX. Example systeminfo.getDeploymentType(); Returns {String} The deployment type, which is either Unified CCE or Unified CCX. getHeartbeatInterval() Retrieves the ctiHeartbeatInterval for the current deployment. This represents the interval of heartbeats between the Cisco Finesse server and CTI server (in seconds) that helps in failover time calculation. Returns Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 515 Cisco Finesse JavaScript APIs SystemInfo