Exploring VitalPBX
-
@JaredBusch I will let the web development team know your feedback!
-
@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 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.
-
@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.
-
@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'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.
-
@MontesVitalPBX said in Exploring VitalPBX:
@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'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.
More clear than hidden is not hard..
-
@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.
-
@MontesVitalPBX said in Exploring VitalPBX:
@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.
I realize that. But it was the only location where recurring costs were ever mentioned.
-
@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.
-
@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:
@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.
-
@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.
-
@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.
-
@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.
-
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:
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.
-
Start to LE cert installed on a Vultr $5 CentOS 7 image was 18 minutes form Vultr instance creation email to VitalPBX registration email.
Spent at least 5 minutes in there replying to a couple posts. So more like 10 minutes.
-
Interesting default choice they made here. No hint means no BLF functionality
-
This is useful to have someplace easy to find.
-
Is there no default music on hold?
