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.

@JaredBusch said in Extensions not registering: Fully updated FreePBX and zero issues. I use pretty much only use pjsip. 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

Full PDF of plan comparison https://vitalpbx.org/wp-content/uploads/2019/03/ENG_VitalPBX-Plans-Web.pdf Oh look WP link. Lazy....

@Dashrender said in VitalPBX Sonata Suite: I'm with JB on this one. Assuming that 1 additional year of support costs the same as the original purchase, they could solve this whole bit by simply stating, yearly maintenance is the same cost. Oh it would be nice to state that there is no pricing that isn't listed. But you have to admit, it's slightly odd as a thought process to have to state the lack of things that don't exist.

@Romo said in Exploring VitalPBX: @JaredBusch What other issues did you see? I do not recall the detail, but things were missing. Probably related to the remote address book. Not something FreePBX handles either. Just something here also missing. I spent at most 60 minutes going through the screens and settings. I never fuly brough the system into a functional state. It was also weeks ago. It is hard to recall. That said, I spun a new instance up this morning. I plan to actually bring this one all the way to fully operational.

Gotcha - thanks for the feedback