Why if I dont want FQDN?

[ionut]

I will install 3CX on a PC with 2 network cards: 1 card for LAN with NAT and static public IP for phone provisioning and another card with private line for sip trunk. I want mentenance only for 1 year.

What happen after first year if I dont want FQDN? I dont want use remote management from public domain nor conference links and I will provision my hardphones using IP address. Its mandatory to port forward HTTP/HTTPS with FQDN? This FQDN is used to verify the licence or for what?

What is wrong if I want to isolate my 3CX PBX on an IP without NAT?

Thank you

 

[Archie Frederic]

I will install 3CX on a PC with 2 network cards: 1 card for LAN with NAT and static public IP for phone provisioning and another card with private line for sip trunk. I want mentenance only for 1 year.

What happen after first year if I dont want FQDN? I dont want use remote management from public domain nor conference links and I will provision my hardphones using IP address. Its mandatory to port forward HTTP/HTTPS with FQDN? This FQDN is used to verify the licence or for what?

What is wrong if I want to isolate my 3CX PBX on an IP without NAT?

Thank you

What would happen is that all online support and updates would not be available anymore. But, all the features currently installed should still be available as it is. And port forwarding of the HTTPS and HTTP port would be used also in google push account, when remote registering, if you are familiar with it. And by the way, nothing is wrong if you want to isolate your 3cx pbx on an IP without NAT.