AWS VICIdial Cluster Configuration

进行中 已发布的 4 年前 货到付款
进行中 货到付款

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.

Asterisk PBX Amazon Web Services Linux 系统管理

项目ID: #23914338

关于项目

4个方案 远程项目 活跃的4 年前

授予:

cristaor

Hi I have more than 15 years of experience installing Call Centers in America (Latin and USA). I have installed several Open Source platforms (Asterisk, elastix, FreePBX, Freeswitch, Vicidial), solved and fixed proble 更多

$430 USD 在5天内
(5条评论)
4.6

有4名威客正在参与此工作的竞标,均价$545/小时

NinjaWebCorp

Ok let me see if I understand. - As you mentioned, you are raising all services in EC2. - You have load balancers in instances - Database is RDS And of course, the process are going high at some point that server has 更多

$750USD 在1天里
(38条评论)
6.2
ranumehta2017

***system admin*** 更多

$500 USD 在7天内
(36条评论)
5.2
mgeorgiev13

Dear Employer, I can help you with your AWS diagnostic, monitoring and discovering the faced issue. I have extensive experience with: - Public and Private Cloud infrastructure design, migration (from/to), implementati 更多

$500 USD 在3天内
(15条评论)
5.0