Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

CaseDescription Reason Version 
Failover Logout EventFor 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 type set by consult call For failover case in consult call we will not set main call type if we receive 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












  • No labels