After installing SNG7-PBX-64bit-1805-1 and FreePBX-64bit-10.13.66 multiple times last night, I think the issue is related to EFI.
Every time that I installed, I followed the following minimal setup script:
- Installed with all default options
- Skipped past all of the initial Sangoma offers
- Did NOT enable the firewall
- Created new PJSIP extension 225 (no user)
- Created new inbound route, destination=225
- Enabled DAHDI for writing
- Apply config
- Restart DAHDI and asterisk
- Created new trunk DAHDI\c2, prefix=“w”
- Created new outbound route POTS, trunk=DAHDI\c2, pattern=XXXXXXXXXX
- Apply config
- Dial out from 225, “All circuits are busy now”
- reboot
On VMs installed with the VMware EFI firmware (which CentOS 7 supports), I was never able to get the A200 card to work. Dead air on all outbound calls. On VMs installed with VMware BIOS firmware (which both CentOS 6 and 7 support), the A200 card worked after the reboot. So, FreePBX 13 vs FreePBX 14 was probably a red herring.
I don’t particularly need EFI; it was just a convention that I have been using for all my VMs. As I have the foundation of a working system now, I will proceed with the re-installation. But, I can still be available if there’s anything that might want me test. Thanks!