I have a VM server running several VM’s with no issues. When I try to install FreePBX 17 using the ISO I have issues with the network install portion where nothing is recognize for DHCP. If I manually configure that part it continues only to fail again when installing the mirror. Suggests it’s not resolving the domain names.
While I would like to use the ISO install method are these problems common and is it better to install Debian 12 first and then use the non vm install method?
You can try the alternative Heqet ISO:
Sounds like network pseudo-hardware detection failure. Which spice level from GRUB screen did you pick ? (OSO excludes non-free drivers, but for that to break on virtualized device would be odd as usually those are more standardized.)
Does standard Debian 12 install pick up your network ? Also what hypervisor ?
I’m betting this is the same as what I posted in this thread:
BETA v17 ISO feedback request - partitions and more - split from other thread - Distro Discussion & Help - FreePBX Community Forums
I’m using Hyper-V and had to go to the console and make some manual changes in order for it to work. I haven’t tried the latest ISO to see if this is fixed or not.
Chris
The latest ISO offers a SLAB option at the GRUB installer to utilize only three partitions – boot, root and swap – which should help with some of the edge cases around additional partitions.
As for the networking, that could still use a touch-up. Planning to poke around in there soon to get another v17 ISO together in conjunction with the v18 BETA ISO.
I managed to get FreePBX 17 built from the ISO and the setup went well for all my extenstion in house. That’s where the success ended. I have spend countless hours chasing a variety of issues when adding remote extensions and trunks to other PBX’s. Extentions that fail after enabling a trunk, reported router “Blocked” ports yet WAN/LAN TCPDUMPS that suggest otherwise. I spent hours on the router reviewing TCPdumps in an attempt to determine if my firewall was causing issues and not passing ALL SIP related traffic. My router appears to be passing traffic yet still seeing failures. Been all through the PBX verifying settings and all seems to be correct yet we see inconsistant behaviours we can’t explain. I am not sure if my core PBX itself did not build 100% correctly. It seems that the outbound/inbound traffic is the major problem area.
I have no deep knowledge of SIP messaging yet do understand the high level protocols. I see 501 errors and trying to chase them down. I see "OPTIONS, NOTIFY, 200 OK , REGISTERS, and the REMOTE endpoint + MY PBX seem happy yet in some cased no audio other don’t connect as expeced. RTP ports 10,000 to 20,000 enabled port forwarding rules in place.
HAS ANYONE SEEN THIS KIND OF BEHAVIOURS OR INCONSISTENCIES BEFORE WHEN TRYING TO REMOTE THE PBX?
AFTER SO MANY HOURS PERHAPS ITS TIME TO START FROM SCRATCH. JUST TRYING TO GET A SENSE OF WHATS OUT THERE. I HAVE BEEN WORKING WITH OTHER FREEPBX OWNERS.
MY THANKS TO THOSE REPLIED TO MY FIRST MESSAGE !