As of Friday October 16th, access to restricted content on this site now requires you to log in with your Genesys account. If you don't have an account, you can request one at these locations: Request MyPartner Portal Account or Request My Support Account.
Jump to: navigation, search

Login/Logout

This set of models illustrates a scenario which follows Successful Registration:

  1. After connecting and registering, the agent application logs in to all available Interaction Servers.
  2. The agent application logs out from the Interaction Servers.

Agent Logs In

In this phase, shown in the figure below:

  1. The agent application sends RequestAgentLogin to the primary Interaction Server.
  2. The primary Interaction Server sends EventAgentLogin to the reporting engine, which responds with EventCurrentAgentStatus.
  3. The agent applications sends RequestAgentAvailable to all other Interaction Servers that are running.
  4. The primary Interaction Server relays EventCurrentAgentStatus to the agent application.

Note that the agent application uses different events to log in to primary versus secondary Interaction Servers.

Agent Logs In

This phase uses the messages shown in the following table:

Messages in Agent Logs In
Message Protocol
EventAck Interaction Management
EventAgentLogin Reporting
EventCurrentAgentStatus Reporting

Agent Logs Out

In this phase, shown in the figure below, the agent application sends RequestAgentLogout to the primary Interaction Server, which relays that information to the reporting engine. After the agent application receives EventAck from this Interaction Server, it sends RequestAgentNotAvailable to all secondary Interaction Servers.

Agent Logs Out

This phase uses the messages shown in the following table:

Messages in Agent Logs Out
Message Protocol
EventAck Interaction Management
EventAgentLogout Reporting
This page was last edited on March 22, 2018, at 00:48.

Feedback

Comment on this article:

blog comments powered by Disqus