Cloud or on prem, custom fqdn or 3cx fqdn?

[ZacSC]

Hello!

Looking for some folks perspectives on the direction I should head. I currently have two 3CX installs, one on prem, one in the cloud, one with a custom fqdn one with a 3cx fqdn. Eventually I think I want to converge them mostly because SMS requires a professional license and I am not sure I need two installs but I am not exactly sure what direction to head. Here is what I have...

#1 On prem that serves our cooperate offices with a custom fqdn, professional license, ISP SIP Trunk service (I have had this one for several years, started on v14 I think).
#2 In the cloud that serves some of our remote offices with a 3cx fqdn, standard license, cloud SIP Trunk service (skyetel) (I created this one so that remote offices did not need to connect to our cooperate network and learn a cloud install of 3cx).

It seems like automated SSL certificates may never come to custom fqdn installs and SMS requires a professional license to use so here is my question, I think I might want to consolidate these so what direction should I head?
-Move my professional license to the cloud install I have, port over the numbers to Skytel and use an SBC for our Cooperate Office?
-Ditch the cloud install and move them all to my on prem install (what about my custom fqdn and ssl certs, does that even matter?)
-Keep them separate, suck it up and purchase another professional license?
-Something else?

Thanks for the help!
Zac

 

[HRMNY]

I would move everything to cloud hosted, under a single server if possible. Use the 3CX FQDN, it's a no brainer. Every server we have deployed is hosted, nothing on-prem. SBC works great and STUN works fairly well too for smaller sites or work from home extensions.

 

[greatchoice]

I use Vultr for my cloud servers. Works great and the price you cant beat. SBC with the Rasp Pi

 

[StefanW]

my personal 2 cent, 3CX FQDN. Why pay extra for a cert and then every year(s) manually update them. All not worth the time and hassle...