I typically handle those integrations with highly integrated workflows into Amazon by using the Route 53 load balancer to route traffic between all services.

The integrations for my main use case are set up using Terraform, which then creates the infrastructure on Amazon.

VICIbox & VICIdial for AWS EC2 has impacted my organization positively by being used for company broadcasts with one-directional channels for people to visualize updates from the company channel without more interaction.

This setup has helped with efficiency, reach, and saved the team resources by enabling us to reach a larger audience.

I don't have any additional comments about needed improvements or features I'd like to see in the future.

I did not purchase VICIbox & VICIdial for AWS EC2 through the AWS Marketplace, as I'm not responsible for that decision.

On a scale of 1-10, I rate VICIbox & VICIdial for AWS EC2 a six.

My main use case for VICIbox & VICIdial for AWS EC2 is setting up a small contact center for a client who wanted to have 10 to 20 agents onboarded to their company and start a contact center.

The best features that VICIbox & VICIdial for AWS EC2 offers include a free SSL certificate, and we can have a UI where the first user login is pretty simple.

The pre-installed SSL certificate and the simple user login helped me because I do not have to purchase a different SSL certificate for end security. We just need to point our domain to a static IP and then run a service as root. We can also use a simple 6666 username and go to our IP address or domain and log in with that username.

VICIbox & VICIdial for AWS EC2 includes built-in tools that enhance the user experience. One example of these features includes the ability to use the ISO.

VICIbox & VICIdial for AWS EC2 has positively impacted my organization by being quick, efficient, and it does not require many separate installations on EC2, making the stack pretty simple.

VICIbox & VICIdial for AWS EC2 could be improved by integrating dial-in software within the UI pop-up so that we can access it immediately on the user interface first page.

In terms of needed improvements, reporting would be beneficial for VICIbox & VICIdial for AWS EC2. I would appreciate having reporting features such as PDF versions of reports, number of calls, average handle time, and related metrics.

I have used VICIbox & VICIdial for AWS EC2 for around two years, but not in this company, in my previous roles and for personal projects.

In my experience, VICIbox & VICIdial for AWS EC2 is stable; I have not seen any downtimes.

VICIbox & VICIdial for AWS EC2's scalability is definitely strong, as it can handle growth easily.

I previously used Five9 for other clients.

For that contact center project, I had to spin it through EC2 and then configure the roles and services needed. I first needed to SSH and then do either express setup or standard setup. I went with the express setup which quickly let me set up the software.

My setup experience includes the fact that it has quite low port usability, which is just two to three or four ports. It uses 50-60 UDP, which gives flexibility for the projects.

I went with a direct setup for VICIbox & VICIdial for AWS EC2, without purchasing through any marketplace.

I have seen a return on investment from using VICIbox & VICIdial for AWS EC2, as it definitely saves time and requires fewer employees, but I am not sure about revenue because that's something handled by a different team.

Pricing, setup cost, and licensing for VICIbox & VICIdial for AWS EC2 is handled by a different team.

I have not evaluated other options before choosing VICIbox & VICIdial for AWS EC2 because this is handled by another department.

The efficiency and quick setup benefited my project as it saved time because there were no complex tools needed to be installed and just a simple UI to go in and log in as a master user and then we can provide access to our agents.

My advice for others looking into using VICIbox & VICIdial for AWS EC2 is to first check if they need a very big environment with more than 20,000 agents. They can go for different options in such cases. If it's quick and they need it for a smaller amount of people, it's definitely worth considering.

Go, go VICIbox & VICIdial. Anyone can dial. Goodbye.

On a scale of 1-10, I rate VICIbox & VICIdial for AWS EC2 an 8.

Our main use case for VICIbox & VICIdial for AWS EC2 is to set it up for server purposes, which is working as a backend, and in some cases, we have configured ASA firewall on the particular EC2 for intercommunication.

In our daily workflow with VICIbox & VICIdial for AWS EC2, we have configured it as an ASA firewall, so whenever traffic is coming from the internet, it is being verified by the firewall before going to the backend server. In some cases, we are also using AWS EC2 as a server to run a particular website or something.

The best features of VICIbox & VICIdial for AWS EC2 that I have seen are good scalability and open source flexibility, though I have an issue with the visualization of the portal itself, as compared to Azure, where I can see all configured resources in one page; in AWS, I have to select specific regions to view resources, which I don't prefer.

Using AWS EC2 and related tools such as VICIbox & VICIdial has impacted my organization positively; however, I'm new to this particular project and have only been using it for four months, so I might give a proper response after a few months once I have a better understanding of VICIbox & VICIdial in my team's usage.

From my perspective so far, the only improvement needed for AWS EC2 and related solutions such as VICIbox & VICIdial is with the visualization portal, which I find quite complex.

The only problem I have with VICIbox & VICIdial for AWS EC2 is the portal visualization complexity; apart from that, everything is good.

We have been using Amazon EC2 for the last five years, but I am using VICIbox & VICIdial for AWS EC2 in that particular project for around four months.

We haven't faced any issues while running instances on AWS EC2 with VICIbox & VICIdial for AWS EC2; personally, I haven't seen any issues in the last three to four months, though my team might have faced something.

In my experience, VICIbox & VICIdial for AWS EC2 is stable.

The customer support for AWS EC2 and related solutions has been good; I would rate it a nine out of ten because, while everything is satisfactory, no one is 100% perfect.

Positive

Initially, we used an on-prem solution before switching to AWS and Azure both, a decision made by the management team for load balancing, due to accessibility, scalability, and easy access to resources from anywhere, thus facilitating our move to the cloud.

We have seen a return on investment with AWS EC2 and related solutions such as VICIbox & VICIdial. We are running it as a back-end server for a particular project, and since it is running smoothly, the company is profiting, demonstrating a solid return on investment.

My experience with pricing, setup cost, and licensing for VICIbox & VICIdial for AWS EC2 is that it totally depends on the project requirements; while Azure may be good for specific needs, AWS could be suitable for others, emphasizing that both Azure and AWS have their strengths based on project management and budget.

We have evaluated Azure before choosing VICIbox & VICIdial for AWS EC2, after which management decided on our current path.

If you are using VICIbox & VICIdial for AWS EC2, then it must be through the AWS Marketplace.

My advice for others looking into using VICIbox & VICIdial for AWS EC2 is to compare both Azure and AWS, allowing the individual to determine which better fits their project requirements.

On a scale of one to ten, I rate VICIbox & VICIdial for AWS EC2 an 8.5.