Communication Flow Diagram
Solution components communicate over different TCP/IP channels as explained below.
Component | Communication Pattern |
Siebel Driver | Connects with GC over OpenWire for bidirectional communication |
GC | A telephony middleware between Driver and Cisco Finesse. It establishes a local connection with ActiveMQ for bidirectional async communication on OpenWire protocol. With Cisco Finesse, GC communicates via RESTFul web services and XMPP. |
Connector Monitor | Web console monitoring of the Connector via HTTP/HTTPS |
Communication Flow for an Agent Login
This is a sample and a happy path flow of messages for an operation.
When client logs into Siebel Web and tries to login on the communication toolbar, the flow of communication between the Siebel CTI Connector solution components is described below.
The Driver sends a Hello message to GC.
If the connector is alive and receives the Driver’s request, it responds with a System IN_SERVICE message.
The Driver sends a Connect() request to GC
GC checks if it doesn’t already have this agent’s subscription, it requests Cisco Finesse for agent’s subscription.
The Driver then sends a Login request with agent Id, password, and extension.
If “UseSecurePassword” is set, then agent password is encrypted with Triple-DES before forwarding the request.
GC forwards the login request to Cisco Finesse
If “UseSecurePassword” is set, the Connector decrypts the password before forwarding the request to Cisco Finesse.
Cisco Finesse shares updated agent state if the login happens successfully.
GC responds with update agent-state and dialog state if there’s already an active call for this agent.
For further details about GC communication patterns for its clients, refer to Generic Connector SDK.