Exploring VitalPBX
-
@Romo said in Exploring VitalPBX:
@rcuadra Is there a time frame of when the endpoint manager will be working with PJSIP extensions?
It would even be better if they quit using SIP as the default on port 5060. Asterisk gave up CHAN_SIP years ago.
-
@JaredBusch said in Exploring VitalPBX:
@Romo said in Exploring VitalPBX:
@rcuadra Is there a time frame of when the endpoint manager will be working with PJSIP extensions?
It would even be better if they quit using SIP as the default on port 5060. Asterisk gave up CHAN_SIP years ago.
RIP chan_sip -
@Skyetel said in Exploring VitalPBX:
@JaredBusch said in Exploring VitalPBX:
@Romo said in Exploring VitalPBX:
@rcuadra Is there a time frame of when the endpoint manager will be working with PJSIP extensions?
It would even be better if they quit using SIP as the default on port 5060. Asterisk gave up CHAN_SIP years ago.
RIP chan_sipPJSIP is still SIP, just better done and with more feature parity to other implementations of SIP.
-
Rather than create a new thread, would I be correct that any hardware that works in FreePBX also works in VitalPBX?
I have a Sangoma wanpipe card that connects into our PRI and before I break things and move to VitalPBX I'd like to know for sure that it works.
-
@WLS-ITGuy said in Exploring VitalPBX:
Rather than create a new thread, would I be correct that any hardware that works in FreePBX also works in VitalPBX?
I have a Sangoma wanpipe card that connects into our PRI and before I break things and move to VitalPBX I'd like to know for sure that it works.
Asterisk is Asterisk, and CentOS is CentOS. so yes.
-
@WLS-ITGuy said in Exploring VitalPBX:
Rather than create a new thread, would I be correct that any hardware that works in FreePBX also works in VitalPBX?
I have a Sangoma wanpipe card that connects into our PRI and before I break things and move to VitalPBX I'd like to know for sure that it works.
Curious why you're switching?
-
@Dashrender said in Exploring VitalPBX:
@WLS-ITGuy said in Exploring VitalPBX:
Rather than create a new thread, would I be correct that any hardware that works in FreePBX also works in VitalPBX?
I have a Sangoma wanpipe card that connects into our PRI and before I break things and move to VitalPBX I'd like to know for sure that it works.
Curious why you're switching?
Having hardware from Sangoma does not imply switching from FreePBX. Sangoma has made hardware for years and years before buying FreePBX from Schmooze.
-
@Dashrender said in Exploring VitalPBX:
@WLS-ITGuy said in Exploring VitalPBX:
Rather than create a new thread, would I be correct that any hardware that works in FreePBX also works in VitalPBX?
I have a Sangoma wanpipe card that connects into our PRI and before I break things and move to VitalPBX I'd like to know for sure that it works.
Curious why you're switching?
Not 100% on switching but would like to test. Before I tested it all and possibly found I liked it better I wanted to make sure the hardware I was using worked.
-
Here is my experience with Vitalpbx
I have used FREEPBX for years - minor resolveable issues.
Vitalpbx installs fast, has a clean looking GUI, has a great back up option
But all this is pointless if your PJSIP extensions won't register with hard devices such as a common Yealink T29g or a Cisco SPA 525 G2. It shows a "green" registration on the phone itself, but is not really registered. The logs indicate a problemI sent those logs to Migues with Vitalpbx. They can't figure it out. I wasted too much time trying to get it to work so I abandoned it for now. I am sure somewhere down the road they will figure it out.
In the meantime, there auto provisioning does NOT support PJSIP. Unreal! A technology like PJSIP which is quickly replacing chansip should have been first priority. They keep saying next release.
But that is pointless anyway if you can easily register a pjsip extension.My advice to those starting up or even advanced users - stick with Freepbx or even Fusionpbx (based on Freeswitch). These platforms are much more stable, reliable, dependable and have really developed pjsip as part of their infrastructure.
-
@andrewbyrd70 said in Exploring VitalPBX:
In the meantime, there auto provisioning does NOT support PJSIP. Unreal! A technology like PJSIP which is quickly replacing chansip should have been first priority. They keep saying next release.
Not quickly replacing. Replaced years ago. The fault here lies with VitalPBX. It is one of the main reasons, after the closed source crappiness, that I refuse to use it yet.
-
I have been told that this is in progress ETA end of the month (hopefully) if not end of Sept.
-
@CCWTech said in Exploring VitalPBX:
I have been told that this is in progress ETA end of the month (hopefully) if not end of Sept.
Fingers crossed, it's a big deal.
-
I tried 2 days ago to spin up a server with Vitalpbx. I am using PJSIP extensions. I should be able to call ext to ext with no sip trunks. The "green" lights on the Yealink T29g show green. BUT - when I look at the logs, it says it can not establish a route for PJSIP. I made sure that I was using port 5062 - no success
Miguel at Vital suggested I not use any special characters in my passwords even though their own documentation says to use special charactors. I tried that. No success.
I spend too many hours trying to get it to work.
-
@andrewbyrd70 said in Exploring VitalPBX:
I tried 2 days ago to spin up a server with Vitalpbx. I am using PJSIP extensions. I should be able to call ext to ext with no sip trunks. The "green" lights on the Yealink T29g show green. BUT - when I look at the logs, it says it can not establish a route for PJSIP. I made sure that I was using port 5062 - no success
Miguel at Vital suggested I not use any special characters in my passwords even though their own documentation says to use special charactors. I tried that. No success.
I spend too many hours trying to get it to work.
not sure where we have a T29G, but we have several series of Yealinks and no issues with PJSIP on VitalPBX.
-
That is a really old phone, but should work just fine. Are you sure everything was setup correctly within VitalPBX?
Devices do not know anything about the channel driver used by the server.
-
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 . . . )
I compare it to Freepbx - I can register pjsip extensions with Cisco SPA525g2 and with Yealinks (any model) without issue.
On the phone side (yealink T29G) I enabled the account, typed in the IP address, changed default port of 5060 to port 5062, hit confirm
I loaded Vital from ISO once, and then tried reinstalling with the Centos script from Github. One thing I noticed was with ISO, I had some network settings pre-installed and populating. With the script it said that the network was not installed.
-
@JaredBusch said in Exploring VitalPBX:
That is a really old phone, but should work just fine. Are you sure everything was setup correctly within VitalPBX?
Newer than mine, I have the T38G. LOL
-
@andrewbyrd70 said in Exploring VitalPBX:
If I added a trunk, I could dial outboutn no issues, just no inbound or ext to ext
That tells you that the extension is registered and working and that PJSIP or the phone connection cannot be the problem. That's a real issue, but nothing like you are picturing that it is.
-
@andrewbyrd70 said in Exploring VitalPBX:
On the phone side (yealink T29G) I enabled the account, typed in the IP address, changed default port of 5060 to port 5062, hit confirm
It definitely worked since you were able to make calls.
-
That is true. But ext to ext would go straight to the extensions VM
