Outbound data interactions

The following sequence diagram describes a typical outbound power call scenario. The scenario can be resumed in the following steps (step numbers are annotated in the diagram):

  1. ListManagement has a contact ready for execution; ListManagement requests ServerManager to create a session.
  2. ListManagement requests a Distribute to ServerManager.
  3. ServerManager sends a Session::Distribute|Routing event to Router.
  4. Router searches for an appropriate available agent and requests a deliver to ServerManager.
  5. ServerManager reserves the agent and creates the agent session – events sent to OneAgentWeb (Server).
  6. ServerManager sends Session::AssignAgent|Assigned event to ListManagement.
  7. ListManagement request a MakeContact to ServerManager.
  8. ServerManager request a MakeDataInteraction to MessageControl.
  9. ServerManager evolves the agent state to busy and the agent session state to connecting – events sent to OneAgentWeb (Server).
  10. OneAgentWeb accepts Data interaction.
  11. ServerManager calls accept message to MessageControl.
  12. ServerManager evolves the agent session state to Working.
  13. MakeDataInteraction callback is sent to ServerManager.
  14. MakeContact callback is sent to ListManagement.
  15. Deliver callback is sent to Router indicating that the operation was successful.

Outbound_Data_Interactions_Diagram.png