Posts made by MontesVitalPBX

@JaredBusch Hey, sorry I never got the email for this mention. We are looking into your post, but cannot find it. It appears that your account was not verified So that is why moderation was needed, but we weren't able to find your post. I have gone ahead and verified your account so you should be able to post once again. Now, it would be good if you can try again, so we can solve it, and continue running your issues on the VitalPBX forum so our support and dev team can take a look into it.

@JaredBusch said in Exploring VitalPBX:

@MontesVitalPBX said in Exploring VitalPBX:

Hello MangoLassi users! This is Jose Montes, Channel Manager for VitalPBX. I was contacted by @FATeknollogee and @scottalanmiller about this forum thread and decided to chime in, and it seems there has been an interest on VitalPBX over here. That makes us at VitalPBX very happy! If you got any questions, you can shoot us an e-mail to [email protected]. I am not the fastest forum thread responder, but I try my best!

As it is a US holiday, you will do well to check back in tomorrow, and follow up daily at least.

I've already deleted the test instance I made yesterday. But I will be making a new instance and actually doing a full turn up and making calls.

There are definite shortcomings in the EPM that I have already noted in just my 30 minutes of poking around the now deleted instance.

We are working on updating the EPM to a new and better version. This is part of our roadmap for this year.

There are many tutorials available on our blog that show you how to do various things with VitalPBX. Be sure to check it out, as there might be a tutorial that any of you might be interested in.

@JaredBusch said in Exploring VitalPBX:

@MontesVitalPBX said in Exploring VitalPBX:

@JaredBusch said in Exploring VitalPBX:

@MontesVitalPBX said in Exploring VitalPBX:

But if you are using a VPS, then the script is your best source.

Nothing on your site tells me I need to use a CentOS 7 base VPS instance.

We obviously looked. But if I go here and click this.

I end up on github. and nothing states I need CentOS 7.

3 seconds looking at your shell script makes it obvious to experienced people.

We got the information on our blog where it shows you how to install on different VPS services like Amazon AWS and Google Cloud. This would work the same on services like Vultr.

Yes, but that is not the point. Your blog is not the linked set of instructions.

OK, I'll have the instruction of a CentOS 7 installation needed added on the GitHub.

@JaredBusch said in Exploring VitalPBX:

@MontesVitalPBX said in Exploring VitalPBX:

If you don't pay the fee, you can still use the add-on for life, no problem, just not with the latest update.

This is the same model as FreePBX and FOP2. People will understand and accept this. But it has to be known.

I have already advised the web development team about it.

@JaredBusch said in Exploring VitalPBX:

@MontesVitalPBX said in Exploring VitalPBX:

But if you are using a VPS, then the script is your best source.

Nothing on your site tells me I need to use a CentOS 7 base VPS instance.

We obviously looked. But if I go here and click this.

I end up on github. and nothing states I need CentOS 7.

3 seconds looking at your shell script makes it obvious to experienced people.

We got the information on our blog where it shows you how to install on different VPS services like Amazon AWS and Google Cloud. This would work the same on services like Vultr.

@JaredBusch said in Exploring VitalPBX:

I also made a thread specifically about the plans..

Including a link to the full PDF comparison document.

In absolutely no location do you mention the recurring costs for add on renewals.

The Enterprise plan mentions "always up to date", but that is a larger purchase and then $50/month.

Those are the VitalPBX Plans, which is a different program than purchasing individual licenses. The VitalPBX Plans gives you access to all of the commercial modules at once, the difference between the Enterprise and Carrier being the number of tenants you can create.

@JaredBusch said in Exploring VitalPBX:

@MontesVitalPBX said in Exploring VitalPBX:

@JaredBusch When purchasing the commercial modules, it is a one-time payment. The only recurring payments are for the Licensing Subscription Plans, which can be paid monthly or yearly. You can learn more about the plans at the Plan Page on our website.

Every single one of your commercial modules clearly states that it only gets updates for 1 year.

What is my cost to get updates after 1 year?

I made a thread about it

I'll have the web development team make that more clear. After a year, you pay a maintenance fee for the latest version when that time comes, which is 25% of the cost of the commercial add-on. If you don't pay the fee, you can still use the add-on for life, no problem, just not with the latest update.

@JaredBusch I will let the web development team know your feedback!

@JaredBusch When purchasing the commercial modules, it is a one-time payment. The only recurring payments are for the Licensing Subscription Plans, which can be paid monthly or yearly. You can learn more about the plans at the Plan Page on our website.

Hello MangoLassi users! This is Jose Montes, Channel Manager for VitalPBX. I was contacted by @FATeknollogee and @scottalanmiller about this forum thread and decided to chime in, and it seems there has been an interest on VitalPBX over here. That makes us at VitalPBX very happy! If you got any questions, you can shoot us an e-mail to [email protected]. I am not the fastest forum thread responder, but I try my best!

From the thread, I can see the following concerns:

1. Why we promote the ISO more, rather than the installation script?
   a) We find the installation process with the ISO the easiest for most users since it installs CentOS 7 and Asterisk, along with the VitalPBX application. You just follow the common CentOS 7 installation screens, and at the end of the process, VitalPBX is installed. This is perfect for Virtual Machines and dedicated servers. But if you are using a VPS, then the script is your best source.

2. Ombutel and VitalPBX.
   a) Yes, VitalPBX originally was known as Ombutel. Ombutel compared to VitalPBX was a smaller more basic project, and with the name change, we have expanded the features a lot. You can learn more about VitalPBX with its Ombutel origins at our blog, with our letter to Ombutel followers, and a blog post about the name change.

3. Add-Ons.
   a) Given the practices of various competitors, there seems to be a doubt on what is free and what is not. VitalPBX comes as a full PBX system out of the box. All of the features we consider essential of a PBX come already available in VitalPBX. From IVR, Conferences and CDR to Class of Service and more. Our commercial add-ons are modules that expand or complement to what is available or what is possible in VitalPBX. We just posted on our blog about installing, updating, and licensing our add-ons. You can test all of the commercial add-ons with no time limit or feature limits. You are only limited by the number of objects you can make on the unlicensed modules. For example, on the Multi-Tenant module, you can create a fully featured tenant but are only limited to one.

4. FREE.
   a) Yes, VitalPBX comes with a free version that you can use even commercially if you want to want to sell a server with VitalPBX installed, for example. Our Commercial Model is based on commercial Add-ons, Support, and other services like the White Label program. We also offer some licensing subscription plans, so you can have access to multiple commercial add-ons on VitalPBX. You can see everything that is commercial at our store page on our website. You might find that the Free version is sufficient for you, but you might also want to expand your PBX with additional modules. We find that this is the most comfortable option for most of our customers and users. No, we don't sell any data. We leave that to the Zuck.

MySQL root user comes in default without a password since it is used to create local connections only. MySQL is not exposed to the network, so the only way the DB might be intruded is if someone got the console root password somehow. So be careful when leaving the prototype iPhone at a bar!

I will be here for the next hour, so I might be able to respond to other questions in the thread. If I don't respond fast enough, remember you can send an e-mail to [email protected] and we will get back to you as soon as possible.

By the way, there are Webinars and Training Courses coming soon for VitalPBX users, so be sure you are subscribed to our newsletter!