Exploring VitalPBX
-
@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
-
@andrewbyrd70 said in Exploring VitalPBX:
That is true. But ext to ext would go straight to the extensions VM
Sure. But since the extension is known to be working, we know for certain that the issue is in the ext to ext routing and can't be with PJSIP or the extension itself.
-
Something to note:
I went to the Vitalpbx GUI - PBX - Extension Status
1001 - showed unavailable
1002 - showed unavailableyet, they both could make outbound calls - Just could not receive calls nor call ext to ext
-
@andrewbyrd70 said in Exploring VitalPBX:
yet, they both could make outbound calls - Just could not receive calls nor call ext to ext
Routing issue
-
When I explained this to support at Vitalpbx (Miguel) he told me:
-
Change your password on your extensions ???????? I did it anyway to no avail
-
Said to change my qualify settings on the sip devices ??????
My confidence level in his knowledge of this issue lowered with each response.
-
-
@andrewbyrd70 said in Exploring VitalPBX:
When I explained this to support at Vitalpbx (Miguel) he told me:
-
Change your password on your extensions ???????? I did it anyway to no avail
-
Said to change my qualify settings on the sip devices ??????
My confidence level in his knowledge of this issue lowered with each response.
Well, if you want to have zero confidence, talk to the FreePBX creator. Literally the second most incompetence IT person I've ever spoken to (after the famous VCR "programmer" guy.)
When you spoke to Miguel, did you tell him that the extensions were not registering, or did he know that they were working and try that anyway?
-
-
This post is deleted! -
@andrewbyrd70 this is why people like Jared and I get lots of PBX support calls
-
@andrewbyrd70 said in Exploring VitalPBX:
@scottalanmiller Yes, I told him all the information I just told you. He knew they could dial out. He knew they showed registered (green) on the sip phone. He probably just didn't know what to do.
Then yeah, that's not good support.
-
@andrewbyrd70 one thing I do for a lot of testing is to dial into a conference room.
-
@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.
-
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.
