AWS VICIdial Cluster Configuration.

Closed Posted 4 years ago Paid on delivery
Closed Paid on delivery

I have a multiserver vicidial cluster setup on AWS which encounters a handful of issues once upwards of 50+ simultaneous users are logged in and autodialing 100+ lines. In fact, the odd part is this is the only point at which the system begins to demonstrate the error (the reason i'm making this post).

Our current configuration is the following:

1 - DB instance

1 - Primary calling server A (which is configured to include 2 load balancing only asterisk instances. 1/3 of agents register softphones and use this as a webserver)

2 - Primary server A load balancing dialer instances ( agent webphones are registered on calling server A. These two instances do not have registered SIP softphones for agents.)

1- Secondary calling server B (which does not part of the load balancing. 1/3 of agents register soft phones and use as web server)

1 - Third calling server C (which does not part of the load balancing. 1/3 of agents register soft phones and use as web server)

all using:

VERSION: 2.14-715a

BUILD: 190705-1012

© 2019 ViciDial Group

To describe the issue as best as possible: inbound/outbound blended calling is seamless with 40 users registered and taking calls while the asterisk is ratio calling between 70 to 100 lines simultaneously. The issue is triggered by the following: 20 additional users are registered and ready for calls and 120 to 150 lines are dialing. There is a point which agent wait time begins to increase from seconds to minutes between ACD. The UI will display 50 agents ready with dialing 150 numbers and yet, a handful of calls are served every minute translating to 3 to 5 minutes between call distribution.

Consider the following changes and still encounter the same issue:

- I have tried using multiple SIP carriers

- increased and decreased trunks per server and calls per second

- optimized the DB settings for high load dialing

-had all agents logged into a single and several dialer instances with the same issue

-increased server size ( we are using T3-2xlarge on all instances and doesnt even max at 15% utilization )

-Tried variations of Max FILL grouping and trunk caps with and without LB

Hopefully i can find somebody whos more capable with cluster systems using vicidial. I have no other ideas on how to trouble shoot this.

Amazon Web Services Asterisk PBX System Admin Linux

Project ID: #23914369

About the project

5 proposals Remote project Active 4 years ago

5 freelancers are bidding on average $162 for this job

bindmission

Hello Hope you are doing well. I have 7 years of experience in Asterisk and VoIP. I can handle this project. Regards VishnuLal*

$200 USD in 1 day
(174 Reviews)
6.3
vinskendaj

greetings i think that its not a problem with the carriers, and ive seen this issue before. ive done a couple of scripts to work around it, there was no other way. lets have a chat over it and we can decide if my s More

$111 USD in 2 days
(34 Reviews)
5.4
ranumehta2017

***AWS EXPERT*** More

$200 USD in 2 days
(30 Reviews)
4.7
otrzemvoup

I have 10 years of experience working as a tier-2/NOC agent for a VoIP company in the US, I'm not quite familiar with this Vicidal software, but apparently it runs on top of Asterisk, and your servers A, B, C are Aster More

$100 USD in 5 days
(1 Review)
1.3