Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Won't Do
-
chat 3.6, chat 3.11
-
None
-
CRM Connector (CRMCONNECT)
-
Sprint 17 CTI 7 Nov - 20 Nov
Description
On restore, chat-server:
- sends a chat-server-restore AMQ message to communication-server.
- The communication-server sets all logged in agents state to UNKNOWN.
- All offered (and not accepted) chat requests are re-queued. If we don't change the state of a logged in agent to UNKNOWN, all the offered chats (not yet accepted by the agent) will never be rerouted due to a limitation in the communication-server.
- The chat-server socket.IO server starts accepting connection requests
- Disconnected agents get auto reconnected but in an UNKNOWN state regardless of their previous state before disconnection.
- All conversations previously active on the agent are restored.
The agent cannot receive new chat requests until the agent changes state to READY.
Attachments
Issue Links
- causes
-
CSN-1029 [chat-server restore] Agent gets a new request even after MAX_SESSION
- Resolved
- created
-
CSN-955 [Chat Server Restore] Agent is in ready state - have no active chat session
- Open
- relates to
-
CSN-1193 Agent goes in UNKNOWN state fro Chat MRD from INTERRUPTED when comm-server comes up after fail-over
- Resolved
- Affects test execution of
-
CSN-955 [Chat Server Restore] Agent is in ready state - have no active chat session (Chat Solution/chat 3.6/Component Failover Testing ) FAIL
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...