Hello, for the company where I am working, I have set up a FreePBX server, but for the moment it is hosted on a virtual machine on my computer, because I was in a testing phase, to see if FreePBX could work for my company and how to connect it with the external service we needed.
Almost everything is working fine, so now I am looking for an external server on which I can put the freePBX server, if possible by exporting the machine virtual (or at least the configuration in it) so I don’t have to redo all the configuration.
I am in Switzerland, the server need to be local (so no cloud service), cost efficiency, have at least one rg45, one usb connection, 2 GB of RAM, for stockage no sure.
We won’t need to save video or vocal call, the server will only be used to connect our voip phone with our trunk provider (swisscom) and odoo.
Thank for all the help you have already given me throught the others posts.
You can make a Full Backup and Restore that backup you can use where you wanted. VM, Physical or Cloud environment server.
In here backup restore you have to know your FreePBX Deployment ID to active same id at the new VM or Physical server side.
Sorry me, i don’t understand your question.
You want to keep that FreePBX Box in house ( in a Local network)?
How many Extension and Calls you gonna have ?
You are thinking to install your new FreePBX-17 to Physical HW or VM Environment ?
Yes my boss prefer to have it in local network because it cost too much to host it on your main host (they ask for 27 CHF per month).
For the call, 8 calls maximum (but I think we will have rarely more than three at the same time, usually we are 2 working in the office),
for the extension I need one for odoo (one per user ?) and I am not sure if I need one extension per voip phone we have, for the moment I have 2 extensions
airsay your proposition is very good but overkill (and certainly too costly for our small business) at least for the moment
1st- Backup your VM FreePBX.
2- Export Backup out. ( To USB or any other media )
3- Install a new Debian-12 and Freepbx-17 to Physical Intel Nuc device.
4- Activate your new installed FreePBX-17 with same Deployment ID.
5- Restore your FreePBX(step 2) to new installation.
6- Compare VM and Physical FreePBX. Everything needs to be restored.
Yes, thats ID, ( Admin → System Admin → Activation → Deployment ID : XXXXXX ) Note at that number. Basically you can see same id at Sangoma Portal side. and when you what to buy additional Module License you gonna buy for and use that ID.
Thank you for your help, I don’t know if I need to open a new thread, but I have a strange problem with my VOIP set-up, some call from our side to another cellphone don’t work correctly, there is no audio from both side.
But some others call work fine.
I totally agree with you @shahin. I wanted to give @AubeMort and idea of the specs and sizes they could need. Plus it’s nice to put Sangoma product out there given that this is more a less a Sangoma platform. But yes, a NUC would do.
I’m running with trunks to Deutsche Telekom on various plattform on different locations.
1st is a virtual on Synology Rackstation, where 19’’ physical rack is my preferred hardware. Costs nothing where Synology is available anyway.
2nd on APU3C4 single-board (www.varia-store.com), which has end of life, but swiss-made in 19’’ cover and m2-sata 128 GB 4 GB RAM productive system for now about 7 years with 4-8 calls at the same time. Now possibly available as APU3D4 where …4 at the end is the RAM-size. Costs about 300 €, and needs 0-Modem-cable and terminal to install OS since no VGA or other output is available. Install / boot from USB is BIOS configured. A little bit tricky.
3rd old fujitsu esprimo Q556/2 upgraded to 8 GB RAM, M2-SATA 128 GB, not win11 compliant any more, therefore end-of life as a company pc. Cheapest and fastest hardware in my environment running Debian12! For about 60 € second hand. Also runs postfix/dovecot mail-servers. Webmail - such as Roundcube - will not work in parallel since you’re gonna kill the freepbx web-platform.
Good idea is to use a kind of harddisk for permanent power-on such as as WD-red. Think also of possible power-loss. What happens to unsaved data in the harddisk-cache. Does the PC starts automatically when power comes back? Usually not.
Concerning Deployment-ID: You may unlink your current Deployment-ID under sysadmin and re-use it with your new hardware. …but 3times only.
Finally saying: You may use any hardware - even older ones - you have. My goal was lowest power consumption for a permanently running PC and less add-on to the heating of the room.
For each call which is running, you need 2 connections. The one from outside to freepbx (trunk), the other from freepbx to the extension. As long as I remember correct, 100 kb RAM each, so 200 kb per running call for both ends. These adds to 2GB RAM for 10 parallel running calls. But a 2GB 64bit Debian12-PC doesn’t make fun.
I also use a raspberryPi4 as a emergency freepbx. There’s a full “rasp-pbx” distribution available with reduced modules, and not and never supported by sangoma. You should not use it for permanent company use, since systems running from SD-Cards will not have an endless live.
