I've been playing with the beta 2.3.7 version on my cloud instance. It's pretty slick. There is a learning curve to figure out where all the things you want live in the menu tree but once you figure it out, its just as easy as FreePBX. I found setting up trunks using chan_sip was quite straight forward. I still avoid pjsip like the plague so I haven't tried that. Overall the former Xorcom turned Ombutel turned VitalPBX is quite slick. Here are my observations so far:
1) To do a GUI based custom context (equvalent to FreePBX custom destinations), they want you to download a commercial custom-context module for pay. There is a workaround to create their equivalent of an extensions_custom.conf but I had to research it on their forums and haven't tried it yet.
2) Not all configs are in the /etc/asterisk directory. Their is an ombutel subdirectory with a lot of special config files for their application. Don't hope that you can use your FreePBX /etc/asterisk/*conf files on VitalPBX.
3) Ring groups are a little different because if you include an external number in them, you can't set it to ask the external recipient if they want to push 1 to accept, 2 to reject. So if your external number is a cell phone that is out of range, it will dump to the cell phone voicemail. I was able to get around that by using the extension follow-me settings and point the DID directly at the extension. Then it will ask the external recipient to accept the call. Also on follow-me, it plays a recording that you are not at your desk and that it will try to locate you as it moves to the follow-me ring group.
4) It will not install and run on Hosting73 Centos-7 64-bit. Asterisk and VitalPBX work but the same issue occurs with Fail2ban not starting and iptables not running. Installing Ward's TM3 fixes the firewall but you will have to tinker further to disable auto-startup of Fail2ban and the firewalld service. You also have to set iptables to auto-start.
5) VitalPBX supports class-of-service so you can create restriction groups to limit calling and feature access. A definite leg-up over standard FreePBX features. This gives you great flexibility per extension and gives features more like a proprietary PBX like Avaya or Nortel systems. You can restrict outbound routes (say deny toll calling to employee's who don't need it, etc.)
6) There is out-of-the-box support for opencnam caller-id lookups but, alas, no CIDSuperfecta at this time.
7) There is an odd boss/secretary mode that simply routes all the boss calls to the secretary and only the secretary can directly ring the boss. Still no bridged call appearances on Asterisk.
8) It allows you to set up gmail as your smarthost for mail directly from the GUI. No downloads, makefiles or anything requiried.
9) There is built-in security for firewall, whitelists, services, etc. directly from within the GUI.
10) There is a built-in endpoint manager that supports a large variety of manufacturers and their products. I was happy to see most of the older Aastra/Mitel sets supported.
That's all I've uncovered so far. The system is stable and professional. Now we need to see what Ward's big brain can do to bring the enchilada experience to VitalPBX.