[ASTPPCOM-1254] voice broadcast - call not working as per CC Created: 06/Oct/22  Updated: 12/Oct/22  Resolved: 12/Oct/22

Status: Closed
Project: ASTPP Community
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Highest
Reporter: Bhavyata Raval (Inactive) Assignee: Ashish Gohil
Resolution: No Change Required Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 3h 40m
Original Estimate: Not Specified

Attachments: PNG File 13 calls.png     PNG File 22 csv.png     File 23.mp4     PNG File cc calls.png     PNG File Screenshot from 2022-10-07 19-28-01.png    
Issue Links:
Blocks
blocks ASTPPCOM-982 Voice Broadcasting[Only for Admin] To Do
Reproducibility: always
Category: Functional
Edition: Community

 Description   

steps to reproduce:

  1. login as admin
  2. add 10 CC calls in one customer
  3. create one broadcast with more than 10 records
  4. now go to cdrs and check more than 10 call entries display

expected result: call should be working as per CC 

check attachment to reproduce 



 Comments   
Comment by Alpesh Kaklottar [ 07/Oct/22 ]

Look like there is some misunderstanding in CDRs verification, at the same time 10 calls were success and 2 were failed. See screenshot. 

Comment by Bhavyata Raval (Inactive) [ 11/Oct/22 ]

customer : 20 cc calls, csv : 22 records , calls originate = 13

please check recent attachment.

expected result: call should be originate 22

Comment by Ashish Gohil [ 12/Oct/22 ]

Hello Bhavyata Raval, can you please check on live call?
whenever you call then call will execute as i set 2 call at a time then it will sleep for 2 second and after call cut then it will not getting switch congestion.  so it will run the call.

if you add 50 records in csv it doesn't mean that it runs 50 calls at a time.

So Please check on live call or logs there you can check how many calls run at a time.

please let me know if anything.

Comment by Bhavyata Raval (Inactive) [ 12/Oct/22 ]

verified in latest,

working fine 

Generated at Sat Feb 10 07:24:29 CET 2024 using Jira 8.13.3#813003-sha1:22ebedbb75c99b147c66f14e031dd8a2d214753a.