Exploring VitalPBX
-
Ah, that's a good test, too. What I was meaning though was have two extensions dial into a conf room and see if they can talk that way.
-
@andrewbyrd70 said in Exploring VitalPBX:
Yes, I am - I went to the extensions tab, created new ext 1001, selected PJSIP, , saved, and my key turned green. If I added a trunk, I could dial outboutn no issues, just no inbound or ext to ext
The logs when I tried to dial ext to ext or inbound said, "could not create pjsip route . . . )
This right here means you have something misconfigured in your firewall most likely.
-
@andrewbyrd70 said in Exploring VitalPBX:
He knew they showed registered (green)
Stop saying this. This means nothing.
-
@JaredBusch I am using Vultr VPS - no firewall issues. I have 10 vps servers with Vultr running Freepbx for different clients. Never had a firwall issue thus far.
-
This post is deleted! -
@andrewbyrd70 said in Exploring VitalPBX:
@JaredBusch I am using Vultr VPS - no firewall issues. I have 10 vps servers with Vultr running Freepbx for different clients. Never had a firwall issue thus far.
FreePBX uses a different firewall than VitalPBX does. They use the same IPS, but different firewall styles. VitalPBX uses a plain firewall, and FreePBX uses responsive. They behave differently.
-
@andrewbyrd70 said in Exploring VitalPBX:
@JaredBusch I am using Vultr VPS - no firewall issues. I have 10 vps servers with Vultr running Freepbx for different clients. Never had a firwall issue thus far.
Bzzt wrong answer.
Which way is the problem? Inbound. This typically means you have something configured wrong either on the inbound router, or the endpoint itself.
-
@scottalanmiller said in Exploring VitalPBX:
@andrewbyrd70 said in Exploring VitalPBX:
@JaredBusch I am using Vultr VPS - no firewall issues. I have 10 vps servers with Vultr running Freepbx for different clients. Never had a firwall issue thus far.
FreePBX uses a different firewall than VitalPBX does. They use the same IPS, but different firewall styles. VitalPBX uses a plain firewall, and FreePBX uses responsive. They behave differently.
That he registers means the problem is not on that side firewall.
-
-
I love your sense of humor Scott - Going to get a beer now
-
First, you need to figure out WTF you are doing wrong.
VitalPBX is Asterisk. Asterisk has all the answers.
First show the registratoin info.
rasterisk -x "pjsip show aor 1001"or
asterisk -rx "pjsip show aor 1001" -
and this
rasterisk -x "pjsip show endpoint 1001" -
OR I could just stick with what has worked for the past 5 years - FREEPBX. I am all about ease of setup and use.
It Vitalpbx wants me to change multiple settings and dance on one foot to get their product to work I don't need it. I can fire up a Freepbx server right now and have it working and ready to go in half an hour or less.
The only reason I explored Vitalpbx is for a client for multi-tenant.I do thank you for the suggestions, criticisms and insights though. You gave this to me freely and I do appreciate that - I really do.
-
@andrewbyrd70 said in Exploring VitalPBX:
The only reason I explored Vitalpbx is for a client for multi-tenant.
While they support that, I'm not sure that it looks very interesting. FusionPBX is way more interesting for that kind of functionality, IMHO.
-
@andrewbyrd70 said in Exploring VitalPBX:
OR I could just stick with what has worked for the past 5 years - FREEPBX. I am all about ease of setup and use.
It Vitalpbx wants me to change multiple settings and dance on one foot to get their product to work I don't need it. I can fire up a Freepbx server right now and have it working and ready to go in half an hour or less.
The only reason I explored Vitalpbx is for a client for multi-tenant.I do thank you for the suggestions, criticisms and insights though. You gave this to me freely and I do appreciate that - I really do.
If you think FreePBX was easy the first time, then you have rose colored glasses on. take them off.
FreePBX is certainly not simple or straight forward to get right for a beginner.
Honestly, IMO, VitalPBX and FreePBX are about the same in that regard. The VitalPBX GUI is tons more friendly, but the settings and options are the same in both systems.
-
That said, I'm not a multi-tenant guy, I'm a single tenant engineer these days. So maybe Vital does something great there, but building multi-tenant on Asterisk seems like a nightmare.
-
@scottalanmiller said in Exploring VitalPBX:
@andrewbyrd70 said in Exploring VitalPBX:
The only reason I explored Vitalpbx is for a client for multi-tenant.
While they support that, I'm not sure that it looks very interesting. FusionPBX is way more interesting for that kind of functionality, IMHO.
Correct. I would never recommend any thing base don Asterisk for a multi-tenant deployment. It was never not designed for it.
-
@scottalanmiller said in Exploring VitalPBX:
That said, I'm not a multi-tenant guy, I'm a single tenant engineer these days. So maybe Vital does something great there, but building multi-tenant on Asterisk seems like a nightmare.
It is all prefixing. Nothing special, but crazy to maintain.
-
I agree that Fusionpbx is a better multi-tenant solution. I have a server with Vultr running Fusionpbx and has for over 6 months with very little issues. It went into production 3 months ago and has been a great solution for 3 of my clients. Just my 2 cents. . . .
-
Closed source is my #1 complaint about VitalPBX.
This is why:
I absolutely use custom contexts on almost all systems. Typically only one or two simple things. But they are things that make Asterisk so much more friendly IMO.
Asterisk is open source, and the structure of adding custom dialplan into contexts is freely available. But VitalPBX locks this out by not having a way to include custom contexts by default.
Examples of some I use with this
pjsip send notify:
Reload, but do not reboot a Yealink Phone:[reload-yealink] Event=>check-sync\;reboot=falseForce reboot a Yealink Phone
[restart-yealink] Event=>check-sync\;reboot=trueSend a command to a Yealink phone to turn on DND
[dndon-yealink] Content-Type=>message/sipfrag Event=>ACTION-URI Content=>key=DNDOnSend a command to a Yealink phone to turn off DND
[dndoff-yealink] Content-Type=>message/sipfrag Event=>ACTION-URI Content=>key=DNDOffSend a command to a Yealink phone to factory reset it
[default-yealink] Content-Type=>message/sipfrag Event=>ACTION-URI Content=>key=ResetThat does not even get into simple basic custom dialplan for actual call routing things.
