Hi all,   For various very long reasons relating to working around CORS and embedding other 3rd party apps/CRMs, we're trying to run Finesse 11.6(1) ES01 at a customer behind a reverse proxy. Everything's set up and forwarding / URL rewriting. However, the call control banner fails to load, because of CORS. The call control banner looks like it attempts to load from the real Finesse server name, rather than the reverse proxy. And while the Finesse API endpoints support sending the needed Access-Control-Allow-Origin header, apparently the Finesse Tomcat instance serving the general /desktop (or /desktop/thirdparty) resources does not. So the call control banner is unable to load its HTML resources, causing a Load Failed message to be displayed.   Any ideas? Would ES04 fix this? Attached is the CORS error from Chrome's dev console.       ... View more

We have a CTI client library for an application of ours, which to this point has always been read-only, merely processing events. We are now adding some call and agent control to it. However, once that test CTI application performs a normal CloseReq with no error (and receives the CloseConf back from the UCCE CTI server), any agent that test CTI application previously sent an agent state request for is placed into Not Ready (Connection Failure) state in Finesse. This only seems to happen if an agent state request message is sent - call control and other control operations do not cause this behavior. Attached is a snippet of a dumplog from our PCCE PG's CTI server. The test agent is already logged in and in Ready mode, through Finesse, before our test client connects. The test CTI client connects, performs a single agent state change request to Ready (which basically is a no-op), and then sends a CloseReq. The CTI client receives back the CloseConf and properly shuts down. But in the PG CTI server, as soon as the CloseReq is received, the agent is placed by UCCE into Not Ready 50002 (Connection Failure) mode. The agent must manually return themselves to Ready in Finesse afterwards. What is missing? Is this a CTI bug or other undocumented behavior because another CTI client has done an agent state control request? ... View more

Is it possible to have a gadget publish an event to a topic, with a proper payload containing DNIS, call variables, etc, that would cause other gadgets and screen pops to perform their operations as if a call was being received, but without a call? This would sort of work, in concept, like an Outbound Preview call, where call data is presented before an agent can accept or reject, but would not work through the Outbound Option. The gadget would then perform a place call if the user so chooses. But the main point of the question is how to have Gadget A, which has received all data on the call to be placed through other means, force all other gadgets to perform their actions with the call data provided by Gadget A. What about the workflow events? Thanks! ... View more