/
Copy of L2 and suppression conflict

Copy of L2 and suppression conflict

Nov 04, 2019

Scenario occurs when using L2 resilience and Call Suppression features:

1.    Duplicate calls, call1 and call2, are being processed.
2.    A user makes an API request to call2 to suppress the call.
3.    call2 is suppressed, call1 is not.


When an API request is used to suppress a call, the calling application should not need to have knowledge that this call is being recorded in duplicate but both calls should be treated identically.


Business Case Summary

  • Currently when duplicate calls are captured from the L1 and L2 collector (Call 1= L1 collector, Call 2= L2 collector) and processed for deduplication. If the user has made a suppression request on a call captured from the L2 collector during deduplication the same call captured from the L1 collector will not be suppressed. We need a solution that ensures calls captured are suppressed upon a Suppression request by the user during the deduplication process. 


1.

Use Case Title:
[L2 and RoD conflict]
Description To ensure the user's suppression request on call is achieved during the deduplication process for PCI DSS compliance(Payment Card Industry Data Security Standard).  
Trigger Customer triggers RoD request to suppress a  call.
Primary Actors (Personas)


Secondary Actors 
Stakeholders 


Preconditions 
  • Customer has Suppression licence
  • Suppression permissions 
Flow (Main success Scenario)

Scenario 1 

  • Pre-call a user makes an RoD request to suppress a call captured on L2 collector but not L1 collector 
  • Call is captured by L2 and L1 collector (Call 2= L2 collector and Call 1= L1 collector)

Scenario 2 

  • Pre-call a user makes an RoD request to suppress a call captured on L1 collector but not L2 collector 
  • Call is captured by L2 and L1 collector (Call 2= L2 collector and Call 1= L1 collector)
Alternative flows[Document alternate flows and exceptions to the main success scenario. Extensions are branches from the main scenario, and numbering should align with the step of the success scenario where the branch occurs]
Post-conditions 

Post-Call (After calls are captured by L2 and L1 collector)

  1. Success End condition: 

    During deduplication call captured by L1 collector and L2 collector are suppressed as requested by the user.  

  2. Failure End condition:

    Assumptions: We assume the solution will not produce a failure event because based on the logic. However possible errors due to enhanced exceptions in code which will be picked up by QA. 

Frequency 

Dependent on customer request

Priority MUST have 
Technical SpecificationCall Suppression - tech spec#techspec-L2resilienceandsuppression
Add label