e0defcac-7cf0-4601-8e04-178a60ea74ed-image.png

@ing-joserivera26 said in VitalPBX 3:

I will not continue posting on your blog.

This is not my blog. This is an public community targeting IT professionals.

I would (and have) posted on the VitalPBX community, but it seems that i'm eternally moderated.

@JasGot said in VitalPBX / Asterisk Limit Calls Then Go To Voicemail:

@scottalanmiller said in VitalPBX / Asterisk Limit Calls Then Go To Voicemail:

We can't limit in Skyetel, or the calls won't make it to the voicemail.

My first thought would be to route calls (when their are 4 current calls) to a specific DiD that goes right to VM.

Are you working with Skyetel with custom programming or are you limited to their web portal options?

Not sure what we'd have them do to fix the issue.

I even posted a selfie.

EABA5B11-2698-43DF-AF29-6BC568FA0C10.jpeg

But my time was so rushed to catch my flight home, I didn't have time to discuss anything with him.

Found the issue and fixed it.

There were some extra entries in the default pjsip profile which were the culprit. The entries were there since quite a few versions back and hadn't caused any sort of issue with the trunks until we updated yesterday. Even after reverting to the previous working version, the trunks wouldn't get properly created until I found the extra entries and removed them. After that, the endpoints are created and the trunks are up once again.

@Romo said in Cisco SPA504G Call Reparking issue:

Totally agree, the phones suck, but they are what the client has as they didn't want to upgrade to new phones =(

Same here, we have an office full of that Cisco garbage, but hopefully we will be switching out our provider soon.

@StuartJordan NTG and CCWTech both run on VitalPBX primarily.

Typo in the port, we found it.

@ing-joserivera26 said in VitalPBX - exts can't call each other:

@JaredBusch On Next major versions of VitalPBX, the main protocol will be PJSIP instead of SIP, due as you know SIP has been totally deprecated.

Looking forward to that!

Very nice.

That’s one thing that’s seriously missing from FusionPBX!

Tagging @MontesVitalPBX

@JasGot said in Yealink will not register with VitalPBX, Wrong password:

@JaredBusch said in Yealink will not register with VitalPBX, Wrong password:

@Romo said in Yealink will not register with VitalPBX, Wrong password:

@JaredBusch The device is tied to the numeric extension, it lets you set the device's username to whatever you want.

The better question is why are you even thinking this is a good idea?

What benefit are you thinking you are gaining by using a non-standard approach?

All this does is complicate things by putting a random value in a place that is normally something that matches the extension. This is a 1 to 1 tie between this informaiton and the extension. There is no benefit to this.

Only after you've pigeon-holed yourself into that 1 to 1 relationship.

No, it is a 1 to 1 relationship regardless of if you use the extension or a name or a fuck01.

That auth name is 100% tied 1 to 1 to the extension.

@Dashrender said in What is the best workflow to setup VitalPBX:

@JaredBusch said in What is the best workflow to setup VitalPBX:

@bnrstnr said in What is the best workflow to setup VitalPBX:

@rcuadra popped back in yesterday... Maybe he could help?

Well, that was honestly why I replied here again. Also @scottalanmiller is back in the states and may have valid input as I know that he has deployed this.

Or at least set it up on the PBX side, no telling on the phone and SIP/telco access side.

Why would the phone side be any more or less difficult?

@JaredBusch said in Extensions not registering:

Fully updated FreePBX and zero issues. I use pretty much only use pjsip.
b6a3844c-2573-4763-bd7f-efce2b7603ae-image.png

This is VitalPBX, its super weird still. I didn't really touch anything on the extensions.

@JaredBusch fair enough, I haven't used the product itself as of yet and wasn't aware it had whitelisting inside the product, if this was specific to just fail2ban then that method would be suitable, but in this case I agree with you, my mistake.

@JaredBusch said in Building VitalPBX on Vultr Automatically:

@scottalanmiller said in Building VitalPBX on Vultr Automatically:

and be fully updated.

I noticed that the defualt CentOS 7 image was pretty much fully up to date before I ran the install script. Only thing that came down when I ran yum update -y was wget.

Yeah, it is more of a "just in case" something is out of date. I almost never see it not fully up to date when I fire it up.

@JaredBusch Thanks for the link. Good reading!

@JaredBusch said in Real Costs of VitalPBX:

@scottalanmiller said in Real Costs of VitalPBX:

@JaredBusch said in Real Costs of VitalPBX:

So thanks to @MontesVitalPBX we now know that the commercial addons cost 25% of purchase price for yearly maintenance.

This will let us begin to calculate the real costs of using VitalPBX.

Wow, that's not bad at all. So much cheaper than I would assume most people assume and way cheaper than I was expecting. That should be on the site because that's really good info!

Well it will be. See the other thread.

It is a fair price. It is totally acceptable. My objection was always because it was hidden.

Been chilling all weekend so not even close to caught up yet :)