Uploaded image for project: 'Chat Solution'
  1. Chat Solution
  2. CSN-867

[socketIO] Implement server side acknowledgement

    XMLWordPrintable

Details

    • Story
    • Status: Resolved
    • Major
    • Resolution: Done
    • chat 3.6
    • chat 3.7
    • Chat Server
    • None
    • CRM Connector (CRMCONNECT)
    • Sprint 2 CTI 11 Apr 24, Sprint 3 CTI 25 Apr - 8 May, Sprint 4 CTI 9 May - 22 May, Sprint 6 CTI 12 Jun - 19 Jun, Sprint 7 CTI 20 Jun - 3 Jul
    • 3

    Description

      For all socket connections with its clients, chat server should send the acknowledgment only when the message has been processed.

      • A message may have been enqueued successfully ⇒ SUCCESS
      • A message couldn’t be processed due to an error from the underlying component such as ActiveMQ. ⇒ FAILURE event

      implement SUCCESS and ERROR codes/objects in a standard mechanism
      implement messageId on agent-gadget and customer-gadget, 
      Update chat server to use messageId of customer-gadget and agent-gadget

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. CSN-1011 Agent can't perform any action when activeMQ is down.

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. CSN-1156 Chat Server behavior on ActiveMQ failover, in this scenario

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. CSN-484 Failover -->No notification shows to agent when MRE service is down

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Re-opened

          Activity

            People

              faisal.nawaz Faisal Nawaz (Inactive)
              jawad.bokhari Jawad Bokhari
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 6 hours Original Estimate - 6 hours
                  6h
                  Remaining:
                  Time Spent - 2 days, 7 hours, 4 minutes Remaining Estimate - 1 hour, 30 minutes
                  1h 30m
                  Logged:
                  Time Spent - 2 days, 7 hours, 4 minutes Remaining Estimate - 1 hour, 30 minutes
                  2d 7h 4m