Posts made by andrewbyrd70

No. I probably won't for a very long time due to the number of bugs. Freepbx has far fewer bugs for me and causes me less stress and headaches

@andrewbyrd70 I did know that by enabling RTP symmetric that fixes a one-way audio issue. I have figured that one out last year. But I never knew to enable rewrite contact. I think in previous versions it came enabled by default and that's why this confused me this go around. Thank you again

@JaredBusch what I am fascinated by is you in a matter of minutes were able to find the issue and resolve the issue. Their own tech support guy after receiving more information from me than you did never ever suggested that. He suggested password changes with no special characters. He suggested things that have absolutely nothing to do with the problem. Again my confidence level and their support is very low at this moment. maybe you need to be my tech support guy? Thank you so much for investing your time in this.

@JaredBusch Something has changed. On previous versions of vitalpbx you could spin it up and instantly connect without showing the internal IP. In the most current version 2.3.6 something change to where something has to be adjusted. Where would I go in vitalpbx to fix this?

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. . . .

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.

I love your sense of humor Scott - Going to get a beer now

@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.

@scottalanmiller Funny you should say that - I changed the routing of the incoming DID # to forward to my cell phone. That worked fine. I just could never get ext to ext or DID to an ext to work.

When I explained this to support at Vitalpbx (Miguel) he told me:

1. Change your password on your extensions ???????? I did it anyway to no avail

2. Said to change my qualify settings on the sip devices ??????

My confidence level in his knowledge of this issue lowered with each response.

Something to note:

I went to the Vitalpbx GUI - PBX - Extension Status

1001 - showed unavailable
1002 - showed unavailable

yet, they both could make outbound calls - Just could not receive calls nor call ext to ext

That is true. But ext to ext would go straight to the extensions VM

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.

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.

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 problem

I 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.