Pre install question

[briankelly64]

I can install on Debian or Windows but would prefer Debian. Good idea? I have a public static IP and domain name. Should I go through the extra steps of using my own public domain name or take advantage of the 3CX process that uses its naming. Other than an email server there is nothing else running that utilizes the public ip or name.

 

[cobaltit]

So no one can answer the questions but you. If you are supporting the environment and you prefer Debian then install on Debian. Otherwise install on Windows. Both are supported. If you want to use your own FQDN and understand the extra work involved then do it. If you want things to just work then let 3CX manage it.

 

[Saqqara]

As above

my choice would be Debian , takes out windows updates etc and use 3cx fqdn address.

you do not need a email smtp server. you can use 3cx server which uses port 2528

 

[briankelly64]

I assume both platforms are 100% equivalent now and offer the same feature set through the web interface. If using the 3CX FQDN I thought I remember seeing that a current support contract is required for that to function after an initial support period?

 

[Saqqara]

No difference between debian or windows versions - all have the same functions (license edition dependance)

you would be mad, not to have a current support contacts as it allows you to upgrade the the latest version - 3cx is always being developed https://www.3cx.com/blog/releases/v16-roadmap-updates/

Some of the updates are out of 3cx control , for example https://www.3cx.com/community/threa...ires-http-2-is-your-windows-compatible.70255/

 

[florink]

I'd go for the linux version + 3CX FQDN. Yes the FQDN does need a valid maintenance but unless I am mistaken due to covid19 the free version is currently extended to 3 years. So for the next 3 years you won't have to worry about it! If you ever want to switch to Windows you can very easily migrate. Just take a backup and restore on the new machine.

p.s: Use the 3CX Linux ISO ideally.
p.s2: If you choose to use your own FQDN then you'll have to manage the SSL certs, DNS etc.

 

[florink]

Ah looking at the edition comparison I missed something major. You cannot use your own FQDN in the free edition! So no dilemma for you, you only have one option!