| Case | Description | Reason | Version |
|---|---|---|---|
| Failover Logout Event |
received in case of failover after login.
We will distinguish it from normal event
based on reason code, it is -1 in case of
failover event
| For forced logout we check system status through Api ,if heartbeat successfulthen check agent state, if agent state logout then login. If no heartbeat check system status again, for 3 times. | Sometimes in failover we receive logout event even after login, to avoid agent from logging out, we need to ignore this event. | 2.0.2 onwards |
| Failover case, main call |
set
| type set by consult call | For failover case in consult call we |
not
| will not set main call type if we receive |
event
| first event of consult call. | For scenario, where we have 2 calls i.e. inbound and consult then if we receive consult event first, then it will set main call type to be Internal for activity of main call i.e inbound call. | 2.0.2 onwards | |
| Consult call over queue not differentiable in CCE | Append "c" with ani in call variable for consult case. Not update call variable if already has "c" appended. | In CCE, for consult over queue, call type becomes OUT same as outbound. To differentiate it from normal call we will append "c" in call variable. Also we will not update call variable if it has been already set with a value that has "c" appended in order to preserve the consult call variable. | 2.0.2 onwards |